From: "Caleb Tennis" <caleb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-libs/qt: ChangeLog qt-4.3.2.ebuild
Date: Wed, 3 Oct 2007 14:05:58 -0400 (EDT) [thread overview]
Message-ID: <46082.192.168.2.155.1191434758.squirrel@www.aei-tech.com> (raw)
In-Reply-To: <20071003173803.GX15143@supernova>
> Try being a little smarter with both CHOST and CXX -- only add an
> exception if the spec name isn't equal to the variable value.
>
> spec=$(echo ${CHOST} | cut -d- -f3)
> spec=${spec%%[0-9]*}
> spec=${spec}-$(tc-getCXX)
The bsd folks are the ones who added these conditionals. I'd like for them to make
the necessary changes, because I don't want to risk screwing up their
builds/installs.
> For icc, you should just be able to use 'icc'; it's installed that for
> quite a while. That way you don't require any special cases here.
This change was made based on a bug a user filed (albiet, some time ago). Again,
I'd prefer if someone who can test it with icc can make the appropriate change.
> Quote variables that can have spaces in them: D, S, T, WORKDIR,
> FILESDIR, DESTDIR, ROOT.
Should be fixed thanks.
> If emake doesn't work, please add a comment to that effect.
Will test and fix or comment as needed, thanks.
Caleb
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-03 18:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Id5gB-0006KU-HS@stork.gentoo.org>
2007-10-03 17:38 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in x11-libs/qt: ChangeLog qt-4.3.2.ebuild Donnie Berkholz
2007-10-03 18:05 ` Caleb Tennis [this message]
2007-10-04 4:03 ` Steve Long
2007-10-04 6:49 ` Roy Marples
2007-10-04 7:32 ` Donnie Berkholz
2007-10-04 7:43 ` Roy Marples
2007-10-04 9:53 ` Marijn Schouten (hkBst)
2007-10-04 10:11 ` Roy Marples
2007-10-05 12:34 ` [gentoo-dev] " Steve Long
2007-10-05 17:50 ` Donnie Berkholz
2007-10-05 23:41 ` [gentoo-dev] " Steve Long
2007-10-06 0:06 ` Donnie Berkholz
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=46082.192.168.2.155.1191434758.squirrel@www.aei-tech.com \
--to=caleb@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