Date: Mon, 9 Feb 2009 05:56:34 +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: <20090209055634.GA2116@melon.esperance-linux.co.uk> In-Reply-To: <1b30fd140902081424p1d75e304y9f4ef9f9b472328c@mail.gmail.com> References: <1b30fd140902050032x20e84ef6oc5030c99e6a62d81@mail.gmail.com> <498ABACC.3060102@bsdforen.de> <1b30fd140902050218m1660ad97ife6b0a679d8a946a@mail.gmail.com> <20090207075521.GA93084@melon.esperance-linux.co.uk> <1b30fd140902080816v7dfb8bb6g6f3c9a3d162f48c0@mail.gmail.com> <20090208203553.GA99661@melon.esperance-linux.co.uk> <1b30fd140902081424p1d75e304y9f4ef9f9b472328c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 08, 2009 at 10:24:52PM +0000, David Collins wrote: > > > 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)). > > I tried running portupgrade as root user, not sudo, and no success. > The bottom line is > ---> Packages processed: 2 done, 69 ignored, 133 skipped and 28 failed > > I think the most pressing issue is that I am not able to compile. I > have watched the output periodically and I saw a lot of configure > errors. Picking one at random this is the config.log (grub) file, the > error being "compiler is unable to create executables" exit 77: > > I think if this were to be solved then my ports would be unbroken! Sorry, I got distracted & forgot your compiler toolchain is broken. What does: $ ldconfig -r | grep gcc_s give you? If it fails to return anything, then you might want to try running ldconfig: # /etc/rc.d/ldconfig start Then try grepping ldconfig -r output again. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090209055634.GA2116>