From: Sylvain <asm8@wanadoo.fr>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] 2 uclibc questions : (un)masked / new use flag ?
Date: Wed, 21 May 2003 01:25:41 +0200 [thread overview]
Message-ID: <20030521012541.60443fc6.asm8@wanadoo.fr> (raw)
Hello !
My questions are in the title :-)
1) What about unmasking uclibc ebuild ? Did someone use it ? If so,
are you happy with it, so that it would be possible to unmask it.
I didn't find anything related to it on bugs.gentoo, and very few topics
in forums.
2) Maybe i should submit a bug for that, but i first want to know if i'm
the only person interested in that : i speak about a uclibc use flag.
Packages in particular which could benefit from that are of course busybox,
but also udhcp, and maybe others ?
A package using this flag would change the PATH variable to
/usr/i386-linux-uclibc/usr/bin/:$PATH in the environnement of econf and
emake function.
Waiting for comments :-)
regards,
sylvain
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-05-20 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 23:25 Sylvain [this message]
2003-05-22 21:07 ` [gentoo-dev] 2 uclibc questions : (un)masked / new use flag ? Zach Welch
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=20030521012541.60443fc6.asm8@wanadoo.fr \
--to=asm8@wanadoo.fr \
--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