a linker script isn't something unusual. Maybe the versioned .so file as
a linker script is unusual.
flex (2.5.33-6) unstable; urgency=low
* Starting with version 2.5.33-6 of flex we have started providing
a static library compiled with position independent code, namely,
libfl_pic.a. The problem is with packages that contain share
libraries with a flex scanner compiled in. Since flex generates code
that is not self contained, and the missing symbols live in
libfl.a. However, since linking a shared library with a object
containing non position independent code stopped working with gcc 4.1
(apparently, it was sheer luck that it worked at all). So now we also
provide libfl_pic.a for shared library packages to link with.
An alternative would have been to provide a full fledged
shared library, but that would have been a major break with upstream
and other distributions that also have flex, and would entail
creating new library and devel packages for flex, which is more work
that seems justified (considering that we would have to maintain the
fork, and keep track of any ABI changes, and all that).
so what use case if failing for you?
** Changed in: flex (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515159
Title:
libfl.so contains text instead of ELF code
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flex/+bug/1515159/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
