Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: raj.khem@gmail.com, kai.kang@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] gcc: remove g77/f77
Date: Thu, 13 Jun 2024 21:22:48 +0100	[thread overview]
Message-ID: <81dc7b8327a4e18655db76ffaed23e3ca8d073d4.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1sqKt13o1DbyVmw3OARQu5u=CP4z76PKdidfPqfridvYJw@mail.gmail.com>

On Thu, 2024-06-13 at 09:58 -0700, Khem Raj via lists.openembedded.org
wrote:
> On Thu, Jun 13, 2024 at 4:53 AM Kai Kang via lists.openembedded.org
> <kai.kang=windriver.com@lists.openembedded.org> wrote:
> > 
> > From: Kai Kang <kai.kang@windriver.com>
> > 
> > g77/f77 has been removed from gcc 4.0.0 via commit:
> > 
> > * b4117c30610 Makefile.def, [...]: Remove all mention of libf2c.
> > 
> > When set
> > 
> >     FORTRAN = ",f77"
> > 
> > it complains with error:
> > 
> > > The following requested languages could not be built: f77
> > > Supported languages are: c,c,c++,fortran,go,lto,m2,objc,obj-c++
> > 
> > So remove g77/f77 from gcc recipes.
> 
> Looks fine to me.

Agreed, this looks like good cleanup thanks!

I'll queue for testing.

Cheers,

Richard


  reply	other threads:[~2024-06-13 20:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 11:51 [PATCH 1/2] gfortran: update runtime dependencies kai.kang
2024-06-13 11:51 ` [PATCH 2/2] gcc: remove g77/f77 kai.kang
2024-06-13 16:58   ` [OE-core] " Khem Raj
2024-06-13 20:22     ` Richard Purdie [this message]
2024-06-13 21:56 ` [OE-core] [PATCH 1/2] gfortran: update runtime dependencies Richard Purdie
2024-06-14  2:36   ` Kai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=81dc7b8327a4e18655db76ffaed23e3ca8d073d4.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=kai.kang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox