On 7/11/07, Mark Hatle [EMAIL PROTECTED] wrote:
if librpm* has a requirement on librpmmisc, and librpmmisc requires the
libraries (static or shared) it works w/o --as-needed.
No, not really. It may break in the presence of symbol versioning.
Consider this case:
* the developer links librpmmisc
On Wed, Jul 11, 2007, Arkadiusz Miskiewicz wrote:
Try this:
./configure LDFLAGS=-Wl,--as-needed
It will fail miserably because things are not linked properly.
It's like in the patient/doctor joke: Patient: 'Doctor, it hurts when I
do this'. Doctor: 'Well, then just don't do it'...
On Wednesday 11 of July 2007, Ralf S. Engelschall wrote:
On Wed, Jul 11, 2007, Arkadiusz Miskiewicz wrote:
Try this:
./configure LDFLAGS=-Wl,--as-needed
It will fail miserably because things are not linked properly.
It's like in the patient/doctor joke: Patient: 'Doctor, it hurts when I
Try this:
./configure LDFLAGS=-Wl,--as-needed
It will fail miserably because things are not linked properly.
Do we actually need separate librpmXYZ for anything?
Doing single librpm.so would solve the problem.
--
Arkadiusz MiśkiewiczPLD/Linux Team
arekm / maven.pl
Arkadiusz Miskiewicz wrote:
Try this:
./configure LDFLAGS=-Wl,--as-needed
It will fail miserably because things are not linked properly.
Do we actually need separate librpmXYZ for anything?
Doing single librpm.so would solve the problem.
quick summary of the discussion we had on #rpm
