Haren Visavadia wrote:
You missed "The GCC team has been urged to drop
support for SCO Unix from GCC, as a protest against
SCO's irresponsible aggression against free software".
When starting my Unix learnings with SCO Xenix/286,
SCO Xenix/386 and SCO Unix (all some kind of trademarks),
I hav
Haren Visavadia <[EMAIL PROTECTED]> writes:
| --- Kean Johnston wrote:
| > > The GCC team has been urged to drop support for
| > SCO
| > > Unix from GCC, as a protest against SCO's
| > irresponsible
| > > aggression against free software and GNU/Linux.
| > > We have decided to take no action at
--- Kean Johnston wrote:
> > The GCC team has been urged to drop support for
> SCO
> > Unix from GCC, as a protest against SCO's
> irresponsible
> > aggression against free software and GNU/Linux.
> > We have decided to take no action at this time,
> as we
> > no longer believe that SCO is a seri
The GCC team has been urged to drop support for SCO
Unix from GCC, as a protest against SCO's irresponsible
> aggression against free software and GNU/Linux.
> We have decided to take no action at this time, as we
no longer believe that SCO is a serious threat.
What part of *NO ACTION* was unc
--- Kean Johnston wrote:
> Perhaps you should read README.SCO at the top of the
> GCC tree?
README.SCO contains:
"
The GCC team has been urged to drop support for SCO
Unix from GCC, as
a protest against SCO's irresponsible aggression
against free software
and GNU/Linux. We have decided to take n
Your system is NOT supported by GCC, please read
http://www.fsf.org/licensing/sco/
Perhaps you should read README.SCO at the top of the GCC tree?
And for your information, SCO is supported by GCC. I am the
maintainer, and a few malcontents like yourself aside, I
have had little trouble doing so.
--- Kean Johnston <[EMAIL PROTECTED]> wrote:
> System V Release 5 (UnixWare / OpenServer 6).
>
Your system is NOT supported by GCC, please read
http://www.fsf.org/licensing/sco/
___
How much free photo storage do you g
The error makes perfect sense. __pthread_mutex has only one
assignment operator for it (implicitly generated by the compiler):
__pthread_mutex & operator=(const __pthread_mutex&).
When you try to pass a volatile __pthread_mutex (named as
pthread_mutex_t), the compiler can't pass it to the assig
Kean Johnston wrote on 22/07/2005 00:41:06:
[...]
>
> I hope someone can help me. I am C++ impaired, and I am getting
> the following error when trying to bootstrap the current 4.0.2
> CVS. The error is coming from include/ext/bitmap_allocator.h
> line 111. The relevant code snippet is:
>
> cla
Hi all,
I hope someone can help me. I am C++ impaired, and I am getting
the following error when trying to bootstrap the current 4.0.2
CVS. The error is coming from include/ext/bitmap_allocator.h
line 111. The relevant code snippet is:
class _Mutex {
__gthread_mutex_t _M_mut;
// Prevent Cop
10 matches
Mail list logo
