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/
grub-0.97 ...
make -j5 -l12.8
make all-recursive
make[1]: Entering directory '/data/tmp_var/portage/sys-boot/grub-0.97-r16/
FYI :
Since the profile change, 2 versions of net-libs/webkit-gtk began
failing to compile.
net-libs/webkit-gtk-2.18.3:4
net-libs/webkit-gtk-2.4.11-r200:2
Both had the same failures. JavaScript support related.
-
net-libs/webkit-gtk-2.4.11-r1:3 did compile.
Corbin
app-cdr/cdrdao-1.2.3-r4 also fails to install:
[snip ...]
Making all in utils
make[2]: Entering directory '/var/tmp/portage/app-cdr/cdrdao-1.2.3-r4/work/
cdrdao-1.2.3/utils'
x86_64-pc-lin
On 12/02/2017 07:15 AM, Mick wrote:
> app-cdr/cdrdao-1.2.3-r4 also fails to install:
>
> [snip ...]
> Making all in utils
>
> make[2]: Entering directory '/var/tmp/portage/app-cdr/cdrdao-1
On Saturday, 2 December 2017 15:12:51 GMT Corbin wrote:
> Just for the sake of curiosity ...
>
> Have you tried to compile with this
>
> CPPFLAGS="-D_GLIBCXX_USE_CXX11_ABI=1"
>
> added to make.conf ?
I've added this to the command line and it failed at the same point - see
below.
> The reaso
On Saturday, 2 December 2017 13:15:58 GMT Mick wrote:
> app-cdr/cdrdao-1.2.3-r4 also fails to install:
[snip ...]
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../x86_64-pc-linux-gnu/bin
> /ld: toc2mp3-toc2mp3.o: warning: relocation against `bitrate_table' in
> readonly section `.text.startu
On Sat, Dec 2, 2017 at 8:15 AM, Mick wrote:
> app-cdr/cdrdao-1.2.3-r4 also fails to install:
>
> [snip ...]
> Making all in utils
> make[2]: Entering directory '/var/tmp/portage/app-cdr/cdrdao-1.2.3-r4/work/
> cdrdao-1.2.3/utils'
> x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I../trackdb-
This profile change seems to have hit a few people in sensitive
locations.
What is the upshot of this change? Can I eyeball the diff _before_ I
sync ?
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_
On 02-12-2017 ,13:28:37, Ian Zimmerman wrote:
> This profile change seems to have hit a few people in sensitive
> locations.
>
> What is the upshot of this change? Can I eyeball the diff _before_ I
> sync ?
This is what the news item states:
=
~ $ eselect news rea
On 12/02/2017 04:28 PM, Ian Zimmerman wrote:
> This profile change seems to have hit a few people in sensitive
> locations.
>
> What is the upshot of this change? Can I eyeball the diff _before_ I
> sync ?
>
The new 17.0 profile switches the default C++ version to C++14, and
enables PIE/SSP by
Am Sat, 2 Dec 2017 18:33:09 -0500
schrieb Michael Orlitzky :
> You're seeing a lot of reports because there is a news item telling
> people to switch to the new profile and run "emerge -e @world".
Does this mean that "emerge -e @world" should be run or that the news
item is wrong in this point?
On 12/02/2017 08:07 PM, Heiko Baums wrote:
> Am Sat, 2 Dec 2017 18:33:09 -0500
> schrieb Michael Orlitzky :
>
>> You're seeing a lot of reports because there is a news item telling
>> people to switch to the new profile and run "emerge -e @world".
>
> Does this mean that "emerge -e @world" should
> * Select the new profile with eselect
> * Re-emerge, in this sequence, gcc, binutils, and glibc
> emerge -1 sys-devel/gcc:6.4.0
> emerge -1 sys-devel/binutils
> emerge -1 sys-libs/glibc
> * Rebuild your entire system
> emerge -e @world
>
Would emerge -e --exclude gcc --exclude bi
Hi,
the instruction of the news item about the swicth to profile 17 says
that one needs to rebuild @world.
Is this technically needed?
Would it be possible to do this on base of the daily updates intead
all in one go?
Background: I simply need my PC more often as it would allow me
to wait (and f
On 2017-12-02 20:14, Michael Orlitzky wrote:
> >> You're seeing a lot of reports because there is a news item telling
> >> people to switch to the new profile and run "emerge -e @world".
> >
> > Does this mean that "emerge -e @world" should be run or that the
> > news item is wrong in this point?
On 12/02/2017 09:18 PM, Ian Zimmerman wrote:
>>
>> You do need to run "emerge -e @world", unless you happened to be using
>> a hardened toolchain already.
>
> But only if you in fact switch the new profile on, right?
Right.
> There seems to be another thing afoot, though. All (or nearly so)
>
On 12/02/2017 09:15 PM, tu...@posteo.de wrote:
> Hi,
>
> the instruction of the news item about the swicth to profile 17 says
> that one needs to rebuild @world.
>
> Is this technically needed?
Yes, unless you were already using a hardened toolchain.
> Would it be possible to do this on base o
On Sun, Dec 3, 2017 at 1:30 PM, Michael Orlitzky wrote:
> On 12/02/2017 09:15 PM, tu...@posteo.de wrote:
> > Hi,
> >
> > the instruction of the news item about the swicth to profile 17 says
> > that one needs to rebuild @world.
> >
> > Is this technically needed?
>
> Yes, unless you were already
On 12/02/2017 09:32 PM, Adam Carter wrote:
>
> Does having the hardened USE flag enabled = having a hardened toolchain?
If only it were that simple... what you really need to know is, did you
build everything on your system with PIE enabled?
* Some packages have "pie" USE flags, and it's only
On 12/02 09:30, Michael Orlitzky wrote:
> On 12/02/2017 09:15 PM, tu...@posteo.de wrote:
> > Hi,
> >
> > the instruction of the news item about the swicth to profile 17 says
> > that one needs to rebuild @world.
> >
> > Is this technically needed?
>
> Yes, unless you were already using a hardene
Am Sun, 3 Dec 2017 04:26:55 +0100
schrieb tu...@posteo.de:
> If the compilation will fail at a certain point (and it will fail,
> since this is a complete new thing) -- would it be possible to resume
> even some tweaks, hacks and patches (even certain recompilations)
> would be needed in between?
On 12/03 04:35, Heiko Baums wrote:
> Am Sun, 3 Dec 2017 04:26:55 +0100
> schrieb tu...@posteo.de:
>
> > If the compilation will fail at a certain point (and it will fail,
> > since this is a complete new thing) -- would it be possible to resume
> > even some tweaks, hacks and patches (even certain
Am Sun, 3 Dec 2017 04:26:55 +0100
schrieb tu...@posteo.de:
> Delaying would not solve the problem as it is...
Btw., if you're using the testing tree (e.g. ~amd64) you should do a gcc
upgrade instead of rebuilding gcc as the news item says.
Unfortunately the news item explicitly mentions gcc-6.4.
Am Sun, 3 Dec 2017 04:45:59 +0100
schrieb tu...@posteo.de:
> Suppose one would do an emerge @world...and then BOOOM! a powerfailyre
> would stop the whole thing.
In such a case you should consider buying a UPS.
Can't you do this over night or a weekend? And how often do you have a
power failure?
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)
# /usr/portage/profiles/releases/17.0/package.mask:
# An
Am Sun, 3 Dec 2017 05:43:39 +0100
schrieb tu...@posteo.de:
> 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
> # requir
> How can I check, whether a binary is "PIE"-conform ("pie-conform" is
> a freaky funny language hack :) ;) ) ?
>
emerge hardening-check
# hardening-check /usr/bin/cpuid2cpuflags
/usr/bin/cpuid2cpuflags:
Position Independent Executable: yes
Stack protected: yes
Fortify Source functions: yes
On 12/03 06:16, Heiko Baums wrote:
> Am Sun, 3 Dec 2017 05:43:39 +0100
> schrieb tu...@posteo.de:
>
> > 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 pa
Am Sun, 3 Dec 2017 06:29:29 +0100
schrieb tu...@posteo.de:
> I already did this...
There are two things which emerge can tell you with this message.
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-d
Heiko Baums wrote:
> Am Sun, 3 Dec 2017 06:29:29 +0100
> schrieb tu...@posteo.de:
>
>> I already did this...
> There are two things which emerge can tell you with this message.
>
> 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
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"
I have the possibility of upgrading the system to a first-generation I
On Sun, Dec 3, 2017 at 2:23 AM, 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"
>
> I ha
32 matches
Mail list logo
