OpenSAML user discussion

["George Stanchev" <>]

Forgot to mention that I double checked by invoking g++ by hand with
-pthread option
and I can confirm that $? is 0 after that. So it is a gcc problem. I am
sure someone
somewhere has come up with a workaround. I will try to find it.

-----Original Message-----
From: George Stanchev 
[mailto:]
 
Sent: Thursday, May 10, 2007 6:13 PM
To: 

Subject: RE: building cpp-xmltooling on unix

I think can look into that -pthread issue for a workaround and will let
you know if I find anything.

If you can add also

#ifndef WIN32
#include <signal.h>
#endif

at the top of that Threads.h file, it'd be great.

Its worth mentioning that even with the g++ option being wrong, the
library biulds and links fine with no other errors or warnings. 

I haven't ran the tests, may be I can look into running them sometimes
tomorrow and will post here. 

George

-----Original Message-----
From: Scott Cantor 
[mailto:]
Sent: Thursday, May 10, 2007 5:58 PM
To: 

Subject: RE: building cpp-xmltooling on unix

> I am building with gcc, yes.

I know, and I have no plans to support that. I favor the system compiler
in all cases, and that's Sun's, not gcc.

> What about that other error. If I manually replace  the -pthread with 
> proper -pthreads it compiles, but that other error remains.

You can add #include <signal.h> and then you'll hit many other errors
immediately after that. There are at least 6-7 files not building right
off the bat, so it's not going to work yet. At least one isn't showing
any immediate signs of fixability, so that means a code around, which
takes longer.

I can check in a couple of fixes, including the signal header, in a bit
once I do a regression check.

That still won't fix the gcc issue, I don't have any suggestion for
that, but if the Makefiles aren't working, then you should consider gcc
completely unsupported right now.

-- Scott




**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact the
sender by reply e-mail and destroy all copies of the original message.