On Sat, Dec 02, 2017 at 11:23:10PM -0800, Manuel McLure wrote
> Here's the situation. I have a system that's been running for many years
> with an Athlon 5050e processor. The system is built with
>
> CFLAGS="-march=k8-sse3 -O2 -pipe -msse3"
> CPU_FLAGS_X86="3dnow 3dnowext mmx mmxext sse sse2 sse3"
On Sun, Dec 3, 2017 at 3:43 PM, wrote:
> Hi,
>
> I started emerge -e @world
>
> and it stops with this message:
>
> The following mask changes are necessary to proceed:
> (see "package.unmask" in the portage(5) man page for more details)
> # required by @selected
> # required by @world (argument
On Sunday, 3 December 2017 04:15:25 GMT Heiko Baums wrote:
> Like I said before. emerge always calculates the dependency tree, which
> is a lot faster in case of `emerge -e @world` than in case of `emerge
> -uDN @world`. And then it knows which packages have already been
> installed and which are
On Sun, 3 Dec 2017 04:45:59 +0100, tu...@posteo.de wrote:
> Suppose one would do an emerge @world...and then BOOOM! a powerfailyre
> would stop the whole thing. Further suppose the filesystem, the
> hardware and anything has survived luckily -- only emerge @world needs
> to be restarted.
> And one
On Saturday, 2 December 2017 12:30:57 GMT Mick wrote:
> I'm getting this error after I changed my profile as per
> '2017-11-30-new-17-
> profiles' news item:
> >>> Compiling source in /data/tmp_var/portage/sys-boot/grub-0.97-r16/work/
[...]
> However, sys-boot/grub-0.97-r17 installed fine once ke
Am Sun, 03 Dec 2017 09:53:21 +
schrieb Peter Humphrey :
> On Sunday, 3 December 2017 04:15:25 GMT Heiko Baums wrote:
>
> > Like I said before. emerge always calculates the dependency tree,
> > which is a lot faster in case of `emerge -e @world` than in case of
> > `emerge -uDN @world`. And th
Heiko Baums wrote:
> Am Sun, 03 Dec 2017 09:53:21 +
> schrieb Peter Humphrey :
>
>> On Sunday, 3 December 2017 04:15:25 GMT Heiko Baums wrote:
>>
>>> Like I said before. emerge always calculates the dependency tree,
>>> which is a lot faster in case of `emerge -e @world` than in case of
>>> `em
On 2017/12/03 at 06:55am, Dale wrote:
> I think I get what you are saying. If for example you start a
> emerge -e world, a emerge -uDN world or something and then stop it
> before it finishes, running emerge --resume should pick up where you
> left off.
Another helpful option, which I don't thi
On 12/03 09:09, Spackman, Chris wrote:
> On 2017/12/03 at 06:55am, Dale wrote:
>
> > I think I get what you are saying. If for example you start a
> > emerge -e world, a emerge -uDN world or something and then stop it
> > before it finishes, running emerge --resume should pick up where you
> > l
Am Sun, 3 Dec 2017 06:55:59 -0600
schrieb Dale :
> I hope I understood what you meant with all this. I disturbed quite a
> few electrons and stuff with this. lol
I think you understood what I meant even if I didn't think about doing
some other stuff with emerge in between another emerge. And I
Am Sun, 3 Dec 2017 09:09:37 -0500
schrieb "Spackman, Chris" :
> emerge --resume --skipfirst
`emerge --resume --skipfirst` is necessary if you don't use --keep-going
y, a package fails to build and you want to manually resume the actual
emerge. Not using --skipfirst wouldn't make much sense, becau
Am Sun, 3 Dec 2017 15:16:26 +0100
schrieb tu...@posteo.de:
> what is about emerge -e @world --keep-going
> instead?
That would do something like a --resume --skipfirst automatically with
the difference that it first recalculates the dependency tree in case
another package would depend on the pac
On 03-12-2017 ,10:57:33, Peter Humphrey wrote:
> On Saturday, 2 December 2017 12:30:57 GMT Mick wrote:
> > I'm getting this error after I changed my profile as per
> > '2017-11-30-new-17-
> > profiles' news item:
> > >>> Compiling source in /data/tmp_var/portage/sys-boot/grub-0.97-r16/work/
>
> [.
On Sunday, 3 December 2017 14:39:31 GMT Heiko Baums wrote:
> Am Sun, 3 Dec 2017 15:16:26 +0100
>
> schrieb tu...@posteo.de:
> > what is about emerge -e @world --keep-going
> > instead?
>
> That would do something like a --resume --skipfirst automatically with
> the difference that it first recalc
On Sun, 3 Dec 2017 15:39:31 +0100, Heiko Baums wrote:
> But it's actually "--keep-going y".
y is the default, so "--keep-going" and "--keep-going y" do the same
thing.
--
Neil Bothwick
Drive not ready: (R)etry (G)o to Impulse (C)all Engineering
pgpAV8PgaVH97.pgp
Description: OpenPGP digital
On 2017-12-03 06:46, Heiko Baums wrote:
> 1. It can't find >=sys-devel/gcc-6.4.0 but only older gcc versions.
>
> 2. You have installed a package that depend on sys-devel/gcc-5.4.0-r3
> or sys-devel/gcc-4.9.4.
>
> I already explained what you can do in the first case. In the second
> case I woul
On 17-12-03 at 09:52, Ian Zimmerman wrote:
> On 2017-12-03 06:46, Heiko Baums wrote:
>
> > 1. It can't find >=sys-devel/gcc-6.4.0 but only older gcc versions.
> >
> > 2. You have installed a package that depend on sys-devel/gcc-5.4.0-r3
> > or sys-devel/gcc-4.9.4.
> >
> > I already explained wha
Hi,
is there any way to check, whether a compilated binary is using
the position-independant-code feature or is still build according
to old standards?
Cheers
Meino
Well, I moved to the new profile and started emerging gcc on about eight
computers or so. I use distcc to speed up the compile process on the
slower machines, so I need to keep the versions in sync.
I forgot to prefix `emerge -1 gcc` with `FEATURES="-distcc"` and am
wondering if the sys-devel/
You can use app-admin/checksec to see if different security features are
enabled or not.
On Sun, Dec 3, 2017 at 8:06 PM, wrote:
> Hi,
>
> is there any way to check, whether a compilated binary is using
> the position-independant-code feature or is still build according
> to old standards?
>
> Ch
Hi,
>From the news I did everything to switch to the 17th profile EXCEPT
emerge -e @world.
One application which was recompiled was gcc-7.20.
>From my undertsand/point of view gcc now has to have the PIE-feature
gcc-bin/7.2.0>l
total 6676
lrwxrwxrwx 1 root root 23 2017-12-02 16:36 c++ -> x
On 2017-12-03 18:58, Simon Thelen wrote:
> Palemoon builds fine with gcc 6.4.0 (just not with gcc 7.2.0), if the
> ebuild you're using requires an older gcc it's either wrong or doing
> something weird.
It builds, but the result binary crashes every 10 minutes. Have you
tried it?
The ebuild fro
Am Sonntag, 3. Dezember 2017, 19:56:19 CET schrieb tu...@posteo.de:
> Hi,
>
> From the news I did everything to switch to the 17th profile EXCEPT
> emerge -e @world.
>
> One application which was recompiled was gcc-7.20.
>
> From my undertsand/point of view gcc now has to have the PIE-feature
>
On 17-12-03 at 12:06, Ian Zimmerman wrote:
> On 2017-12-03 18:58, Simon Thelen wrote:
>
> > Palemoon builds fine with gcc 6.4.0 (just not with gcc 7.2.0), if the
> > ebuild you're using requires an older gcc it's either wrong or doing
> > something weird.
> It builds, but the result binary crashes
On 12/03/17 10:29, Daniel Frey wrote:
Well, I moved to the new profile and started emerging gcc on about eight
computers or so. I use distcc to speed up the compile process on the
slower machines, so I need to keep the versions in sync.
I forgot to prefix `emerge -1 gcc` with `FEATURES="-distc
On 2017-12-03 22:45, Simon Thelen wrote:
> It might be that palemoon has issues with certain
> optimizations/instruction sets that are aggravated by using newer gcc
> versions (which could turn on optimizations by default etc).
Yes, this is my provisional explanation too.
> I tried checking when
Heiko Baums wrote:
> Am Sun, 3 Dec 2017 06:55:59 -0600
> schrieb Dale :
>
>> I hope I understood what you meant with all this. I disturbed quite a
>> few electrons and stuff with this. lol
> I think you understood what I meant even if I didn't think about doing
> some other stuff with emerge in b
Am Sun, 3 Dec 2017 19:08:25 -0600
schrieb Dale :
> I hope that makes sense because it can be rather complicated if it
> doesn't click as to what I'm describing.
It does.
> Based on all the threads, I'm sticking with the old profile until next
> week or maybe two weeks. Let some of this settle.
On Mon, Dec 04, 2017 at 02:18:30AM +0100, Heiko Baums wrote
> Some packages already failed to build but I don't know yet which. But
> usually `emerge --keep-going` prints a list of the failed packages at
> the end.
If you've got it set up, try...
ll -rt /var/log/portage/elog/
--
Walter Dnes
Hi,
what could fail, when doing the change to PIE-enabled applications
on base of the regular updates?
Compilation may fail, if libs are included and not flagged as to be
recompiled, which are of the "old standard"...
What else can fail? What may be the worst scenario?
Is there a way to do a "eme
tu...@posteo.de wrote:
> Hi,
>
> what could fail, when doing the change to PIE-enabled applications
> on base of the regular updates?
> Compilation may fail, if libs are included and not flagged as to be
> recompiled, which are of the "old standard"...
> What else can fail? What may be the worst sc
31 matches
Mail list logo
