Re: [gentoo-user] unable to emerge anything...

[James Ausmus]

On Jan 9, 2008 9:13 AM, Richard Torres <rtorres827@×××××.com> 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.


It may not be the C compiler at all. To check this copy the following code
into a file called test.c:



#include <stdio.h>

int main(void)
{
  printf("Hello World!\n");
  return 0;
}


And then run the following commands:

gcc test.c -o test
./test

If you see a Hello World! output, then your C compiler is working fine. If
this is the case, then you need to do as the original error message
specifies - check the config.log file. It should be located at
/var/tmp/portage/dev-lang/php-5.2.5-r1/work/php-5.2.5/config.log

config.log files can be a little confusing to read through if you're not
used to them, but you'll just want to start at the bottom and work your way
up, until you find any error messages - or, you can post your
config.logfile, and someone can help you out with it.

HTH-

James






>
>
> 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
>
> -----Original Message-----
> From: Alan McKinnon [mailto:alan.mckinnon@×××××.com]
> Sent: Sunday, January 06, 2008 1:51 AM
> To: gentoo-user@l.g.o
> 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@×××××.com>
> > To: gentoo-user@l.g.o
> > 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@l.g.o mailing list
>
> --
> gentoo-user@l.g.o mailing list
>
>