Hi,
I've just noticed that one of the environment variables I (have to) have
set causes troubles with an ebuild.
In my case I have set the environment variable PLATFORM (for my user).
If I now just su to root and then emerge mono the emerge will fail
because mono also seems to make use of
Hi,
I'd like to unmask (-*) certain versions of a package (gcc).
I'd like to keep the defaults for everything but I'd like to unmask
gcc-4.0.1_pre*
I've already tried to unmask
~sys-devel/gcc-4.0.1_pre20050616 -*
and also
~sys-devel/gcc-4.0.1 -*
but it didnt work. The first only only
Hi,
another problem I've just run into:
I'd like to have gcc 3.4.x, 4.0.1_pre* and 4.1.* installed at the same
time. However all gcc-4.* versions do not seem to use different slots
(eg one 4.0.* and one 4.1.* slot).
Is there any way I can force slots without creating my own ebuilds in
the
Edward Catmur wrote:
I'd like to unmask (-*) certain versions of a package (gcc).
I'd like to keep the defaults for everything but I'd like to unmask
gcc-4.0.1_pre*
Try
=sys-devel/gcc-4.0.1* -*
or
=sys-devel/gcc-4.0.1_pre* -*
Remember that ~ only matches -r* revisions of a
Hi,
I'd like to use gcc 4 to compile some of my own software but still use
3.4 for everything else (all ebuilds etc).
Now I simply emerged gcc4 (its slotted) and then as my user I did export
the variables a
gcc-config -E x86_64-pc-linux-gnu-4.0.1-pre20050616
printed out.
This way I
Richard Fish wrote:
Philip Lawatsch wrote:
So my querstion now is what else gets changed by gcc-config, and is
there a chance to have the 3.4 gcc profile selected but still run
programs compiled with gcc 4?
I haven't verified this (try switching configs back and forth to
verify
6 matches
Mail list logo