Search the forums and bugzilla. This a RFE, and there are at least a few
scripts and patches to do this. Currently, stock portage does not do
this.
On Wed, 2005-03-30 at 23:14 +0200, Antonio Coralles wrote:
> How can I tell portage to use specific CFLAGS for a particular package
> without temporar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nick Rout wrote:
> I thought perhaps
>
> CFLAGS="whatever" CXXFLAGS="${CFLAGS}" emerge foo
>
> no doubt some dev guru will tell me I am way out of line :-)
wrong! there's nothing wrong with doing that. If it was something like
ACCEPT_KEYWORDS you
gentoo-user@gentoo.org wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Nick Rout wrote:
>> I thought perhaps
>>
>> CFLAGS="whatever" CXXFLAGS="${CFLAGS}" emerge foo
>>
>> no doubt some dev guru will tell me I am way out of line :-)
>
> wrong! there's nothing wrong with doing that. If
On Thu, Mar 31, 2005 at 05:40:24PM +0200, Antonio Coralles wrote:
> gentoo-user@gentoo.org wrote:
[...]
> So, the correct way would be (??):
> #CFLAGS="whatever"
> #CXXFLAGS=CFLAGS
> #emerge something
If you really feel the need to cram it all onto one line, you could
#CFLAGS="whatever" && CXXFLAG
Juergen Fiedler wrote:
If you really feel the need to cram it all onto one line, you could
#CFLAGS="whatever" && CXXFLAGS=CFLAGS && emerge something
without the typo and even smaller:
# CFLAGS="whatever" && CXXFLAGS=$CFLAGS emerge something
SCNR
Christoph
--
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..
On Thu, 31 Mar 2005 20:46:31 +0200 Christoph Gysin <[EMAIL PROTECTED]>
wrote:
| Juergen Fiedler wrote:
| > If you really feel the need to cram it all onto one line, you could
| > #CFLAGS="whatever" && CXXFLAGS=CFLAGS && emerge something
|
| without the typo and even smaller:
| # CFLAGS="whatever"
On Thu, 31 Mar 2005, Aaron Walker wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Nick Rout wrote:
> > I thought perhaps
> >
> > CFLAGS="whatever" CXXFLAGS="${CFLAGS}" emerge foo
> >
> > no doubt some dev guru will tell me I am way out of line :-)
>
> wrong! there's nothing wrong with
On Thu, 31 Mar 2005, Aaron Walker wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Nick Rout wrote:
> > I thought perhaps
> >
> > CFLAGS="whatever" CXXFLAGS="${CFLAGS}" emerge foo
> >
> > no doubt some dev guru will tell me I am way out of line :-)
>
> wrong! there's nothing wrong with
> There may not be nothing wrong with it, but it is nevertheless almost as
> crappy way to do it. This is because the next time the package with custom
> CFLAGS gets updated as part of a world/system update, it will be emerged
> with the default CFLAGS again...
In these cases it is better to manag
On Friday 01 April 2005 04:07, Ciaran McCreesh wrote:
> On Thu, 31 Mar 2005 20:46:31 +0200 Christoph Gysin <[EMAIL PROTECTED]>
>
> wrote:
> | Juergen Fiedler wrote:
> | > If you really feel the need to cram it all onto one line, you could
> | > #CFLAGS="whatever" && CXXFLAGS=CFLAGS && emerge someth
I thought perhaps
CFLAGS="whatever" CXXFLAGS="${CFLAGS}" emerge foo
no doubt some dev guru will tell me I am way out of line :-)
On Wed, 30 Mar 2005 23:14:48 +0200
Antonio Coralles wrote:
> How can I tell portage to use specific CFLAGS for a particular package
> without temporary changing my
11 matches
Mail list logo
