This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Building egcs 2.95 on UnixWare 2.1.3


> > > it works swimmingly -- threads, shared libraries, C++ and all.
> > 
> > that's suprising since I didn't add thread support to the UW2 target.
> 
> It is, actually, isn't it.  UW2 doesn't have pthreads, which the UW7
> port would want.  Still, the program seems to work and ldd says the
> program is linked to /usr/lib/libthread.so.1.  Congratulations on doing

The choice of naming the flag "-pthreads" was perhaps not the best.  The
flag should work with UI threads, even though the name rings of "POSIX
threads".  I shamelessly picked it to be Makefile compatible with Linux.

If you're not using -pthreads (and I don't see how you could be on a UW2 
target) you need to set the right thing for the preprocessor, too.  I'm
guessing that a '-D_REENTRANT' is in order.

> > > "implicit int" rule of C89 conflicting with the ISO C++ rules.  The FAQ
> > > recommends adding -fpermissive to the command line to fix this, but it
> > > didn't help.  Has the option name changed, or what?
> 
> #include <X11/Intrinsic.h>
> int main(void)
> {
>         printf("Hello, world!\n");
>         return 0;
> }
> 
> $ g++ -fpermissive -I/usr/X/include test.c -o test

I don't see a problem on UW7 and don't have ready access to a UW2 system.
This test compiles and links without a problem.

Can you analyze what's in Intrinsic.h that it doesn't like?  If it would
help, I'll send you that file from a UW7 box for comparison.

> > > headers.)  2.95 fails on this file with a signal 11.
> > 
> > The G++ wizards did a lot of template changes.   Are you perhaps running
> > into a ulimit somewhere?  If, for example,  you crash into the ulimit for
> 
> That looks like the problem, or at least the end result.  I changed the

I'll look at this tonight.  

> I then had to write a 60 LOC test harness for the template.  I hope that
> slips under your size limits...  

Most of the maintainers won't grouse much about anything in the 100-200
line range.  It's the folks that do "I'm learning C++ and have written
a 12 zillion line program that fails.  Can you help debug it?" that get
ignored. :-)


Thanx for the testcase.   I'll poke at it later.

RJL


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]