This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/51103] configure: error: GNU Fortran is not working
- From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 12 Nov 2011 17:29:38 +0000
- Subject: [Bug fortran/51103] configure: error: GNU Fortran is not working
- Auto-submitted: auto-generated
- References: <bug-51103-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51103
--- Comment #11 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2011-11-12 17:29:38 UTC ---
On Sat, Nov 12, 2011 at 05:22:42PM +0000, richalewis at gmail dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51103
>
> --- Comment #9 from Richard Lewis <richalewis at gmail dot com> 2011-11-12 17:22:42 UTC ---
> (In reply to comment #8)
> > On Sat, Nov 12, 2011 at 02:51:32PM +0000, richalewis at gmail dot com wrote:
> > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51103
> > >
> > > --- Comment #7 from Richard Lewis <richalewis at gmail dot com> 2011-11-12 14:51:32 UTC ---
> > > Created attachment 25807 [details]
> > > --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25807
> > > libgfortran build log
> > >
> > > --
> >
> > In what directory is the gcc source code?
> >
> > In what directory did you run configure?
>
> ./gcc-4.6.2
>
> configure and make in the top level directory, libgfortran.a build fails
>
What happens if you actually follow the installation instruction?
Building gcc within its source directory hierarchy has not been
supported for years. One can get lucky and have a successful
build, but it is neither guaranteed to work nor recommended.