This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch, libgfortran] PR 27740 Symbol versioning
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Janne Blomqvist <blomqvist dot janne at gmail dot com>
- Cc: fortran at gcc dot gnu dot org, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 20 Apr 2007 13:44:12 -0700
- Subject: Re: [Patch, libgfortran] PR 27740 Symbol versioning
- References: <462860CB.8060209@gmail.com>
On Fri, Apr 20, 2007 at 09:42:19AM +0300, Janne Blomqvist wrote:
>
> Regtested on i686-pc-linux-gnu.
>
> Ok for trunk?
>
> --
> 2007-04-20 Janne Blomqvist <jb@gcc.gnu.org>
>
> PR fortran/27740
> * configure.ac: New test to determine if symbol versioning is
> supported.
> * Makefile.am: Use result of above test to add appropriate linker
> flags.
> * gfortran.map: New file.
> * configure: Regenerated.
> * Makefile.in: Regenerated.
> * config.h.in: Regenerated.
I applied the patch, ran aclocal, autoconf, and automake. Ran
the new configure. During the build I used tee to get a log
of everything written to the screen. In the libgfortran configure
portion of the build, I see
checking whether symbol versioning is supported... yes
which of course is good. The built compiler gives
=== gfortran Summary ===
# of expected passes 17379
# of expected failures 7
# of unsupported tests 74
on x86_64-*-freebsd. What I can't determine is if symbol
version is actually used. :-\ There is no mention of gfortran.map
is the log file. I can find libgomp.map, libssp.map, and libgcc.map,
but no gfortran.map. So, I guess I've done something wrong.