From: Matthew Kennedy <mkennedy@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] gcc without ada,f77,objc ?
Date: 06 Jan 2003 11:59:37 -0600 [thread overview]
Message-ID: <87znqekvli.fsf@gentoo.shacknet.nu> (raw)
In-Reply-To: <006601c2b4f0$1406b5d0$6401a8c0@win2000>
"Achim Gottinger" <achim@gentoo.org> writes:
> >
> > hi achim,
> >
> > <snip>
> > > I agree and already too a short look. looks like all these packages need
> > > gcc-core and the additional sub-package.
> > > how do you think about an eclass for these builds?
> > </snip>
> >
> Hi Johannes,
>
> the problem ist that gcc (the binary) must be build with java,fortran,ada
> support,
> otherwise gcj... do not work, so it's not possible to use the separated
IIRC, only C and C++ support need to be built for GCJ (at least this
is the case for the GCC-3.3 branch from CVS).
When I first saw this "too many languages" complaint in bugzilla, I
had a WTF kind of reaction. If f77, objc were made USE flags, what
happens when the user tries to emerge something months from now which
depends on f77 -- it would fail at ./configure most likely.
Now I see this thread has solved that problem by proposing
gcc-{objc,java,f77} which is kinda messy like the VIM thing and mostly
un-Gentoo-like IMO, but anyway. What happens when the user has
gentoo-core, and emerge, say, octave which requires gcc-f77 to be
emerged. Can f77 truly be built outside GCC's own build system? If its
possible, what about java,objc,ada?
If not, then gcc-{c++,java,objc,ada} are merely aliases for emerging
gcc all-over, correct?
Personally, I feel the GCC we build should be as complete and
featureful as possible. After all, your compiler is the most important
part of a source-based distro.
My second preference is actually the USE flag approach. Only our more
knowledgeable users are going to tweak compiler USE flags and when
their ebuilds break with "Checking for a working
f77... (no)\n***Error: no fortran compiler found.***" they will know
exactly what to do (adjust their USE flags and re-emerge gcc).
Yes it seems a bit manual. Some support in portage might be need to
make it automatic (but I won't guess how hard that would be for
carpaski).
BTW, if we want to future proof ourselves a bit, some of the other
front ends currently in development are: GPC (pascal), Cobol, G95
(fortran 95), modula 2 and ghdl (like vhdl).
Matt
--
Matthew Kennedy
Gentoo Linux Developer
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-01-06 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 16:57 [gentoo-dev] gcc without ada,f77,objc ? Martin Volf
2003-01-02 14:21 ` Johannes Findeisen
2003-01-02 22:08 ` Martin Schlemmer
2003-01-03 17:05 ` Achim Gottinger
2003-01-03 18:05 ` Johannes Findeisen
2003-01-03 19:52 ` Achim Gottinger
2003-01-05 13:13 ` Johannes Findeisen
2003-01-05 15:42 ` Martin Schlemmer
2003-01-05 16:33 ` Martin Volf
2003-01-05 16:58 ` Richard Lärkäng
2003-01-05 16:47 ` Johannes Findeisen
2003-01-05 19:24 ` Achim Gottinger
2003-01-06 17:59 ` Matthew Kennedy [this message]
2003-01-11 13:04 ` Johannes Findeisen
2003-01-03 19:54 ` Marko Mikulicic
2003-01-03 22:11 ` Achim Gottinger
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=87znqekvli.fsf@gentoo.shacknet.nu \
--to=mkennedy@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/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