This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/58276] "make install-host" gfortran is not functional


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

--- Comment #2 from Larry Baker <baker at usgs dot gov> ---
Andrew,

On 29 Aug 2013, at 4:31 PM, pinskia at gcc dot gnu.org wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58276
> 
> Andrew Pinski <pinskia at gcc dot gnu.org> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |RESOLVED
>         Resolution|---                         |INVALID
> 
> --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> libgfortran.spec is part of the target library libgfortran so you need to
> install the target libraries.  If the build mechanism for Yocto/OE does not do
> that, then it a bug there and not in GCC.

Yes, this is exactly what I described in my post.  The question I have is, what
is the intended behavior of a GCC "make install-host" with regard to the
functioning of the compilers.  gcc and g++ are functional; gfortran is not.  Is
that what the GCC maintainers expect?  Is that what the gfortran maintainers
expect?

Where can I read about the distinction between "make install", "make
install-host", and "make install-target"?  Is "make install-host" supposed to
install usable compilers?

> -- 
> You are receiving this mail because:
> You reported the bug.


Larry Baker
US Geological Survey
650-329-5608
baker@usgs.gov


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]