[Bug fortran/51779] New: gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[Bug fortran/51779] New: gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[zippy at anl dot gov]

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

             Bug #: 51779
           Summary: gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2,
                    with gfortran erorr
    Classification: Unclassified
           Product: gcc
           Version: 4.6.2
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zippy@anl.gov


Created attachment 26261
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26261
gcc-4.6.2/build2/x86_64-apple-darwin11.2.0/libgfortran/config.log

Trying to build gcc 4.6.2 on Mac OS X Lion, with Xcode 4.2.1 installed.
Prerequisites like gmp, mpc, etc built fine. Configure step for gcc gave no
errors. Actual "make" step for gcc failed like this:


checking whether the /Users/zippy/Downloads/gcc-4.6.2/build2/./gcc/gfortran
-B/Users/zippy/Downloads/gcc-4.6.2/build2/./gcc/
-B/Users/zippy/zippy_gcc/x86_64-apple-darwin11.2.0/bin/
-B/Users/zippy/zippy_gcc/x86_64-apple-darwin11.2.0/lib/ -isystem
/Users/zippy/zippy_gcc/x86_64-apple-darwin11.2.0/include -isystem
/Users/zippy/zippy_gcc/x86_64-apple-darwin11.2.0/sys-include    linker
(/Users/zippy/Downloads/gcc-4.6.2/build2/./gcc/collect-ld) supports shared
libraries... yes
checking dynamic linker characteristics... darwin11.2.0 dyld
checking how to hardcode library paths into programs... immediate
checking whether the GNU Fortran compiler is working... no
configure: error: GNU Fortran is not working; please report a bug in
http://gcc.gnu.org/bugzilla, attaching
/Users/zippy/Downloads/gcc-4.6.2/build2/x86_64-apple-darwin11.2.0/libgfortran/config.log
make[1]: *** [configure-target-libgfortran] Error 1
make: *** [all] Error 2


Relevant libgfortran/config.log attached

[Bug fortran/51779] gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[kargl at gcc dot gnu.org]

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

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu.org
           Severity|major                       |normal

--- Comment #1 from kargl at gcc dot gnu.org 2012-01-07 06:38:26 UTC ---
What is the complete path for the gcc sources?
What is the complete path for where you tried
to build gcc?  What is the configure command line
you used?

[Bug fortran/51779] gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[zippy at anl dot gov]

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

--- Comment #2 from Tim Williams <zippy at anl dot gov> 2012-01-07 07:31:46 UTC ---
(In reply to comment #1)
> What is the complete path for the gcc sources?

/Users/zippy/Downloads/gcc-4.6.2/

> What is the complete path for where you tried
> to build gcc? 

/Users/zippy/Downloads/gcc-4.6.2/build2

>  What is the configure command line
> you used?

../configure --prefix=$HOME/zippy_gcc --enable-checking=release
--with-gmp=$HOME/zippy_gcc --with-mpfr=$HOME/zippy_gcc
--with-mpc=$HOME/zippy_gcc --program-prefix=zippy-

If helpful, I was using instructions from this blog as a guide (almost
certainly I am doing/configuring something wrong---no implication that these
instructions are wrong or that the blogger is in any way responsible):

http://solarianprogrammer.com/2011/12/01/compiling-gcc-4-6-2-on-mac-osx-lion/

[Bug fortran/51779] gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[burnus at gcc dot gnu.org]

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

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

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-07 14:06:22 UTC ---
I think that's the same issue as PR 51103, PR 51343, PR 51343.

Typically those errors occur if MPFR does not work (for various reasons).
However, there seems to be a particular issue with MacOS.

Andrew wrote in the other PRs:
> Darwin's GCC can sometimes produce a broken MPRF.  This is not a GCC bug.

[Bug fortran/51779] gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[burnus at gcc dot gnu.org]

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

--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-07 14:08:11 UTC ---
I forgot to mention that there exist also unofficial binaries for MacOS at:
  http://gcc.gnu.org/wiki/GFortranBinaries#MacOS
Thus, that could be an alternative to fixing the MPFR issue.

[Bug fortran/51779] gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[dominiq at lps dot ens.fr]

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fxcoudert at gcc dot
                   |                            |gnu.org, howarth at bromo
                   |                            |dot med.uc.edu

--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-01-07 15:34:28 UTC ---
You may try to configure mpfr with --disable-thread-safe: see
http://news.gmane.org/gmane.os.apple.fink.devel .

[Bug fortran/51779] gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[sgk at troutmask dot apl.washington.edu]

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

--- Comment #6 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2012-01-07 16:02:51 UTC ---
On Sat, Jan 07, 2012 at 07:31:46AM +0000, zippy at anl dot gov wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51779
> 
> --- Comment #2 from Tim Williams <zippy at anl dot gov> 2012-01-07 07:31:46 UTC ---
> (In reply to comment #1)
> > What is the complete path for the gcc sources?
> 
> /Users/zippy/Downloads/gcc-4.6.2/
> 
> > What is the complete path for where you tried
> > to build gcc? 
> 
> /Users/zippy/Downloads/gcc-4.6.2/build2
> 

This might be a part of your problem.   Others have
noted that there are known issues with MacOS Loin.

> >  What is the configure command line
> > you used?
> 
> ../configure --prefix=$HOME/zippy_gcc --enable-checking=release
> --with-gmp=$HOME/zippy_gcc --with-mpfr=$HOME/zippy_gcc
> --with-mpc=$HOME/zippy_gcc --program-prefix=zippy-
> 
> If helpful, I was using instructions from this blog as a guide (almost
> certainly I am doing/configuring something wrong---no implication that these
> instructions are wrong or that the blogger is in any way responsible):
> 
> http://solarianprogrammer.com/2011/12/01/compiling-gcc-4-6-2-on-mac-osx-lion/
> 

Try reading http://gcc.gnu.org/install/

[Bug fortran/51779] gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[howarth at nitro dot med.uc.edu]

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

Jack Howarth <howarth at nitro dot med.uc.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |howarth at nitro dot
                   |                            |med.uc.edu

--- Comment #7 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-01-07 19:02:06 UTC ---
FYI, the miscompilation of MPFR 3.1.0's tis support by clang is resolved in
Xcode 4.2.1.
This was radar://10291355, "Xcode 4.2 miscompiles tls support in MPFR 3.1.0".

[Bug fortran/51779] gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[zippy at anl dot gov]

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

--- Comment #8 from Tim Williams <zippy at anl dot gov> 2012-01-07 20:24:20 UTC ---
(In reply to comment #7)
> FYI, the miscompilation of MPFR 3.1.0's tis support by clang is resolved in
> Xcode 4.2.1.
> This was radar://10291355, "Xcode 4.2 miscompiles tls support in MPFR 3.1.0".

Thanks, Jack. I should've been more specific: I am using Xcode 4.2.1. I'll try
recompiling mpfr, and maybe try configuring mpfr with --disable-thread-safe as
Dominique suggested.

[Bug fortran/51779] gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[zippy at anl dot gov]

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

--- Comment #9 from Tim Williams <zippy at anl dot gov> 2012-01-09 17:15:06 UTC ---
(In reply to comment #4)
> I forgot to mention that there exist also unofficial binaries for MacOS at:
>   http://gcc.gnu.org/wiki/GFortranBinaries#MacOS
> Thus, that could be an alternative to fixing the MPFR issue.

Thanks, Tobias. I did try out the gfortran 4.6.2 from here, and it does compile
runnable code. Unfortunately, it still does not work with any version of gdb I
have tried on Mac OS X. My end goal in building the whole of gcc 4.6.2 was to
try building a Fortran code and debug it with the latest gdb version (7.3.1).
No luck with this prebuilt gfortran binary either.

[Bug fortran/51779] gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[howarth at nitro dot med.uc.edu]

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

--- Comment #10 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-01-09 17:45:42 UTC ---
(In reply to comment #9)
> Thanks, Tobias. I did try out the gfortran 4.6.2 from here, and it does compile
> runnable code. Unfortunately, it still does not work with any version of gdb I
> have tried on Mac OS X. My end goal in building the whole of gcc 4.6.2 was to
> try building a Fortran code and debug it with the latest gdb version (7.3.1).
> No luck with this prebuilt gfortran binary either.

   You will need to compile binaries with -Wl,-no_pie if you want to debug in
FSF gdb
under Lion (which defaults to -pie in the linker).  Apple's gdb automatically
disables
aslr under Lion (which can be turned back on by setting the  disable-aslr flag
to 0 within
Apple's gdb). This option doesn't exist in FSF gdb yet as far as I know.

ps There is some discussion of this at
http://reverse.put.as/2011/08/11/how-gdb-disables-aslr-in-mac-os-x-lion/.

[Bug fortran/51779] gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[zippy at anl dot gov]

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

--- Comment #11 from Tim Williams <zippy at anl dot gov> 2012-01-10 19:45:44 UTC ---
(In reply to comment #10)
> (In reply to comment #9)
> > Thanks, Tobias. I did try out the gfortran 4.6.2 from here, and it does compile
> > runnable code. Unfortunately, it still does not work with any version of gdb I
> > have tried on Mac OS X. My end goal in building the whole of gcc 4.6.2 was to
> > try building a Fortran code and debug it with the latest gdb version (7.3.1).
> > No luck with this prebuilt gfortran binary either.
> 
>    You will need to compile binaries with -Wl,-no_pie if you want to debug in
> FSF gdb
> under Lion (which defaults to -pie in the linker).  Apple's gdb automatically
> disables
> aslr under Lion (which can be turned back on by setting the  disable-aslr flag
> to 0 within
> Apple's gdb). This option doesn't exist in FSF gdb yet as far as I know.
> 
> ps There is some discussion of this at
> http://reverse.put.as/2011/08/11/how-gdb-disables-aslr-in-mac-os-x-lion/.

The -Wl,-no_pie linker flag is definitely secret sauce I was missing. This made
gdb 7.3.1 work with my test fortran program---was able to set breakpoints and
look at some variables. Thanks, Jack.

[Bug fortran/51779] gcc 4.6.2 build fails on Mac OS X Lion w/Xcode 4.2, with gfortran erorr

[kargl at gcc dot gnu.org]

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

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #12 from kargl at gcc dot gnu.org 2012-01-15 17:38:36 UTC ---
The audit trail indicates that this is not a gfortran.
Closing as INVALID.