From: Jeremy Maitin-Shepard <jbms@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Ebuild determine architecture?
Date: Mon, 05 Jan 2004 18:14:10 -0500 [thread overview]
Message-ID: <87isjqrnst.fsf@jbms.ath.cx> (raw)
In-Reply-To: <ehqjvvko8a6r6e0qe5nfhh5frbdjrdq9pi@4ax.com> (Loyd Goodbar's message of "Mon, 05 Jan 2004 16:52:26 -0600")
Loyd Goodbar <loyd@blackrobes.net> writes:
> The RPMs I'm working with convert to .tar.gz and install, but the RPMs use
> RedHat's naming convention (blah.version.i386.rpm or blah.version.ppc.rpm). Is
> there a way in an ebuild to know which architecture (x86/ppc) is being used so
> I can determine the correct file name?
Yes, USE flags can be used to determine the architecture.
--
Jeremy Maitin-Shepard
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-01-05 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 22:52 [gentoo-dev] Ebuild determine architecture? Loyd Goodbar
2004-01-05 23:04 ` Daniel
2004-01-05 23:14 ` Jeremy Maitin-Shepard [this message]
2004-01-05 23:24 ` Ciaran McCreesh
2004-01-05 23:16 ` Marius Mauch
2004-01-06 0:34 ` Loyd Goodbar
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=87isjqrnst.fsf@jbms.ath.cx \
--to=jbms@gentoo.org \
--cc=gentoo-dev@lists.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