--Signature=_Fri__12_Mar_2004_18_01_04_+0100_NrOBPNE9RQAWNPNB
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

On Fri, 12 Mar 2004 09:57:33 -0700
<brook@biology.nmsu.edu> wrote:

> The www/apache package has some logic for handling gcc3, as stated by
> the Makefile:
> 
>      # if we are using gcc3, we need to link against libgcc_s, too. This
>      # ensures modules can resolve symbols they require from gcc.
> 
> However, with a -current i368 system (which has gcc3) there is no
> libgcc_s present and the compilation fails.  The following patch fixes
> the problem.
> 
>      --- Makefile.~1.1.1.4.~ 2004-03-03 11:43:05.000000000 -0700
>      +++ Makefile    2004-03-12 08:58:47.000000000 -0700
>      @@ -115,7 +115,7 @@
>       # ensures modules can resolve symbols they require from gcc.
>       .    if !empty(CC_VERSION:Mgcc-3*)
>       USE_GCC_SHLIB=         YES # defined
>      -LINK_LIBGCC_LDFLAGS+=  -lgcc_s
>      +#LINK_LIBGCC_LDFLAGS+= -lgcc_s
>       .    endif
>       .  endif
>       .endif
> 
> To me this implies that the Makefile logic needs to be somewhat
> smarter about whether or not to include -lgcc_s.
> 
> Any suggestions?  Should I send-pr this or does a commiter have a
> ready solution?

Looks like that we have libgcc_s.so* in -current, they were added some weeks
ago IIRC, so maybe you will have to rebuild your userland to get them.

[juan@Nocturno][~]> ls /usr/lib/libgcc_s* 
/usr/lib/libgcc_s.so     /usr/lib/libgcc_s.so.1   /usr/lib/libgcc_s.so.1.0
[juan@Nocturno][~]>

-- 
	Juan RP <juan@xtraeme.unixbsd.org>

--Signature=_Fri__12_Mar_2004_18_01_04_+0100_NrOBPNE9RQAWNPNB
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAUezQypkLYVDran0RArWqAJ97/pe61JLnAmLos60zaFvRA1s9HwCgl1HK
WT+GLA1MVvFIDUuK/ddVGrg=
=omeP
-----END PGP SIGNATURE-----

--Signature=_Fri__12_Mar_2004_18_01_04_+0100_NrOBPNE9RQAWNPNB--