Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Feb 2003 19:48:02 +0100
From:      Jens Rehsack <rehsack@liwing.de>
To:        "Paul A. Howes" <freebsd-ports@fair-ware.com>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: Sablotron/PHP4 build error...
Message-ID:  <3E5BBA62.1030005@liwing.de>
References:  <003401c2dcf3$a562e280$0200a8c0@howesnet>

next in thread | previous in thread | raw e-mail | index | archive | help
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: <rehsack@liwing.de>
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E5BBA62.1030005>