public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Achim Gottinger" <achim@gentoo.org>
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] gcc without ada,f77,objc ?
Date: Fri, 3 Jan 2003 18:05:08 +0100	[thread overview]
Message-ID: <006e01c2b34a$450718c0$6401a8c0@win2000> (raw)
In-Reply-To: 200301021521.18151.mailman@hanez.org


----- Original Message -----
From: "Johannes Findeisen" <mailman@hanez.org>
To: "Martin Volf" <mv@inv.cz>; <gentoo-dev@gentoo.org>
Sent: Thursday, January 02, 2003 3:21 PM
Subject: Re: [gentoo-dev] gcc without ada,f77,objc ?


> -----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.
>
Hi,

Maybe the gcc ebuild can be splitted in different packages gcc/g++, f77,
objc, ada, java. Separated tarballs for these are already available (
http://gd.tuwien.ac.at/gnu/sourceware/gcc/releases/gcc-3.2.1/  ).

bye achim~

> 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 PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQE+FEre1e37d/WNRDURAuHhAJ4yvFZh7Ml74FVcCxBcHKQDGS9aDQCeMSHK
> m/GzxOevSUdjn1X27cDkPrw=
> =Csx9
> -----END PGP SIGNATURE-----
>
>
> --
> gentoo-dev@gentoo.org mailing list
>
>


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-01-03 16:08 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 [this message]
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='006e01c2b34a$450718c0$6401a8c0@win2000' \
    --to=achim@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