broken ports
Frank Shute
frank at shute.org.uk
Mon Feb 9 00:33:48 PST 2009
On Mon, Feb 09, 2009 at 07:30:44AM +0000, David Collins wrote:
>
> > What does:
> >
> > $ ldconfig -r | grep gcc_s
> >
> > give you?
>
>
> viper:~$ ldconfig -r | grep gcc_s
> 247:-lgcc_s.1 => /usr/local/lib/gcc-4.2.5/libgcc_s.so.1
On my FreeBSD 7.1-RELEASE-p2 amd64:
$ cc -v
Using built-in specs.
Target: amd64-undermydesk-freebsd
Configured with: FreeBSD/amd64 system compiler
Thread model: posix
gcc version 4.2.1 20070719 [FreeBSD]
and:
$ ldconfig | grep gcc_s
30:-lgcc_s.1 => /lib/libgcc_s.so.1
I think the problem is that somebody has installed a compiler out of
ports on your machine & it's associated libraries. See what cc -v
says.
It could be that it's invoking the system compiler (or not). Check:
$ pkg_info | grep gcc
aswell. Also look at /etc/make.conf & see if there's anything about
GCC_VERSION or something similar.
Regards,
--
Frank
Contact info: http://www.shute.org.uk/misc/contact.html
More information about the freebsd-questions
mailing list