FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Development

 
 
LinkBack Thread Tools
 
Old 08-08-2010, 07:57 AM
Petteri Räty
 
Default Add --hash-style=gnu to LDFLAGS

On 08/08/2010 03:21 AM, Markos Chandras wrote:
> On Sat, Aug 07, 2010 at 05:15:04PM -0700, Alec Warner wrote:
>>
>> Why not just set some LDFLAGS that totally won't work (-Wl, taters)
>> and then assume anything that actually compiles with those flags set
>> does not respect LDFLAGS. Set that up on a tinderbox instead of
>> making users do it.
>>
>> -A
> Alec
>
> I was only talking about the *dev* profiles. As I said this will help
> *developers* to track this problem and fix it before they commit their
> packages to tree. Tinderbox will only catch packages that are already in the
> tree. The main goal here is to fix these packages before they reach it
>

I suggest making the dev profiles just pull in a binutils version that
automatically enables the support (excluding profiles where binutils is
not used).

Regards,
Petteri
 
Old 08-08-2010, 08:37 AM
Ryan Hill
 
Default Add --hash-style=gnu to LDFLAGS

On Sun, 08 Aug 2010 10:57:34 +0300
Petteri Räty <betelgeuse@gentoo.org> wrote:

> I suggest making the dev profiles just pull in a binutils version that
> automatically enables the support (excluding profiles where binutils is
> not used).

Cutting off a portion of binutils versions in the tree to developers
does not seem like a good idea to me.

How about just putting a check in targets/developer/profile.bashrc
and suggesting people enable it if they can?


--
fonts, gcc-porting, and it's all by design
toolchain, wxwidgets to keep us from losing our minds
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
 
Old 08-08-2010, 11:12 AM
Markos Chandras
 
Default Add --hash-style=gnu to LDFLAGS

On Sun, Aug 08, 2010 at 02:19:05AM +0200, Diego Elio Pettenò wrote:
> Il giorno dom, 08/08/2010 alle 03.11 +0300, Markos Chandras ha scritto:
> > We could at least enable that on x86/amd64 dev profiles (since only
> > devs are
> > supposed to use them and they are the most used arches among us) just
> > to get some more
> > feedback and fix the packages before they reach the end users. This
> > will
> > reduce the bug # and make sure that --as-needed is respected in a
> > broader
> > range of packages
>
> I've set it out on the tinderbox, I can start reporting bugs from
> there... the problem is: _who_ is going to look at them?
I 've already started fixing those bugs myself but the real goal here is to
poke maintainers fix them before they commit their packages to the tree. Thats
the whole point of this thread.

--
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
Key ID: 441AC410
Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410
 
Old 08-08-2010, 11:14 AM
Markos Chandras
 
Default Add --hash-style=gnu to LDFLAGS

On Sat, Aug 07, 2010 at 10:16:24PM -0400, Mike Frysinger wrote:
> obviously you only mean linux x86/amd64 dev profiles. i dont have a strong
> opinion on that small subset in either direction.
> -mike
Yes, sorry I only meant the linux profiles


--
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
Key ID: 441AC410
Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410
 
Old 08-09-2010, 11:03 PM
Markos Chandras
 
Default Add --hash-style=gnu to LDFLAGS

On Sat, Aug 07, 2010 at 10:16:24PM -0400, Mike Frysinger wrote:
>
> obviously you only mean linux x86/amd64 dev profiles. i dont have a strong
> opinion on that small subset in either direction.
> -mike

So do you agree to make this linker option default to linux x86/amd64 dev/
profiles?

I don't know how many dev are using those 2 profiles, but if there are no
objections I will add it in 72 hours

Thanks

--
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
Key ID: 441AC410
Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410
 
Old 08-09-2010, 11:05 PM
Mike Frysinger
 
Default Add --hash-style=gnu to LDFLAGS

On Mon, Aug 9, 2010 at 7:03 PM, Markos Chandras wrote:
> On Sat, Aug 07, 2010 at 10:16:24PM -0400, Mike Frysinger wrote:
>> obviously you only mean linux x86/amd64 dev profiles. *i dont have a strong
>> opinion on that small subset in either direction.
>
> So do you agree to make this linker option default to linux x86/amd64 dev/
> profiles?

add them or dont add them, "i dont have a [...] opinion [...] in
either direction". if put to a vote, i'd abstain.
-mike
 
Old 08-10-2010, 08:45 AM
Brian Harring
 
Default Add --hash-style=gnu to LDFLAGS

On Mon, Aug 09, 2010 at 07:05:11PM -0400, Mike Frysinger wrote:
> On Mon, Aug 9, 2010 at 7:03 PM, Markos Chandras wrote:
> > On Sat, Aug 07, 2010 at 10:16:24PM -0400, Mike Frysinger wrote:
> >> obviously you only mean linux x86/amd64 dev profiles. *i dont have a strong
> >> opinion on that small subset in either direction.
> >
> > So do you agree to make this linker option default to linux x86/amd64 dev/
> > profiles?
>
> add them or dont add them, "i dont have a [...] opinion [...] in
> either direction". if put to a vote, i'd abstain.

Possibly a stupid question, but any reason we've not looked at
injecting something that has lower actual affect but can still be used
for a canary? I'm thinking of --build-id specifically...

~brian
 
Old 08-10-2010, 06:40 PM
Francesco R
 
Default Add --hash-style=gnu to LDFLAGS

2010/8/10 Brian Harring <ferringb@gmail.com>

On Mon, Aug 09, 2010 at 07:05:11PM -0400, Mike Frysinger wrote:

> On Mon, Aug 9, 2010 at 7:03 PM, Markos Chandras wrote:

> > On Sat, Aug 07, 2010 at 10:16:24PM -0400, Mike Frysinger wrote:

> >> obviously you only mean linux x86/amd64 dev profiles. *i dont have a strong

> >> opinion on that small subset in either direction.

> >

> > So do you agree to make this linker option default to linux x86/amd64 dev/

> > profiles?

>

> add them or dont add them, "i dont have a [...] opinion [...] in

> either direction". *if put to a vote, i'd abstain.



Possibly a stupid question, but any reason we've not looked at

injecting something that has lower actual affect but can still be used

for a canary? *I'm thinking of --build-id specifically...



~brian

I don't know how*--hash-style=gnu is used to check for LDFLAGS, so this may be OT.
On my personal and _breakable_ desktop I do use
LDFLAGS="${LDFLAGS} -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,--sort-common -Wl,--build-id"in make.conf.
Would this two liners tell me which package who install binaries in /usr/bin does not respect ldflags?

# for i in /usr/bin/* ; do eu-unstrip -n -e *$i ; done &> build-id.txt# qfile $(grep '0x[0-9]*+0x[0-9]* - ' build-id.txt | awk '{ print $3 }')

On a side note, I've noticed that build-id change at every re-compilation of the package, even if nothing changed in the system, since it's supposed to be a "160-bit SHA1 hash on the normative parts of the output contents" should it be the same if the package is compiled on the same system with no changes?

Output of the two liners for this system:
sys-apps/turbotail (/usr/bin/turbotail)app-arch/rzip (/usr/bin/runzip)app-arch/rzip (/usr/bin/rzip)dev-lang/go (/usr/bin/6a)
dev-lang/go (/usr/bin/6cov)dev-lang/go (/usr/bin/6l)dev-lang/go (/usr/bin/6nm)dev-lang/xharbour (/usr/bin/pprun)dev-lang/xharbour (/usr/bin/hbmake)dev-lang/xharbour (/usr/bin/hbdict)
dev-lang/xharbour (/usr/bin/xbscript)dev-lang/perl (/usr/bin/perl)dev-lang/perl (/usr/bin/perl5.12.1)dev-lang/R (/usr/bin/Rscript)x11-misc/xcb (/usr/bin/xcb)dev-libs/dietlibc (/usr/bin/dnsd)
dev-libs/dietlibc (/usr/bin/elftrunc)app-text/o3read (/usr/bin/utf8tolatin1)app-accessibility/festival (/usr/bin/audsp)app-accessibility/espeak (/usr/bin/espeak)sys-devel/gcc (/usr/bin/x86_64-pc-linux-gnu-gcjh-4.4.4)
sys-devel/gcc (/usr/bin/gcjh-4.4.4)sys-devel/llvm-gcc (/usr/bin/llvm-gcov)sys-devel/qconf (/usr/bin/qconf)www-plugins/lightspark (/usr/bin/lightspark)*
 
Old 08-10-2010, 06:40 PM
Francesco R
 
Default Add --hash-style=gnu to LDFLAGS

2010/8/10 Brian Harring <ferringb@gmail.com>

On Mon, Aug 09, 2010 at 07:05:11PM -0400, Mike Frysinger wrote:

> On Mon, Aug 9, 2010 at 7:03 PM, Markos Chandras wrote:

> > On Sat, Aug 07, 2010 at 10:16:24PM -0400, Mike Frysinger wrote:

> >> obviously you only mean linux x86/amd64 dev profiles. *i dont have a strong

> >> opinion on that small subset in either direction.

> >

> > So do you agree to make this linker option default to linux x86/amd64 dev/

> > profiles?

>

> add them or dont add them, "i dont have a [...] opinion [...] in

> either direction". *if put to a vote, i'd abstain.



Possibly a stupid question, but any reason we've not looked at

injecting something that has lower actual affect but can still be used

for a canary? *I'm thinking of --build-id specifically...



~brian

I don't know how*--hash-style=gnu is used to check for LDFLAGS, so this may be OT.
On my personal and _breakable_ desktop I do use
LDFLAGS="${LDFLAGS} -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,--sort-common -Wl,--build-id"in make.conf.
Would this two liners tell me which package who install binaries in /usr/bin does not respect ldflags?

# for i in /usr/bin/* ; do eu-unstrip -n -e *$i ; done &> build-id.txt# qfile $(grep '0x[0-9]*+0x[0-9]* - ' build-id.txt | awk '{ print $3 }')

On a side note, I've noticed that build-id change at every re-compilation of the package, even if nothing changed in the system, since it's supposed to be a "160-bit SHA1 hash on the normative parts of the output contents" should it be the same if the package is compiled on the same system with no changes?

Output of the two liners for this system:
sys-apps/turbotail (/usr/bin/turbotail)app-arch/rzip (/usr/bin/runzip)app-arch/rzip (/usr/bin/rzip)dev-lang/go (/usr/bin/6a)
dev-lang/go (/usr/bin/6cov)dev-lang/go (/usr/bin/6l)dev-lang/go (/usr/bin/6nm)dev-lang/xharbour (/usr/bin/pprun)dev-lang/xharbour (/usr/bin/hbmake)dev-lang/xharbour (/usr/bin/hbdict)
dev-lang/xharbour (/usr/bin/xbscript)dev-lang/perl (/usr/bin/perl)dev-lang/perl (/usr/bin/perl5.12.1)dev-lang/R (/usr/bin/Rscript)x11-misc/xcb (/usr/bin/xcb)dev-libs/dietlibc (/usr/bin/dnsd)
dev-libs/dietlibc (/usr/bin/elftrunc)app-text/o3read (/usr/bin/utf8tolatin1)app-accessibility/festival (/usr/bin/audsp)app-accessibility/espeak (/usr/bin/espeak)sys-devel/gcc (/usr/bin/x86_64-pc-linux-gnu-gcjh-4.4.4)
sys-devel/gcc (/usr/bin/gcjh-4.4.4)sys-devel/llvm-gcc (/usr/bin/llvm-gcov)sys-devel/qconf (/usr/bin/qconf)www-plugins/lightspark (/usr/bin/lightspark)*
 
Old 08-10-2010, 06:40 PM
Francesco R
 
Default Add --hash-style=gnu to LDFLAGS

2010/8/10 Brian Harring <ferringb@gmail.com>

On Mon, Aug 09, 2010 at 07:05:11PM -0400, Mike Frysinger wrote:

> On Mon, Aug 9, 2010 at 7:03 PM, Markos Chandras wrote:

> > On Sat, Aug 07, 2010 at 10:16:24PM -0400, Mike Frysinger wrote:

> >> obviously you only mean linux x86/amd64 dev profiles. *i dont have a strong

> >> opinion on that small subset in either direction.

> >

> > So do you agree to make this linker option default to linux x86/amd64 dev/

> > profiles?

>

> add them or dont add them, "i dont have a [...] opinion [...] in

> either direction". *if put to a vote, i'd abstain.



Possibly a stupid question, but any reason we've not looked at

injecting something that has lower actual affect but can still be used

for a canary? *I'm thinking of --build-id specifically...



~brian

I don't know how*--hash-style=gnu is used to check for LDFLAGS, so this may be OT.
On my personal and _breakable_ desktop I do use
LDFLAGS="${LDFLAGS} -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,--sort-common -Wl,--build-id"in make.conf.
Would this two liners tell me which package who install binaries in /usr/bin does not respect ldflags?

# for i in /usr/bin/* ; do eu-unstrip -n -e *$i ; done &> build-id.txt# qfile $(grep '0x[0-9]*+0x[0-9]* - ' build-id.txt | awk '{ print $3 }')

On a side note, I've noticed that build-id change at every re-compilation of the package, even if nothing changed in the system, since it's supposed to be a "160-bit SHA1 hash on the normative parts of the output contents" should it be the same if the package is compiled on the same system with no changes?

Output of the two liners for this system:
sys-apps/turbotail (/usr/bin/turbotail)app-arch/rzip (/usr/bin/runzip)app-arch/rzip (/usr/bin/rzip)dev-lang/go (/usr/bin/6a)
dev-lang/go (/usr/bin/6cov)dev-lang/go (/usr/bin/6l)dev-lang/go (/usr/bin/6nm)dev-lang/xharbour (/usr/bin/pprun)dev-lang/xharbour (/usr/bin/hbmake)dev-lang/xharbour (/usr/bin/hbdict)
dev-lang/xharbour (/usr/bin/xbscript)dev-lang/perl (/usr/bin/perl)dev-lang/perl (/usr/bin/perl5.12.1)dev-lang/R (/usr/bin/Rscript)x11-misc/xcb (/usr/bin/xcb)dev-libs/dietlibc (/usr/bin/dnsd)
dev-libs/dietlibc (/usr/bin/elftrunc)app-text/o3read (/usr/bin/utf8tolatin1)app-accessibility/festival (/usr/bin/audsp)app-accessibility/espeak (/usr/bin/espeak)sys-devel/gcc (/usr/bin/x86_64-pc-linux-gnu-gcjh-4.4.4)
sys-devel/gcc (/usr/bin/gcjh-4.4.4)sys-devel/llvm-gcc (/usr/bin/llvm-gcov)sys-devel/qconf (/usr/bin/qconf)www-plugins/lightspark (/usr/bin/lightspark)*
 

Thread Tools




All times are GMT. The time now is 09:33 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org