From owner-freebsd-ports Tue Feb 25 10:48: 8 2003 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77BE637B401 for ; Tue, 25 Feb 2003 10:48:06 -0800 (PST) Received: from mail.liwing.de (mail.liwing.de [213.70.188.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9784E43FD7 for ; Tue, 25 Feb 2003 10:48:04 -0800 (PST) (envelope-from rehsack@liwing.de) Received: (qmail 35849 invoked from network); 25 Feb 2003 18:48:02 -0000 Received: from stingray.liwing.de (HELO liwing.de) ([213.70.188.164]) (envelope-sender ) by mail.liwing.de (qmail-ldap-1.03) with SMTP for ; 25 Feb 2003 18:48:02 -0000 Message-ID: <3E5BBA62.1030005@liwing.de> Date: Tue, 25 Feb 2003 19:48:02 +0100 From: Jens Rehsack Organization: LiWing IT-Services User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Paul A. Howes" Cc: freebsd-ports@freebsd.org Subject: Re: Sablotron/PHP4 build error... References: <003401c2dcf3$a562e280$0200a8c0@howesnet> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Paul A. Howes wrote: > 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. That is correct and that's why I added '-lstdc++' to the link flags in the patch I attached at the PR I send last year. A problem ay occur when someone is trying to compile both using sth. like 'icc' or so. Jens > -- > 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. > > > -- L i W W W i Jens Rehsack L W W W L i W W W W i nnn gggg LiWing IT-Services L i W W W W i n n g g LLLL i W W i n n g g Friesenstraße 2 gggg 06112 Halle g g g Tel.: +49 - 3 45 - 5 17 05 91 ggg e-Mail: Fax: +49 - 3 45 - 5 17 05 92 http://www.liwing.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message