Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] [sm-discuss] Failed gcc cast broke system, :-(

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Sukneet Basuta <sukneet AT gmail.com>
  • To: Javier Vasquez <j.e.vasquez.v AT gmail.com>
  • Cc: "sm, discuss" <sm-discuss AT lists.ibiblio.org>
  • Subject: Re: [SM-Discuss] [sm-discuss] Failed gcc cast broke system, :-(
  • Date: Mon, 31 Dec 2012 20:25:13 -0500

Sorry, the file is too big to attach, so I uploaded it to mediafire.
http://www.mediafire.com/?ac013q5jfartava
If you need to use wget or something, the download link should be
static, but you will need to get the download link using a browser or
download the html file and look for the url under "kNO = ".

Just place this in /var/cache/sorcery/ and resurrect gcc. It should be
for generic x64 since I casted it with --no-opts. I try to keep an
archive of gcc around since I often brake it myself.

Happy New Year!
-Sukneet

On Mon, Dec 31, 2012 at 7:01 PM, Javier Vasquez <j.e.vasquez.v AT gmail.com>
wrote:
> On Mon, Dec 31, 2012 at 5:20 PM, Javier Vasquez <j.e.vasquez.v AT gmail.com>
> wrote:
>> Hi,
>>
>> I was casting gcc again to incrementally add gcj. The build went OK,
>> but the installed was totally screwed cause I ran out of "/".
>>
>> Resurrecting didn't work cause the file available in cache is the new one,
>> :-(
>>
>> When trying to recompile gcc I always get:
>>
>> Building gcc
>> Building in dir: /usr/src/gcc-4.6.3
>> gcc 4.6.3
>>
>> checking build system type... x86_64-pc-linux-gnu
>> checking host system type... x86_64-pc-linux-gnu
>> checking target system type... x86_64-pc-linux-gnu
>> checking for a BSD-compatible install... /bin/install -c
>> checking whether ln works... yes
>> checking whether ln -s works... yes
>> checking for a sed that does not truncate output... /bin/sed
>> checking for gawk... gawk
>> checking for gcc... gcc
>> checking for C compiler default output file name...
>> configure: error: in `/usr/src/gcc-4.6.3.bld':
>> configure: error: C compiler cannot create executables
>> See `config.log' for more details.
>> ! Problem Detected !
>>
>> Any hint how to solve this, that'd be much appreciated.
>>
>> I'm using testing. If someone can lend a tarball or something to
>> uncompress and leave gcc in usable state again, that'll be great...
>> If it's a matter of changing permissions or m¿something, I'll need a
>> recipe, :-)
>>
>> Thanks in advance,
>>
>> --
>> Javier.
>
>
> The log starts failing like:
>
> COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.6.3/lto-wrapper
> Target: x86_64-pc-linux-gnu
> Configured with: /usr/src/gcc-4.6.3/configure --prefix=/usr
> --infodir=/usr/share/info --mandir=/usr/share/man
> --enable-threads=posix --enable-languages=c,c++,java
> --with-bugurl=http://bugs.sourcemage.org --enable-bootstrap
> --enable-checking=release --disable-multilib --without-ppl
> --without-cloog --enable-java-home --build=x86_64-pc-linux-gnu
> --enable-java-awt=gtk --with-system-zlib --enable-nls
> Thread model: posix
> gcc version 4.6.3 (GCC)
> configure:4189: $? = 0
> configure:4178: gcc -V >&5
> gcc: error: unrecognized option '-V'
> gcc: fatal error: no input files
> compilation terminated.
> configure:4189: $? = 1
> configure:4178: gcc -qversion >&5
> gcc: error: unrecognized option '-qversion'
> gcc: fatal error: no input files
> compilation terminated.
> configure:4189: $? = 1
> configure:4209: checking for C compiler default output file name
> configure:4231: gcc -O1 -march=x86-64 -fPIC -DPIC -pipe -DPIC -fPIC
> -O3 -O3 -I/usr/include/freetype2 -O3 -O3 conftest.c >&5
> gcc: error trying to exec
> '/usr/libexec/gcc/x86_64-pc-linux-gnu/4.6.3/collect2': execv: Exec
> format error
> configure:4235: $? = 1
> configure:4272: result:
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME ""
> | #define PACKAGE_TARNAME ""
> | #define PACKAGE_VERSION ""
> | #define PACKAGE_STRING ""
> | #define PACKAGE_BUGREPORT ""
> | #define PACKAGE_URL ""
> | /* end confdefs.h. */
>
> Attached goes the log. Not sure if the 1st error, or the collect2 one
> is the relevant one, :-(
>
> Thanks,
>
> --
> Javier.
>
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
>




Archive powered by MHonArc 2.6.24.

Top of Page