Date: Tue, 25 Feb 2003 12:30:49 -0500 From: "Paul A. Howes" <freebsd-ports@fair-ware.com> To: <freebsd-ports@freebsd.org> Cc: "'Jens Rehsack'" <rehsack@liwing.de> Subject: RE: Sablotron/PHP4 build error... Message-ID: <003401c2dcf3$a562e280$0200a8c0@howesnet> In-Reply-To: <3E5B8037.90901@liwing.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Jens, The problem is actually in the Sablotron build. "libsablot.so.69" Is not linked against libstdc++.so.4 in any way. Sablotron is written in C++ and uses the C++ compiler. The "sabcmd" executable is linked against libstdc++, which solves the problem local to Sablot, but does nothing to help PHP. If the Sablotron shared library is itself linked against the standard C++ library, then both sabcmd and mod_php4 have no trouble using it, even though they use different compilers for the link phase. -- Paul A. Howes -----Original Message----- From: owner-freebsd-ports@FreeBSD.ORG [mailto:owner-freebsd-ports@FreeBSD.ORG] On Behalf Of Jens Rehsack Sent: Tuesday, February 25, 2003 9:40 AM To: Paul A. Howes Cc: freebsd-ports@freebsd.org Subject: Re: Sablotron/PHP4 build error... other c++ intensive software didn't break, because they're using c++ even for linking. Compiling www/mod_php4 fails, because php is c source which uses cc for compiling and linking. The error that c++ libraries didn't link against c programs without adding the libc++ is at least as old as I can think developing with unix. In my lessons on university it was the same with solaris (I made homework using watcom c++ and rewrote the makefile on solaris, but using cc as link command - using either c++ as link command or adding -lstdc++ fixed it). No, it couldn't be fixed (as far as I know), because link stdc++ it an implicit dependency of c++, but not of cc. Adding explicit dependency does not has any effect while linking with c++ but fixes the missing calls in cc links. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003401c2dcf3$a562e280$0200a8c0>