dpkg default flags break compilation
Bug #481085 reported by
salsaman
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lives (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: dpkg
dpkg sets LDFLAGS to -Wl,-Bsymbolic-
The LiVES package has very specific LDFLAGS, CFLAGS and so on. These should not be overwritten.
I consider this a very serious issue.
dpkg should not set any of these flags for projects, or at the very least there should at least be a way to override the flag setting.
IMO this is a very bad design decision.
The problem has been noted in at least ubuntu 9.10, possibly other versions have it.
description: | updated |
To post a comment you must log in.
Hi,
Some more information:
As far as I can tell this only affects jaunty, karmic and lucid. The problem seems to be introduced in 1.14.24ubuntu1 and previous versions of Ubuntu don't contain this version or higher.
To reproduce this problem simply try to compile problems such as LiVES (source package name lives) with a dpkg version higher than 1.14.24ubuntu1. Looking through the build log you should see that LDFLAGS has been set to -Wl,-Bsymbolic- functions. See http:// launchpadlibrar ian.net/ 34342772/ buildlog_ ubuntu- karmic- amd64.lives_ 1.1.4-1_ FULLYBUILT. txt.gz for an example.
While this issue is being resolved, please could someone make sure that the relevant changes don't get synced across to Debian? The last thing we need is lives and other programs on Debian *and* Ubuntu crashing because of a dpkg bug.