Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 7 Feb 2009 07:55:21 +0000
From:      Frank Shute <frank@shute.org.uk>
To:        David Collins <davidcollins001@gmail.com>
Cc:        Dominic Fandrey <kamikaze@bsdforen.de>, freebsd-questions@freebsd.org
Subject:   Re: broken ports
Message-ID:  <20090207075521.GA93084@melon.esperance-linux.co.uk>
In-Reply-To: <1b30fd140902050218m1660ad97ife6b0a679d8a946a@mail.gmail.com>
References:  <1b30fd140902050032x20e84ef6oc5030c99e6a62d81@mail.gmail.com> <498ABACC.3060102@bsdforen.de> <1b30fd140902050218m1660ad97ife6b0a679d8a946a@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thu, Feb 05, 2009 at 10:18:52AM +0000, David Collins wrote:
>
> Sorry, forgot about that. Looking at it again I am not sure this is a
> ports thing, and more of an issue with the compiling tool chain.
> 
> 
> viper:/usr/ports/net-p2p/rtorrent$ sudo make
> ===>  Vulnerability check disabled, database not found
> ===>  Found saved configuration for rtorrent-0.8.2_1
> => rtorrent-0.8.2.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
> => Attempting to fetch from http://libtorrent.rakshasa.no/downloads/.
> rtorrent-0.8.2.tar.gz                         100% of  494 kB   48 kBps 00m00s
> ===>  Extracting for rtorrent-0.8.2_1
> => MD5 Checksum OK for rtorrent-0.8.2.tar.gz.
> => SHA256 Checksum OK for rtorrent-0.8.2.tar.gz.
> ===>  Patching for rtorrent-0.8.2_1
> ===>  Applying FreeBSD patches for rtorrent-0.8.2_1
> ===>   rtorrent-0.8.2_1 depends on package: libtorrent=0.12.2 - found
> ===>   rtorrent-0.8.2_1 depends on shared library: curl.5 - found
> ===>  Configuring for rtorrent-0.8.2_1
> checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... ./install-sh -c -d
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for C++ compiler default output file name...
> configure: error: C++ compiler cannot create executables
> See `config.log' for more details.
> ===>  Script "configure" failed unexpectedly.
> Please report the problem to flz@FreeBSD.org [maintainer]  and attach the
> "/usr/ports/net-p2p/rtorrent/work/rtorrent-0.8.2/config.log" including the
> output of the failure of your make command. Also, it might be a good idea to
> provide an overview of all packages installed on your system (e.g. an `ls
> /var/db/pkg`).
> *** Error code 1
> 
> Stop in /usr/ports/net-p2p/rtorrent.
> *** Error code 1
> 
> Stop in /usr/ports/net-p2p/rtorrent.
> 
> 
> 
> Also this might help
> 
> viper:/usr/ports/net-p2p/rtorrent$ uname -a
> FreeBSD viper.homeunix.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb
> 24 19:59:52 UTC 2008
> root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
> 
> 
> 
> On 05/02/2009, Dominic Fandrey <kamikaze@bsdforen.de> wrote:
> > David Collins wrote:
> >> Hi,
> >>
> >> I am not sure if this is better here or in the ports list, but I
> >> thought that since it is something that I have done because I don't
> >> know what I am doing here would be better
> >>
> >> A while ago I installed ports and everything was working fine.
> >> Recently I thought one of my ports was causing my machine to crash so
> >> I uninstalled it, but later found out that the only problem was a poor
> >> wireless network and low diskspace. Trying to reinstall the port
> >> failed at the configure stage. I tried a few others and they also
> >> failed at the same stage. This leads me to believe that it is
> >> something I have done.
> >>
> >> So here is the make install error:
> >> ===>  Script "configure" failed unexpectedly.Please report the problem
> >> to kuriyama@FreeBSD.org [maintainer]  and attach
> >> the"/usr/ports/textproc/expat2/work/expat-2.0.1/config.log" including
> >> the outputof the failure of your make command. Also, it might be a
> >> good idea to providean overview of all packages installed on your
> >> system (e.g. an `ls/var/db/pkg`).
> >>
> >> I found a post saying to try to compile a test program, so I tried that:
> >> viper:~$ gcc -o hello hello.c
> >> /usr/bin/ld: cannot find -lgcc_s
> >>
> >> So it appears that I have completely screwed the pooch! Is there
> >> anything I can do to fix this?
> >>
> >> Thanks
> >> David Collins

How did you uninstall that port after which everything fails at the
configure stage? Which port was it?

Check a couple of things:

$ which c++

and:

$ locate gcc_s | grep lib

Have you installed/uninstalled a c/c++ compiler from ports?


Regards,

-- 

 Frank 


 Contact info: http://www.shute.org.uk/misc/contact.html 




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20090207075521.GA93084>