broken ports
Frank Shute
frank at shute.org.uk
Sun Feb 8 12:36:06 PST 2009
On Sun, Feb 08, 2009 at 04:16:53PM +0000, David Collins wrote:
>
> > How did you uninstall that port after which everything fails at the
> > configure stage? Which port was it?
>
> It was rtorrent that I uninstalled, I used "make deinstall"
>
>
>
> > Check a couple of things:
> >
> > $ which c++
> >
> > and:
> >
> > $ locate gcc_s | grep lib
>
> viper:~$ which c++
> /usr/bin/c++
>
> also
> viper:~$ which gcc
> /usr/bin/gcc
> viper:~$ which cc
> /usr/bin/cc
>
>
> viper:~$ locate gcc_s | grep lib |more
> /usr/lib/libgcc_s.so
> /usr/local/lib/gcc-4.2.5/libgcc_s.so
> /usr/local/lib/gcc-4.2.5/libgcc_s.so.1
>
>
> > Have you installed/uninstalled a c/c++ compiler from ports?
>
> I don't think that I have I haven't installed/uninstalled a compiler
> from ports unless one of the ports did it, and I doubt this is the
> case.
>
That all seems to be in order.
I'm wondering whether your use of sudo is mucking things up and it's a
permissions problem. i.e: it's running make OK but freaking out when
it tries to invoke the compiler in the config stuff.
I always build my ports using portupgrade as root.
Maybe you could try logging in as root & then running it. If you'd
rather not do that, portupgrade has got an -s switch which allows you
to run the commands via sudo but you'd probably have to put cc & c++
in your sudoers (aswell as other commands e.g: install(1)).
Regards,
--
Frank
Contact info: http://www.shute.org.uk/misc/contact.html
More information about the freebsd-questions
mailing list