From: "Richard Torres" <rtorres827@yahoo.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] unable to emerge anything...
Date: Thu, 10 Jan 2008 01:40:11 -0600 [thread overview]
Message-ID: <004b01c8535c$0886fca0$0211030a@TALBOTGW> (raw)
In-Reply-To: <200801092207.42148.alan.mckinnon@gmail.com>
Alan,
I'll check the links out. As for as unmerging anything else no. Not yet
anyway, give me time though.
-----Original Message-----
From: Alan McKinnon [mailto:alan.mckinnon@gmail.com]
Sent: Wednesday, January 09, 2008 2:08 PM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] unable to emerge anything...
On Wednesday 09 January 2008, Richard Torres wrote:
> It's all a blur. It was trying to re-emerge something related to gcc
> and python was blocking it so I unmerged it.
> I've got python back using quickpkg like you suggested. Now I'm
> working on getting gcc to work. I did a quickpkg on gcc but emerge
> still fails with a 'C compiler cannot create executables' error.
> I'm pretty sure I'm using a working version.
>
> gcc-config -l
> [1] i686-pc-linux-gnu-3.3.4
> [2] i686-pc-linux-gnu-3.4.4 *
> [3] i686-pc-linux-gnu-3.4.4-hardened
> [4] i686-pc-linux-gnu-3.4.4-hardenednopie
> [5] i686-pc-linux-gnu-3.4.4-hardenednopiessp
> [6] i686-pc-linux-gnu-3.4.4-hardenednossp
>
> Thanks-a-bunch
Pleasw don't top post, especially not on a thread discussing technical
fixes. Thanks.
This seems to be a relatively common problem - I had it once myself
recently but forget the fix. Google turned up these interesting links:
http://forums.gentoo.org/viewtopic.php?t=27719
http://www.geektimes.com/linux/troubleshooting/c-cant-create-executables.htm
l
http://www.linuxquestions.org/questions/linux-newbie-8/c-compiler-cannot-cre
ate-executables-222588/
http://ubuntuforums.org/showthread.php?t=17033
http://www.brandonhutchinson.com/c_compiler_cannot_create_executables.html
http://forums.gentoo.org/viewtopic.php?t=27486
http://www.linuxforums.org/forum/linux-applications/25592-solved-compiler-ca
n-not-create-executables.html
I would guess that you also unmerged some other important package like
linux-headers, g++ or some such in the frenzy.
alan
>
> -----Original Message-----
> From: Alan McKinnon [mailto:alan.mckinnon@gmail.com]
> Sent: Sunday, January 06, 2008 1:51 AM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] unable to emerge anything...
>
> On Saturday 05 January 2008, Richard Torres wrote:
> > Alan,
> > Thanks for that. It's funny you should mention python, I just
> > inadvertently unmerged it (doh...). I've got another gentoo box
> > running a newer version of gcc and a newer kernel. Do you think I
> > can get what I need out of it?
>
> Yes, you should be able to use that. Python is SLOTted, so even if
> your other box is using a different SLOT, you can emerge the version
> you need, quickpkg it, copy it over to the first machine and unpack
> it there.
>
> quickpkg's are just tarballs so you can even use good old tar and
> bunzip2 if you managed to go to the next step of dohness and unmerge
> portage as well :-)
>
> btw, how did you manage to unmerge python? That's in system and
> portage usually goes to great lengths to prevent you doing just that
>
> alan
>
> > Thanks for your help,
> > -Richard
> >
> > ----- Original Message ----
> > From: Alan McKinnon <alan.mckinnon@gmail.com>
> > To: gentoo-user@lists.gentoo.org
> > Sent: Saturday, January 5, 2008 2:25:52 AM
> > Subject: Re: [gentoo-user] unable to emerge anything...
> >
> > On Saturday 05 January 2008, Richard Torres wrote:
> > > I'm getting pretty much the same error (C compiler cannot create
> > > executables). I'm pretty sure it's because gcc-3.3.4 is
> > > installed. I've tried upgrading gcc by emerging but get the same
> > > error (catch-22 situation). Here's the last part of the error log
> > > which is the same with anything I try to emerge.
> >
> > A quickpkg of gcc might help you out of this, it's about 7M or so
> > so small enough to mail to you. Perhaps some kind soul here with
> > similar settings to you can send their tbz2 of gcc-3.3.6.x
> >
> > Alternatively, you might be able to unpack a working gcc tarball
> > from a
> >
> > stage 3 onto your system and use that
> >
> > It doesn't help you right now, but I've managed to screw up enough
> > gentoo systems enough times that I now keep quickpkg copies of
> > known good working critical packages in $PKGDIR - minimally gcc,
> > glibc, python, portage, tar and a shell
> >
> > alan
> >
> > --
> > Alan McKinnon
> > alan dot mckinnon at gmail dot com
>
> --
> Alan McKinnon
> alan dot mckinnon at gmail dot com
> --
> gentoo-user@lists.gentoo.org mailing list
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
gentoo-user@lists.gentoo.org mailing list
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-10 7:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 19:53 [gentoo-user] unable to emerge anything Richard Torres
2008-01-06 7:50 ` Alan McKinnon
2008-01-09 17:13 ` Richard Torres
2008-01-09 18:22 ` James Ausmus
2008-01-10 7:36 ` Richard Torres
2008-01-10 8:05 ` Gerald Lutter
2008-01-09 20:07 ` Alan McKinnon
2008-01-10 7:40 ` Richard Torres [this message]
2008-01-10 8:07 ` [gentoo-user] " reader
-- strict thread matches above, loose matches on Subject: below --
2008-01-04 23:26 [gentoo-user] " Richard Torres
2008-01-05 9:25 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004b01c8535c$0886fca0$0211030a@TALBOTGW' \
--to=rtorres827@yahoo.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox