From: Martin Schlemmer <azarah@gentoo.org>
To: Johannes Findeisen <mailman@hanez.org>
Cc: mv@inv.cz,gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] gcc without ada,f77,objc ?
Date: Fri, 3 Jan 2003 00:08:49 +0200 [thread overview]
Message-ID: <20030103000849.322d9471.azarah@gentoo.org> (raw)
In-Reply-To: <200301021521.18151.mailman@hanez.org>
[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]
On Thu, 2 Jan 2003 15:21:12 +0100
Johannes Findeisen <mailman@hanez.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> hello martin,
>
> i don't think there is a way to do it without editing the ebuild
> file... there are no USE flags for ada,f77 and objc. you can see it in
> the ebuild of gcc, because there is a part where the java USE flag is
> used. it should be the same for for the other languages too.
>
> i would edit the ebuild and maybe say it to the developers in bugtraq,
> that we need USE flags for ada, f77 and objc. i don't think that they
> are inventing some new USE flags for this problem because it are big
> changes in the gcc ebuild... maybe ask the maintainer or author of the
> actual ebuild script...
>
> i know, that this is no help but i hope this information is usefull
> for you...
>
> i think the idea is not bad to add some more USE flags because not all
> people needs the other languages.
>
Too much of an overload on USE flags if you ask me. Anyhow, ada support
do not really compile in, and f77 and objc are not that big ones. If
you disable java, then you should be down a 1/4 or 1/3 of the time
already.
> kind regards
> hanez
>
> On Wednesday 01 January 2003 17:57, Martin Volf wrote:
> > Hello,
> >
> > is there an other way to emerge gcc without ada,f77,objc except
> > editing the.ebuild file? I don't need these languages, maybe the
> > build would be a little bit faster without them. Or am I wrong? I
> > was quite disappointed when I saw them built. Couldn't this be
> > documented somewhere?
> >
> > Thanks.
>
> - --
> begin .signature
> question: is it a feature to execute code in emails?
> i don't think so!
> end
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQE+FEre1e37d/WNRDURAuHhAJ4yvFZh7Ml74FVcCxBcHKQDGS9aDQCeMSHK
> m/GzxOevSUdjn1X27cDkPrw=
> =Csx9
> -----END PGP SIGNATURE-----
>
>
> --
> gentoo-dev@gentoo.org mailing list
>
--
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-02 22:12 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 [this message]
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
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=20030103000849.322d9471.azarah@gentoo.org \
--to=azarah@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=mailman@hanez.org \
--cc=mv@inv.cz \
/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