public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Joliet <marcec@gmx.de>
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Am I in trouble now?
Date: Sun, 03 Dec 2017 21:22:23 +0100	[thread overview]
Message-ID: <3161763.dWV9SEqChM@thetick> (raw)
In-Reply-To: <20171203185619.n3ysxkc7bnrfrvxl@solfire>

[-- Attachment #1: Type: text/plain, Size: 3634 bytes --]

Am Sonntag, 3. Dezember 2017, 19:56:19 CET schrieb tuxic@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
> 
> gcc-bin/7.2.0>l
> total 6676
> lrwxrwxrwx 1 root root      23 2017-12-02 16:36 c++ ->
> x86_64-pc-linux-gnu-c++ lrwxrwxrwx 1 root root      23 2017-12-02 16:36 cpp
> -> x86_64-pc-linux-gnu-cpp lrwxrwxrwx 1 root root      23 2017-12-02 16:36
> g++ -> x86_64-pc-linux-gnu-g++ lrwxrwxrwx 1 root root      23 2017-12-02
> 16:36 gcc -> x86_64-pc-linux-gnu-gcc -rwxr-xr-x 2 root root   26896
> 2017-12-02 16:36 gcc-ar
> -rwxr-xr-x 2 root root   26896 2017-12-02 16:36 gcc-nm
> -rwxr-xr-x 2 root root   26896 2017-12-02 16:36 gcc-ranlib
> lrwxrwxrwx 1 root root      24 2017-12-02 16:36 gcov ->
> x86_64-pc-linux-gnu-gcov -rwxr-xr-x 1 root root  495400 2017-12-02 16:36
> gcov-dump
> -rwxr-xr-x 1 root root  515944 2017-12-02 16:36 gcov-tool
> lrwxrwxrwx 1 root root      28 2017-12-02 16:36 gfortran ->
> x86_64-pc-linux-gnu-gfortran -rwxr-xr-x 2 root root 1002192 2017-12-02
> 16:36 x86_64-pc-linux-gnu-c++ -rwxr-xr-x 1 root root  998096 2017-12-02
> 16:36 x86_64-pc-linux-gnu-cpp -rwxr-xr-x 2 root root 1002192 2017-12-02
> 16:36 x86_64-pc-linux-gnu-g++ -rwxr-xr-x 1 root root  998096 2017-12-02
> 16:36 x86_64-pc-linux-gnu-gcc lrwxrwxrwx 1 root root      23 2017-12-02
> 16:36 x86_64-pc-linux-gnu-gcc-7.2.0 -> x86_64-pc-linux-gnu-gcc -rwxr-xr-x 2
> root root   26896 2017-12-02 16:36 x86_64-pc-linux-gnu-gcc-ar -rwxr-xr-x 2
> root root   26896 2017-12-02 16:36 x86_64-pc-linux-gnu-gcc-nm -rwxr-xr-x 2
> root root   26896 2017-12-02 16:36 x86_64-pc-linux-gnu-gcc-ranlib
> -rwxr-xr-x 1 root root  639312 2017-12-02 16:36 x86_64-pc-linux-gnu-gcov
> -rwxr-xr-x 1 root root 1002192 2017-12-02 16:36
> x86_64-pc-linux-gnu-gfortran
> 
> 
> solfire:gcc-bin/7.2.0>checksec --file x86_64-pc-linux-gnu-c++
> RELRO           STACK CANARY      NX            PIE             RPATH     
> RUNPATH	FORTIFY	Fortified Fortifiable  FILE Partial RELRO   Canary found   
>   NX enabled    No PIE          No RPATH   No RUNPATH  
> Yes	8		21	x86_64-pc-linux-gnu-c++
> 
> 
> 
> So...No PIE it says.
> 
> /root #>eselect profile show
> Current /etc/portage/make.profile symlink:
>   default/linux/amd64/17.0/no-multilib
> 
> Before I start the rebuild of 2000++ packages ...
> Is this all correct up to this point?

Keep in mind that the news item literally says:

"2) Where supported, GCC will now build position-independent
   executables (PIE) by default."

Note the "Where supported" bit.  I don't know if that means "CPUs that this 
works with" or "profiles that support this", but it looks like the "pie" USE 
flag is forced globally in the profile and not deactivated in any of its sub-
profiles, so I'm tending to the former.

Of course, that doesn't mean that things are correct on your end, though.  On 
one of my computers, checksec does say "PIE enabled".  Maybe you should try 
compiling something else and verifying it.  After all, there's probably a 
reason why the "emerge -e @world" bit doesn't exclude any of the packages 
previously rebuilt.  I'll try to verify that on my desktop, though, which is 
the one out of three computers I haven't migrated yet -- both my home server 
and laptop have completed their "emerge -e @world" already (thankfully almost, 
but not entirely, without problems).

> Cheers
> Meino

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-12-03 20:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03 18:56 [gentoo-user] Am I in trouble now? tuxic
2017-12-03 20:22 ` Marc Joliet [this message]
2017-12-04 11:58   ` Marc Joliet
2017-12-04 14:40     ` David Haller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3161763.dWV9SEqChM@thetick \
    --to=marcec@gmx.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox