OpenSAML user discussion

["George Stanchev" <>]

I am building with gcc, yes.

Here is the output from the log:

configure:21753: checking whether pthreads work with -pthread
configure:21797: gcc -o conftest  -Wall -O2 -DNDEBUG -pthread
conftest.c  -ldl  >&5
gcc: unrecognized option `-pthread'
conftest.c: In function `main':
conftest.c:34: warning: 'th' might be used uninitialized in this
function
configure:21803: $? = 0
configure:21807: test -z 
                         || test ! -s conftest.err
configure:21810: $? = 0
configure:21813: test -s conftest
configure:21816: $? = 0
configure:21830: result: yes

So I think gcc complains but the last line indicates the result is "yes"

I wonder if it is possible gcc to not set the proper exit code and thus
the
scripts to be fooled.

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




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

Subject: RE: building cpp-xmltooling on unix

> Oh, and on solaris, it generates -pthread option, but g++ complains it

> is an unrecognized option so I had to fix the Makefile manually but 
> that
still
> doesn't address the error above.

I think for that to happen, your build environment itself isn't correct
in some way. You're possibly mixing gcc and Sun CC libraries in some way
and the -pthread option is coming from some other dependency's build
settings. When you do a straight configure with gcc, it detects that
-pthread won't work, and should be generating -pthreads without the -mt
option that CC uses.

I note this because you're probably wasting your time unless you fix
that issue in the long run.

From what I can tell from a quick test with CC, the current trunk
doesn't build on Solaris yet. Died right off the bat and had a lot of
warnings too.
I don't know when I'll have a chance to fully debug it, but patches are
welcome. It's probably not totally broken or anything but will take some
time to work through all the small issues.

I don't have the resources to test gcc either, right now I'm using CC
exclusively, so there may still be problems with gcc even if I get it
working. In general I don't support or use gcc on Solaris any more.

-- 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.