From: Mark Goodwin <markgw@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] ia32 RPMs on ia64 systems
Date: Tue, 23 Jan 2001 06:02:14 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005088@msgid-missing> (raw)
I have an ia32 RPM that I need to support on ia64 - it has to remain ia32
due to some 3rd party libs for which I don't have the src (don't flame me).
At the moment I have to force RPM to let me install it, with horrible things like
rpm --ignorearch --nodeps --badreloc \
--relocate /usr/lib=/usr/i386-glibc21-linux/usr/lib -i <ia32package>
or depending on your ia64 distribution, I may need to relocate to /usr/ia32
or for some other distro, probably to somewhere else ...
Could someone from the each distro (redhat, suse, turbo, and deb) please tell
me what they are planning to do about ia32 packaging/installation support? Can
we please standardize on the relocation directories? At the moment, ia32 binaries
work just fine - it's the file system standards base and packaging support that
seem to be missing.. thanks, I'll summarize to the list.
--
Mark Goodwin
SGI Engineering.
reply other threads:[~2001-01-23 6:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590693005088@msgid-missing \
--to=markgw@sgi.com \
--cc=linux-ia64@vger.kernel.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