install script crashes on unknown ld option -Bsylmbolic-functions

I've found an explanation.

- When ecl package is built on the developer host, the flags given by dpkg-buildpackage are stored in the install script.
- These flags include LDFLAGS => '-Wl,-Bsymbolic-functions'
- When ecl is installed on the user host, it needs a version of /usr/bin/ld which supports -Bsylmbolic-functions.
- Therefore, there is a dependency of ecl install script on that version of ld.

-> binutils 2.17.20070103cvs-0ubuntu2 doesn't work
-> binutils_2.18.93.20081009-0ubuntu1_i386.deb works

I guess this problem can be solved with a right package dependency, if confirmed?

Hi! I retry the install in all supported ubuntu versions and it installs fine.

Could you retry please?

No, sorry, I don't have any machine that can be reverted to such an
old version of binutils.

It could only happen when installing ecl on a machine with binutils
2.17, and Hardy (the oldest supported version) uses 2.18, so the bug
is now deprecated (it's almost 3 years old).

Note that if a new flag is added on binutils, the bug will come back,
if ecl still uses at install time a file generated by
dpkg-buildpackage at compile time.

On Thu, Sep 1, 2011 at 11:33 AM, Angel Abad <email address hidden> wrote:
> Hi! I retry the install in all supported ubuntu versions and it installs
> fine.
>
> Could you retry please?
>
> ** Changed in: ecl (Ubuntu)
>       Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/317827
>
> Title:
>  install script crashes on unknown ld option -Bsylmbolic-functions
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ecl/+bug/317827/+subscriptions
>

[Expired for ecl (Ubuntu) because there has been no activity for 60 days.]

As predicted the bug has reappeared. And it seems to affect all currently supported ubuntu versions. See:

 - https://launchpad.net/~maxima-developers/+archive/ubuntu/maxima-nightly/+build/13530410/+files/buildlog_ubuntu-precise-amd64.maxima_5.41.0-2~201710010713~ubuntu12.04.1_BUILDING.txt.gz
 - https://launchpad.net/~maxima-developers/+archive/ubuntu/maxima-nightly/+build/13530416/+files/buildlog_ubuntu-artful-amd64.maxima_5.41.0-2~201710010713~ubuntu17.10.1_BUILDING.txt.gz
 - https://launchpad.net/~maxima-developers/+archive/ubuntu/maxima-nightly/+build/13530418/+files/buildlog_ubuntu-zesty-amd64.maxima_5.41.0-2~201710010713~ubuntu17.04.1_BUILDING.txt.gz
 - https://launchpad.net/~maxima-developers/+archive/ubuntu/maxima-nightly/+build/13530422/+files/buildlog_ubuntu-vivid-amd64.maxima_5.41.0-2~201710010713~ubuntu15.04.1_BUILDING.txt.gz
 - https://launchpad.net/~maxima-developers/+archive/ubuntu/maxima-nightly/+build/13530414/+files/buildlog_ubuntu-trusty-amd64.maxima_5.41.0-2~201710010713~ubuntu14.04.1_BUILDING.txt.gz
 - https://launchpad.net/~maxima-developers/+archive/ubuntu/maxima-nightly/+build/13530420/+files/buildlog_ubuntu-xenial-amd64.maxima_5.41.0-2~201710010713~ubuntu16.04.1_BUILDING.txt.gz

Possible Workaround from the user's side: In my case calling

./configure

as

./configure LDFLAGS=""

allowed me to compile my program.