https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119750

            Bug ID: 119750
           Summary: Unable to compile GCC 14.2 using GCC 11.5 — on 32-bit
                    x86
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zbigniew2011 at gmail dot com
  Target Milestone: ---

Created attachment 61084
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61084&action=edit
files (*.i*)

Not sure is it still of importance — I don't see that version on the list —
still I report the problem. GCC 11.5 (on 32-bit platform) is unable to compile
GCC 14.2. Using Slackware 15.0, x86 platform (Athlon). gcc.build.log contains:

checking build system type... i686-slackware-linux-gnu
checking host system type... i686-slackware-linux-gnu
checking target system type... i686-slackware-linux-gnu
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for a sed that does not truncate output... /usr/bin/sed
checking for gawk... gawk
checking for libatomic support... yes
checking for libitm support... yes
checking for libsanitizer support... yes
checking for libvtv support... yes
checking for libphobos support... yes
checking for i686-slackware-linux-gcc... no
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/tmp/gcc-14.2.0/gcc.build.lnx':
configure: error: C compiler cannot create executables
See `config.log' for more details

(I didn't find any „config.log”, however)

I was using the source package from „slackware-current” with its build scripts
and patches. I'd like to mention that I successfully compiled 14.2 using 11.5 —
but on my other, 64-bit machine.

— GCC 11.5
— x86 32-bit
— scripts and patches from Slackware-current
— command line — just the standard gcc slackbuild script from Slackware-current
— you can see compiler's output above
— I found two (*.i*) files in source directory, but they are shipped with GCC
and I doubt they trigger a bug (still I don't know that) — they are both
attached

Reply via email to