[Bug bootstrap/49469] New: GCC fails to bootstrap when building with embedded zlib on Mac OS X 10.6.7

[Bug bootstrap/49469] New: GCC fails to bootstrap when building with embedded zlib on Mac OS X 10.6.7

[manphiz at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49469

           Summary: GCC fails to bootstrap when building with embedded
                    zlib on Mac OS X 10.6.7
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: manphiz@gmail.com


When building trunk on Mac OS X 10.6.7, it fails when building the embedded
zlib, which creates an i386 directory in the building directory (which was
different from source directory) during stage2, and still reference ./prev-gcc
from there, which would work if it were ../prev-gcc. The i386 seems to be
created as multidirs was set to i386 for zlib. The configure switch was:

$ $HOME/VCS/GIT/gcc/configure --prefix=/usr/local --with-gmp=/usr/local
--with-mpfr=/usr/local --with-mpc=/usr/local --with-ppl=/usr/local
--with-cloog=/usr/local --enable-cloog-backend=isl --program-suffix=-4.7
--enable-languages=c,c++ --disable-nls --disable-werror --enable-__cxa_init
--enable-concept-checks --enable-decimal-float --enable-full-dynamic-string
--enable-libstdcxx-debug --enable-libstdcxx-time --enable-multilib
--enable-plugin --enable-shared --enable-threads
--enable-version-specific-runtime-libs

And the build log is attached.

[Bug bootstrap/49469] GCC fails to bootstrap when building with embedded zlib on Mac OS X 10.6.7

[hp at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49469

Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hp at gcc dot gnu.org

--- Comment #1 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2011-07-02 22:53:49 UTC ---
(In reply to comment #0)
> And the build log is attached.

No, please attach it.

[Bug bootstrap/49469] GCC fails to bootstrap when building with embedded zlib on Mac OS X 10.6.7

[manphiz at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49469

--- Comment #2 from Xiyue Deng <manphiz at gmail dot com> 2011-07-03 04:29:09 UTC ---
Created attachment 24660
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24660
gcc_4.7_build.log.gz

Here is the build log with gcc trunk 'git pull'ed today, still the same
problem.

[Bug bootstrap/49469] GCC fails to bootstrap when building with embedded zlib on Mac OS X 10.6.7

[pinskia at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49469

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2012-02-03
     Ever Confirmed|0                           |1

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-02-03 23:22:38 UTC ---

checking for x86_64-apple-darwin10.8.0-gcc...
/tmp/gcc-build/i386/./prev-gcc/xgcc -B/tmp/gcc-build/i386/./prev-gcc/
-B/usr/local/x86_64-apple-darwin10.8.0/bin/
-B/usr/local/x86_64-apple-darwin10.8.0/bin/
-B/usr/local/x86_64-apple-darwin10.8.0/lib/ -isystem
/usr/local/x86_64-apple-darwin10.8.0/include -isystem
/usr/local/x86_64-apple-darwin10.8.0/sys-include  -m32
checking for suffix of object files... configure: error: in
`/tmp/gcc-build/i386/zlib':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.

Can you attach /tmp/gcc-build/i386/zlib/config.log if this still happens?

[Bug bootstrap/49469] GCC fails to bootstrap when building with embedded zlib on Mac OS X 10.6.7

[manphiz at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49469

--- Comment #4 from Xiyue Deng <manphiz at gmail dot com> 2012-02-07 03:28:06 UTC ---
Created attachment 26594
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26594
config.log

This is /tmp/gcc-build/i386/zlib/config when build with trunk revision 183937.
The configure options are:

${SOURCE_PATH}/configure \
    --prefix=${PREFIX} \
    --with-gmp=${PREFIX} \
    --with-mpfr=${PREFIX} \
    --with-mpc=${PREFIX} \
    --with-ppl=${PREFIX} \
    --with-cloog=${PREFIX} \
    --enable-cloog-backend=isl \
    --program-suffix=-${VERSION} \
    --enable-languages=c,c++,objc,obj-c++,fortran \
    --disable-nls \
    --disable-werror \
    --enable-__cxa_init \
    --enable-concept-checks \
    --enable-decimal-float \
    --enable-full-dynamic-string \
    --enable-libstdcxx-time \
    --enable-multilib \
    --enable-plugin \
    --enable-static \
    --enable-shared \
    --enable-threads \
    --enable-version-specific-runtime-libs

HTH.

[Bug bootstrap/49469] GCC fails to bootstrap when building with embedded zlib on Mac OS X 10.6.7

[pinskia at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49469

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-02-07 03:35:22 UTC ---
/Users/dxy/VCS/GIT/gcc/zlib/configure: line 3225:
/tmp/gcc-build/i386/./prev-gcc/xgcc: No such file or directory

>    --enable-multilib \

Don't use that option, zlib is not very friendly to it.  And the rest of the
build machinary knows if multilib is enabled or now.

[Bug bootstrap/49469] GCC fails to bootstrap when building with embedded zlib on Mac OS X 10.6.7

[manphiz at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49469

--- Comment #6 from Xiyue Deng <manphiz at gmail dot com> 2012-02-07 03:57:49 UTC ---
(In reply to comment #5)
> /Users/dxy/VCS/GIT/gcc/zlib/configure: line 3225:
> /tmp/gcc-build/i386/./prev-gcc/xgcc: No such file or directory
> 
> >    --enable-multilib \
> 
> Don't use that option, zlib is not very friendly to it.  And the rest of the
> build machinary knows if multilib is enabled or now.

Ah I see. Fortunately one can use --with-system-zlib as workaround.