From: Richard Reich <rreich@rdrtech.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] emerge to unconventional directories...
Date: 20 Feb 2002 11:13:07 -0500 [thread overview]
Message-ID: <1014221594.28230.7.camel@loki.rdrtech.net> (raw)
I'm working on a project that needs gcc 3.0.3, basicaly some areas of
the stl that are more mature... Anyway I was wondering what is needed
to modify an ebuild file to install to a different directory or is it
even possible?
Thanks for your help
Richard Reich
Here is a "sniped" versin of the ebuild file for gcc 3.0.3
Within are my questions...
<snip>
LOC=/usr <--- do I need to change this to something like
/opt/gcc-3.0.3? I assume yes
<snip>
src_install() {
#make install from the build directory
cd ${WORKDIR}/build
make install prefix=${D}${LOC} mandir=${D}${LOC}/share/man
infodir=${D}${LOC}/share/info || die
[ -e ${D}/usr/bin/gcc ] || die "gcc not found in ${D}"
FULLPATH=${D}${LOC}/lib/gcc-lib/${CHOST}/${PV}
cd ${FULLPATH}
dodir /lib
dosym /usr/bin/cpp /lib/cpp <--- I'm not exactaly sure what to
do with these do*** "things", do I leave them alone?
dosym gcc /usr/bin/cc
dodir /etc/env.d
echo "LDPATH=${LOC}/lib/gcc-lib/${CHOST}/${PV}" >
${D}/etc/env.d/05gcc <--- do I need to do something with this?
cd ${S}
if [ -z "`use build`" ]
then
#do a full texinfo-${TV} install
reply other threads:[~2002-02-20 16:17 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=1014221594.28230.7.camel@loki.rdrtech.net \
--to=rreich@rdrtech.com \
--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