public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't emerge any gcc
Date: Mon, 28 May 2012 09:49:07 +0800	[thread overview]
Message-ID: <1338169747.21793.0.camel@bunyip> (raw)
In-Reply-To: <CALF0-+WQZ6m3gGKP4YU+U2_a8sO1jVfPbmCLaar1CbqqD1cgUg@mail.gmail.com>

ram usage just before failure? - do you have enough, and enough disk
space?

BillK



-----Original Message-----
From: Ezequiel Garcia <elezegarcia@gmail.com>
Reply-to: gentoo-user@lists.gentoo.org
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't emerge any gcc
Date: Sun, 27 May 2012 21:08:21 -0300

Hi,

On Sun, May 27, 2012 at 8:48 PM, William Kenworthy <billk@iinet.net.au> wrote:
> probably not, you will need some more info as its a bit vague:
>
> What does "gcc -v" say?

Using built-in specs.
Target: i686-pc-linux-gnu
Configured with:
/var/tmp/portage/sys-devel/gcc-4.4.5/work/gcc-4.4.5/configure
--prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.4.5
--includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.4.5/include
--datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.4.5
--mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.4.5/man
--infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.4.5/info
--with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.4.5/include/g++-v4
--host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec
--disable-fixed-point --without-ppl --without-cloog --enable-nls
--without-included-gettext --with-system-zlib --disable-werror
--enable-secureplt --disable-multilib --enable-libmudflap
--disable-libssp --enable-libgomp
--with-python-dir=/share/gcc-data/i686-pc-linux-gnu/4.4.5/python
--enable-checking=release --disable-libgcj --with-arch=i686
--enable-languages=c,c++,fortran --enable-shared
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
--with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.4.5
p1.3, pie-0.4.5'
Thread model: posix
gcc version 4.4.5 (Gentoo 4.4.5 p1.3, pie-0.4.5)

>
> and "gcc-config -l"
>

localhost v4l-dvb # gcc-config -l
 [1] i686-pc-linux-gnu-4.4.5 *

> Can you compile anything, either through emerge or manually (i.e., even
> a  small "hello world")
>

Indeed! I can emerge other stuff.
Plus right now I'm working and compiling my stuff.

Feel free to ask me anything else,
Thanks,
Ezequiel.





  reply	other threads:[~2012-05-29  2:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-27 23:33 [gentoo-user] Can't emerge any gcc Ezequiel Garcia
2012-05-27 23:48 ` William Kenworthy
2012-05-28  0:08   ` Ezequiel Garcia
2012-05-28  1:49     ` W.Kenworthy [this message]
2012-05-29 11:28       ` Ezequiel Garcia
2012-05-28  0:18 ` Dale
2012-05-28  1:01 ` Pandu Poluan
2012-05-29 11:29   ` Ezequiel Garcia
2012-05-29 11:31     ` Ezequiel Garcia
2012-05-29 12:21       ` Ezequiel Garcia
2012-05-29 14:09         ` Ezequiel Garcia
2012-05-29 14:10         ` Alex Schuster

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=1338169747.21793.0.camel@bunyip \
    --to=billk@iinet.net.au \
    --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