public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: craig@jcb-sc.com
To: patrick@mail.boxsoft.com
Cc: craig@jcb-sc.com
Subject: Re: why does g77 build?
Date: Fri, 30 Apr 1999 23:15:00 -0000	[thread overview]
Message-ID: <19990425125840.8682.qmail@deer> (raw)
Message-ID: <19990430231500.wXuJrshWDCF74I17Kc61ly2-rGA-mwkhWTL0NFCjdIA@z> (raw)
In-Reply-To: <199904250430.VAA07112@3eye.boxsoft.com>

>   Could someone clearify these two for newbies like me.  Would
>   the make target for the 'straight-build' just be:
>
>      LANGUAGES="c,c++,etc" make
>
>   or is there more to it?

I think that would work, except for the lack of support for the "etc"
language.  :)

But if you want to avoid libf2c, for example, getting built, start off
with "rm -fr egcs-1.1.2/libf2c" or something like that -- I forget
the recipe others have posted.

        tq vm, (burley)

  reply	other threads:[~1999-04-30 23:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-17 13:59 Alexader V. Voinov
1999-04-24  9:19 ` craig
1999-04-24 21:29   ` patrick
1999-04-25  6:00     ` craig [this message]
1999-04-30 23:15       ` craig
1999-04-25  6:00     ` craig
1999-04-25  8:19       ` Mark Mitchell
1999-04-30 23:15         ` Mark Mitchell
1999-04-25 10:03       ` Jeffrey A Law
1999-04-30 23:15         ` Jeffrey A Law
1999-04-30 23:15       ` craig
1999-04-30 23:15     ` patrick
1999-04-30 23:15   ` craig
1999-04-30 23:15 ` Alexader V. Voinov
  -- strict thread matches above, loose matches on Subject: below --
1999-04-16 17:19 patrick
1999-04-16 21:00 ` craig
1999-04-17  4:07   ` Alex Buell
1999-04-30 23:15     ` Alex Buell
1999-04-30 23:15   ` craig
1999-04-18 13:58 ` Jeffrey A Law
1999-04-30 23:15   ` Jeffrey A Law
1999-04-30 23:15 ` patrick

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=19990425125840.8682.qmail@deer \
    --to=craig@jcb-sc.com \
    --cc=patrick@mail.boxsoft.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).