Bug 58842 - libgfortran configuration error in 32-bit mode for GCC 4.8 with MacPorts "universal installation"
Summary: libgfortran configuration error in 32-bit mode for GCC 4.8 with MacPorts "uni...
Status: RESOLVED WORKSFORME
Alias: None
Product: gcc
Classification: Unclassified
Component: fortran (show other bugs)
Version: unknown
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords: build
Depends on:
Blocks:
 
Reported: 2013-10-22 11:07 UTC by Bernard Kelly
Modified: 2019-06-17 05:06 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments
libgfortran configuration log file (9.04 KB, text/plain)
2013-10-22 11:07 UTC, Bernard Kelly
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernard Kelly 2013-10-22 11:07:31 UTC
Created attachment 31069 [details]
libgfortran configuration log file

Hi. Working on a Macbook running OS X 10.8.5 (Mountain Lion), with MacPorts. I want a "universal" installation of GCC (including Fortran) to run in 32-bit and 64-bit modes. This is failing for me (the pre-packaged 64-bit only is OK). Here's the bug report on trac.macports.org:

https://trac.macports.org/ticket/40548

A responder noted the following line in the lengthy log file I uploaded:

------------------------------------------------------------------------

:info:build checking if /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/build/./gcc/xg++ -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/build/./gcc/ -nostdinc++ -nostdinc++ -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/build/x86_64-apple-darwin12/i386/libstdc++-v3/include/x86_64-apple-darwin12 -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/build/x86_64-apple-darwin12/i386/libstdc++-v3/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/gcc-4.8.1/libstdc++-v3/libsupc++ -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/gcc-4.8.1/libstdc++-v3/include/backward -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/gcc-4.8.1/libstdc++-v3/testsuite/util -L/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/build/x86_64-apple-darwin12/i386/libstdc++-v3/src -L/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/build/x86_64-apple-darwin12/i386/libstdc++-v3/src/.libs -B/opt/local/x86_64-apple-darwin12/bin/ -B/opt/local/x86_64-apple-darwin12/lib/ -isystem /opt/local/x86_64-apple-darwin12/include -isystem /opt/local/x86_64-apple-darwin12/sys-include  -m32 PIC flag -fno-common -DPIC works... no
:info:build configure: error: GNU Fortran is not working; please report a bug in http://gcc.gnu.org/bugzilla, attaching /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/build/x86_64-apple-darwin12/libgfortran/config.log

------------------------------------------------------------------------

... and suggested I follow the advice therein. I'm now attaching the configuration logfile at the end.
Comment 1 Dominique d'Humieres 2013-10-22 21:37:25 UTC
The error "GNU Fortran is not working" is often related to problems with one (or several) of the gmp, mpfr, or mpc libraries. You may have a look at the following PRs: pr30960, pr34207, pr34242, pr36586, pr36810, pr41601, pr43770, pr45641, pr50062, pr50238, pr51103, or pr51607.

Check 
(1) that you have the right versions of this libraries in /opt/local that pass 'make check' without error;
(2) that you don't have other such libraries which may interfere with the one in /opt/local (look into /usr/local for instance).
Comment 2 Dominique d'Humieres 2013-12-21 20:32:11 UTC
No feedback. Closing as WORKSFORME.
Comment 3 Eric Gallager 2014-03-02 19:02:40 UTC
I am running into this error as well. I attached my relevant logfiles in the downstream ticket that the OP linked to.

(In reply to Dominique d'Humieres from comment #1)
> 
> Check 
> (1) that you have the right versions of this libraries in /opt/local that
> pass 'make check' without error;

Local-Admins-MacBook-Pro:~ ericgallager$ port installed gmp mpfr libmpc
The following ports are currently installed:
  gmp @5.1.2_0+universal (active)
  libmpc @1.0.2_0+universal (active)
  mpfr @3.1.1-p2_0+universal (active)

I lost my results for their testsuites, but I suppose that I can run them again...

> (2) that you don't have other such libraries which may interfere with the
> one in /opt/local (look into /usr/local for instance).

MacPorts sanitizes its build environment to avoid finding things in places like /usr/local. That is a moot point though, as I do not have any of gmp, mpfr, or libmpc installed in /usr/local anyways.
Comment 4 Eric Gallager 2014-03-05 17:10:13 UTC
(In reply to Eric Gallager from comment #3)
> I am running into this error as well. I attached my relevant logfiles in the
> downstream ticket that the OP linked to.
> 
> (In reply to Dominique d'Humieres from comment #1)
> > 
> > Check 
> > (1) that you have the right versions of this libraries in /opt/local that
> > pass 'make check' without error;
> 
> Local-Admins-MacBook-Pro:~ ericgallager$ port installed gmp mpfr libmpc
> The following ports are currently installed:
>   gmp @5.1.2_0+universal (active)
>   libmpc @1.0.2_0+universal (active)
>   mpfr @3.1.1-p2_0+universal (active)
> 
> I lost my results for their testsuites, but I suppose that I can run them
> again...

So I am back after re-running the testsuites, and it turned out that mpfr was the culprit, so I opened a separate issue downstream for that: https://trac.macports.org/ticket/42732
Comment 5 Eric Gallager 2014-03-05 17:43:03 UTC
(In reply to Eric Gallager from comment #4)
> > I lost my results for their testsuites, but I suppose that I can run them
> > again...
> 
> So I am back after re-running the testsuites, and it turned out that mpfr
> was the culprit, so I opened a separate issue downstream for that:
> https://trac.macports.org/ticket/42732

Actually libmpc was to blame as well: https://trac.macports.org/ticket/42733