OpenSAML user discussion

[Tristan Waddington <>]

Ah, dang. Spoke too soon. I was able to compile and configure everything 
but Shibboleth-2.1 now dies while compiling with this error:

remoting/impl/TCPListener.cpp: In member function 'void 
shibsp::TCPListener::setup_tcp_sockaddr(shibsp::sockaddr_in*) const':
remoting/impl/TCPListener.cpp:124: error: invalid application of 'sizeof' to incomplete type 'shibsp::sockaddr_in' 
remoting/impl/TCPListener.cpp:125: error: invalid use of incomplete type 'struct shibsp::sockaddr_in'
remoting/impl/TCPListener.cpp:73: error: forward declaration of 'struct 
shibsp::sockaddr_in'
remoting/impl/TCPListener.cpp:126: error: invalid use of incomplete type 
'struct shibsp::sockaddr_in'
remoting/impl/TCPListener.cpp:73: error: forward declaration of 'struct 
shibsp::sockaddr_in'
remoting/impl/TCPListener.cpp:127: error: invalid use of incomplete type 
'struct shibsp::sockaddr_in'
remoting/impl/TCPListener.cpp:73: error: forward declaration of 'struct 
shibsp::sockaddr_in'
remoting/impl/TCPListener.cpp: In member function 'virtual bool 
shibsp::TCPListener::bind(int&, bool) const':
remoting/impl/TCPListener.cpp:144: error: aggregate 'shibsp::sockaddr_in 
addr' has incomplete type and cannot be defined
remoting/impl/TCPListener.cpp: In member function 'virtual bool 
shibsp::TCPListener::connect(int&) const':
remoting/impl/TCPListener.cpp:170: error: aggregate 'shibsp::sockaddr_in 
addr' has incomplete type and cannot be defined
remoting/impl/TCPListener.cpp: In member function 'virtual bool 
shibsp::TCPListener::accept(int&, int&) const':
remoting/impl/TCPListener.cpp:194: error: aggregate 'shibsp::sockaddr_in 
addr' has incomplete type and cannot be defined
gmake[3]: *** [TCPListener.lo] Error 1
gmake[2]: *** [all] Error 2
gmake[1]: *** [all-recursive] Error 1
gmake: *** [all] Error 2

You can view my config.log here:
http://dev.emu.uoregon.edu/~tristan/config.log

Some gmake output here:
http://dev.emu.uoregon.edu/~tristan/gmake_errors.log

If you can offer any advice I would appreciate it. I did some poking 
around, but didn't come up with any solutions. Is there a Shibboleth 
list I would have better luck posting this to? Thanks, this is really 
driving my nuts.

-Tristan

Tristan Waddington wrote:
> Scott,
>
> I was finally able to get Shibboleth and its dependencies to compile 
> in FreeBSD today. After recompiling all the dependencies with the 
> --disable-static flag set, XML-Tooling was still unable to link to the 
> XML-Security-C library.
>
> I did some digging and found out that FreeBSD is unable to handle 
> shared libraries with extended version numbers in the file name.
>
> http://www.freebsd.org/doc/en/books/handbook/linuxemu-lbc-install.html
>
> To solve this problem I had to create some symlinks like so:
>
> libxml-security-c.so -> libxml-security-c.so.14.0
> libxmltooling-lite.so -> libxmltooling-lite.so.2.0
> libsaml.so -> libsaml.so.3.0
>
> After doing so the compiler was able to link successfully.
>
> Some of the dependencies created the links automatically, but 
> apparently    these did not.
>
> Thanks for your help!
>
> -Tristan
>
> Scott Cantor wrote:
> > Also, I have a vague memory that there may be some kind of system 
> > option or
> > compiler setting or something that controls whether -lfoo favors 
> > libfoo.so
> > or libfoo.a. Usually it's supposed to favor .so I think, but maybe 
> > something
> > on your box is doing the opposite.
> >
> > -- Scott