First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 211160
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Dialup Developers <net-dialup@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Paweł Hajdan jr (ph) <phajdan.jr@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 211160 depends on: Show dependency tree
Bug 211160 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2008-02-23 08:32 0000 
* Messages for package net-dialup/ppp-2.4.4-r14:
* QA: stop using the bindnow-flags function ... simply drop it from your ebuild

I'm not sure if it should really be removed, but that's what the message says.

------- Comment #1 From Alin Năstac 2008-02-23 10:14:49 0000 ------- 
When I tried to remove bindnow-flag, it resulted the mess described in bug
210837. When I will have the time, I will try to fix that without using
bindnow-flags.

------- Comment #2 From Jakub Moc (RETIRED) 2008-02-23 12:25:39 0000 ------- 
Well you can use append-ldflags "-Wl,-z,now" to silence the completely useless
warning that's yet again flooding users for no reason.

On a generic note, seriously when deprecating something it's be nice to provide
a replacement unless/until the feature is totally unneeded -  it's apparently
needed here. 

Things like Bug 210837 Comment #13 with some cryptic notes that it "can be
solved cleanly in the ldso itself" don't help at all. What's the replacement
for bindnow-flags(), i.e. where's this fixed in toolchain? If nowhere (which
pretty much seems to be the case), then we should stop deprecating something
just because we can spit out some funky warnings.

------- Comment #3 From Alin Năstac 2008-04-12 08:37:05 0000 ------- 
Fixed in -r15 by replacing it with -Wl,--allow-shlib-undefined.
First Last Prev Next    No search results available      Search page      Enter new bug