Alan Grimes wrote:
> Dale wrote:
>> Dale wrote:
>>
>> This is something I have noticed that changed since the gcc upgrade.
>> One, Firefox seems to use less memory. It's not a whole lot less but it
>> is less for sure. It also uses a lot less CPU power. Used to if I had
>> two or three Firefox
Dale wrote:
> Dale wrote:
>
> This is something I have noticed that changed since the gcc upgrade.
> One, Firefox seems to use less memory. It's not a whole lot less but it
> is less for sure. It also uses a lot less CPU power. Used to if I had
> two or three Firefox profiles running, I could s
Dale wrote:
>
> I just did this myself. After I switched to the new gcc, I ran
> revdep-rebuild. It had a large list of packages. I was planning to do
> a emerge -e world anyway, so I just did it instead. No sense doing most
> of it twice. During the rebuild, I had a qt package to fail. For s
Hello list,
I issued this command:
# revdep-rebuild --library 'libstdc++.so.6' -- --exclude="gcc gentoo-
sources" --jobs --load-average=48
...only to find that gentoo-sources was indeed emerged, though gcc wasn't.
What's gone wrong here? I've always found that style of specifying
exclusions to
On 04/25/2017 12:18 PM, Dale wrote:
Frank Steinmetzger wrote:
On Sun, Apr 23, 2017 at 06:59:16PM +0200, Andreas K. Huettel wrote:
My personal advice & experience:
* install the new gcc-5.4
* switch to it
* run the revdep-rebuild command from the news item (see above)
... and everything should
Frank Steinmetzger wrote:
> On Sun, Apr 23, 2017 at 06:59:16PM +0200, Andreas K. Huettel wrote:
>
>> My personal advice & experience:
>> * install the new gcc-5.4
>> * switch to it
>> * run the revdep-rebuild command from the news item (see above)
>> ... and everything should be fine.
> I do rememb
On Sun, Apr 23, 2017 at 06:59:16PM +0200, Andreas K. Huettel wrote:
> My personal advice & experience:
> * install the new gcc-5.4
> * switch to it
> * run the revdep-rebuild command from the news item (see above)
> ... and everything should be fine.
I do remember having seen the item. And I copi
On Mon, Apr 24, 2017 at 04:07:03PM +, J. Roeleveld wrote:
> >> I've had the odd rebuild failure here & there, don't bother re-emerging
> >> it until revdep-rebuild has finished. Any dependencies it needs would
> >> have been rebuilt by then and it should complete without problem.
> Usually a
Philip Webb wrote:
> I've been following the thread re GCC 5.4.0 & after 'eix-sync' installed it.
> There's a news item warning that there's a new ABI
> & it mb necessary to run 'revdep-rebuild' if it fails with a linking error.
>
> The first pkg I tried to compile with 5.4.0 indeed failed at that
On Mon, 24 Apr 2017 14:36:01 +0100, Peter Humphrey wrote:
> Yes, I had too, once. At that time though quite a few packages could
> only be emerged with -j1, so I had to make exceptions for them. It was
> easier just to put the options into an alias:
>
> $ alias emerj='sudo emerge --jobs=24 --load
On Monday 24 Apr 2017 16:45:58 I wrote:
> On Monday 24 Apr 2017 14:47:32 Mick wrote:
> > On Monday 24 Apr 2017 14:36:01 Peter Humphrey wrote:
> > > Speaking of long emerge times, so far this box has spent nearly six
> > > hours on two systems simultaneously (one being a chroot for a slower
> > > ma
On April 24, 2017 5:45:58 PM GMT+02:00, Peter Humphrey
wrote:
>On Monday 24 Apr 2017 14:47:32 Mick wrote:
>> On Monday 24 Apr 2017 14:36:01 Peter Humphrey wrote:
>> > Speaking of long emerge times, so far this box has spent nearly six
>> > hours on two systems simultaneously (one being a chroot f
On Monday 24 Apr 2017 14:47:32 Mick wrote:
> On Monday 24 Apr 2017 14:36:01 Peter Humphrey wrote:
> > Speaking of long emerge times, so far this box has spent nearly six
> > hours on two systems simultaneously (one being a chroot for a slower
> > machine) and still hasn't finished. And qtwebkit has
On Monday 24 Apr 2017 14:47:32 Mick wrote:
> On Monday 24 Apr 2017 14:36:01 Peter Humphrey wrote:
> > Speaking of long emerge times, so far this box has spent nearly six
> > hours on two systems simultaneously (one being a chroot for a slower
> > machine) and still hasn't finished. And qtwebkit has
On Monday 24 Apr 2017 14:36:01 Peter Humphrey wrote:
> Speaking of long emerge times, so far this box has spent nearly six hours on
> two systems simultaneously (one being a chroot for a slower machine) and
> still hasn't finished. And qtwebkit has just failed; I'd better look into
> that.
I've h
On Monday 24 Apr 2017 11:11:09 Marc Joliet wrote:
> Am Montag, 24. April 2017, 10:13:29 CEST schrieb Peter Humphrey:
> > On Sunday 23 Apr 2017 15:26:48 Marc Joliet wrote:
> > > I followed the instructions and everything went fine, albeit it took
> > > about 2 days on my desktop just for the revdep-
Am Montag, 24. April 2017, 10:13:29 CEST schrieb Peter Humphrey:
> On Sunday 23 Apr 2017 15:26:48 Marc Joliet wrote:
> > I followed the instructions and everything went fine, albeit it took about
> > 2 days on my desktop just for the revdep-rebuild.
>
> I couldn't face the prospect of line-by-line
On Sunday 23 Apr 2017 15:26:48 Marc Joliet wrote:
> I followed the instructions and everything went fine, albeit it took about
> 2 days on my desktop just for the revdep-rebuild.
I couldn't face the prospect of line-by-line emerging of 341 packages taking
hours or days, so I added "--jobs=X --l
170423 Andreas K. Huettel wrote:
> Am Sonntag, 23. April 2017, 07:45:49 CEST schrieb Philip Webb:
>> What are other users' experiences using GCC 5.4.0 ?
> My personal advice & experience:
> * install the new gcc-5.4
> * switch to it
> * run the revdep-rebuild command from the news item (see above)
Am Sonntag, 23. April 2017, 18:59:16 CEST schrieb Andreas K. Huettel:
>
> > What are other users' experiences using GCC 5.4.0 ?
>
> My personal advice & experience:
> * install the new gcc-5.4
> * switch to it
> * run the revdep-rebuild command from the news item (see above)
> ... and everything s
Am Sonntag, 23. April 2017, 07:45:49 CEST schrieb Philip Webb:
> I've been following the thread re GCC 5.4.0 & after 'eix-sync' installed it.
> There's a news item warning that there's a new ABI
> & it mb necessary to run 'revdep-rebuild' if it fails with a linking error.
>
> The first pkg I tried
On Sonntag, 23. April 2017 07:45:49 CEST Philip Webb wrote:
> I've been following the thread re GCC 5.4.0 & after 'eix-sync' installed it.
> There's a news item warning that there's a new ABI
> & it mb necessary to run 'revdep-rebuild' if it fails with a linking error.
While it does read like that
> I went back to GCC 4.9.3 & the pkg merged without any problem.
>
> What are other users' experiences using GCC 5.4.0 ?
>
~amd64 users have been using it for ages, with no problems. I have one
system that seems to need me to run ldconfig when i update gcc, but the
others are fine.
On 04/22/2017 10:45 PM, Philip Webb wrote:
> I've been following the thread re GCC 5.4.0 & after 'eix-sync' installed it.
> There's a news item warning that there's a new ABI
> & it mb necessary to run 'revdep-rebuild' if it fails with a linking error.
>
> The first pkg I tried to compile with 5.4
I've been following the thread re GCC 5.4.0 & after 'eix-sync' installed it.
There's a news item warning that there's a new ABI
& it mb necessary to run 'revdep-rebuild' if it fails with a linking error.
The first pkg I tried to compile with 5.4.0 indeed failed at that point,
so I followed the adv
25 matches
Mail list logo
