On Saturday 15 August 2009 19:37:05 Dirk Heinrichs wrote:
Am Samstag 15 August 2009 19:24:09 schrieb Nikos Chantziaras:
system has to be rebuilt twice. When you get a new toolchain
(system), you need to rebuilt it with itself. The first time you do
that, it is rebuilt using the *old*
On Saturday 15 August 2009 02:33:56 fe...@crowfix.com wrote:
This being 4.3.4 to 4.1.1 looks like a major version change according
to the upgrade guide. It doesn't mention what a switch manual takes,
but it does list a whole series of steps such as remerging system and
world without saying
On Sat, Aug 15, 2009 at 8:50 AM, Alan McKinnonalan.mckin...@gmail.com wrote:
On Saturday 15 August 2009 02:33:56 fe...@crowfix.com wrote:
This being 4.3.4 to 4.1.1 looks like a major version change according
to the upgrade guide. It doesn't mention what a switch manual takes,
but it does list
On Fri, Aug 14, 2009 at 5:43 PM, Nikos Chantziarasrea...@arcor.de wrote:
On 08/15/2009 03:33 AM, fe...@crowfix.com wrote:
[...]
This being 4.3.4 to 4.1.1 looks like a major version change according
to the upgrade guide. It doesn't mention what a switch manual takes,
but it does list a whole
On 08/15/2009 07:42 PM, Mark Knecht wrote:
[...]
I agree with your description, but I disagree that the upgrade
guide is actually very clear about this. It has us upgrade the
compiler (OK), switch to the new compiler (OK), rebuild the libtool
stuff (OK) then then states:
On 08/15/2009 07:48 PM, Mark Knecht wrote:
On Fri, Aug 14, 2009 at 5:43 PM, Nikos Chantziarasrea...@arcor.de wrote:
[...]
I am doing an emerge -e system and emerge -e world anyway though since I
want to take advantage of the faster code 4.4 produces in general, but also
more specific whether
Am Samstag 15 August 2009 18:42:11 schrieb Mark Knecht:
Code Listing 2.2: Rebuilding system
# emerge -eav system
# emerge -eav world
I still wonder about this one. Doesn't world include system, so that the above
would result in rebuilding a vast amount of packages twice?
Bye...
Nikos Chantziaras wrote:
On 08/15/2009 03:33 AM, fe...@crowfix.com wrote:
[...] This being 4.3.4 to 4.1.1 looks like a major version change
according to the upgrade guide. It doesn't mention what a switch
manual takes, but it does list a whole series of steps such as
remerging system and
On Sat, Aug 15, 2009 at 9:49 AM, Nikos Chantziarasrea...@arcor.de wrote:
On 08/15/2009 07:42 PM, Mark Knecht wrote:
[...]
I agree with your description, but I disagree that the upgrade
guide is actually very clear about this. It has us upgrade the
compiler (OK), switch to the new compiler
On Sat, Aug 15, 2009 at 10:06 AM, Dirk
Heinrichsdirk.heinri...@online.de wrote:
Am Samstag 15 August 2009 18:42:11 schrieb Mark Knecht:
Code Listing 2.2: Rebuilding system
# emerge -eav system
# emerge -eav world
I still wonder about this one. Doesn't world include system, so that the above
On Saturday 15 August 2009 18:42:11 Mark Knecht wrote:
Alan,
I agree with your description, but I disagree that the upgrade
guide is actually very clear about this. It has us upgrade the
compiler (OK), switch to the new compiler (OK), rebuild the libtool
stuff (OK) then then states:
On 08/15/2009 08:06 PM, Dirk Heinrichs wrote:
Am Samstag 15 August 2009 18:42:11 schrieb Mark Knecht:
Code Listing 2.2: Rebuilding system
# emerge -eav system
# emerge -eav world
I still wonder about this one. Doesn't world include system, so that the above
would result in rebuilding a vast
On Saturday 15 August 2009 19:06:54 Dirk Heinrichs wrote:
Am Samstag 15 August 2009 18:42:11 schrieb Mark Knecht:
Code Listing 2.2: Rebuilding system
# emerge -eav system
# emerge -eav world
I still wonder about this one. Doesn't world include system, so that the
above would result in
On Saturday 15 August 2009 19:18:36 Mark Knecht wrote:
I've also done two builds of gcc instead of two @system builds. I
think that accomplishes the same thing, but what do I know as there
are no guarantees! ;-)
Look at gcc's makefiles.
It builds gcc with the old compiler then uses that new
Am Samstag 15 August 2009 19:24:09 schrieb Nikos Chantziaras:
system has to be rebuilt twice. When you get a new toolchain
(system), you need to rebuilt it with itself. The first time you do
that, it is rebuilt using the *old* toolchain. The second time it is
rebuilt using the *new*
Am Samstag 15 August 2009 19:25:39 schrieb Alan McKinnon:
A common misunderstanding is that you have to rebuild gcc twice. This is
not true as gcc's own build system in fact builds gcc three times and does
a binary diff between the last two, the build only proceeds if they are
bit-for- bit
On 08/15/2009 08:07 PM, 7v5w7go9ub0o wrote:
[...]
1. FWIW, I found the following note:
To use this code transformation, GCC has to be configured with
--with-ppl and --with-cloog to enable the Graphite loop transformation
infrastructure.
on the following page:
On 08/15/2009 08:37 PM, Dirk Heinrichs wrote:
Am Samstag 15 August 2009 19:24:09 schrieb Nikos Chantziaras:
system has to be rebuilt twice. When you get a new toolchain
(system), you need to rebuilt it with itself. The first time you do
that, it is rebuilt using the *old* toolchain. The
Nikos Chantziaras wrote:
AFAIK, the mudflap pointer checker is just a command line GCC switch.
You need to enable it explicitly using -fmudflap.
ah o.k. I'm using the hardened overlay, and mudflap is a use flag
defaulting to enabled. I'll post that second comment over in hardened.
On 08/15/2009 09:35 PM, 7v5w7go9ub0o wrote:
Nikos Chantziaras wrote:
AFAIK, the mudflap pointer checker is just a command line GCC switch.
You need to enable it explicitly using -fmudflap.
ah o.k. I'm using the hardened overlay, and mudflap is a use flag
defaulting to enabled. I'll
On 08/15/2009 09:52 PM, Nikos Chantziaras wrote:
[...]
time bzip2 --best /dev/shm/500gb-test-file
More like 500mb-test-file as I don't suppose you have a terrabyte of
RAM :P
On 08/14/2009 04:17 PM, fe...@crowfix.com wrote:
Are any special steps needed to handle this upgrade, other than using
gcc-config to change the current selection? Do I need to follow the
upgrade docs, such as remergeing system and world?
I'm no expert, but I just did the same upgrade this
On Fri, Aug 14, 2009 at 04:29:17PM -0700, walt wrote:
On 08/14/2009 04:17 PM, fe...@crowfix.com wrote:
Are any special steps needed to handle this upgrade, other than using
gcc-config to change the current selection? Do I need to follow the
upgrade docs, such as remergeing system and
On 08/15/2009 03:33 AM, fe...@crowfix.com wrote:
[...]
This being 4.3.4 to 4.1.1 looks like a major version change according
to the upgrade guide. It doesn't mention what a switch manual takes,
but it does list a whole series of steps such as remerging system and
world without saying exactly
24 matches
Mail list logo
