On 2018-06-06 18:09 -0400, Thomas Dickey wrote:
> On Wed, Jun 06, 2018 at 11:08:18PM +0200, Sven Joachim wrote:
>> On 2018-06-06 16:09 -0400, Thomas Dickey wrote:
>>
>> > On Wed, Jun 06, 2018 at 07:39:42PM +0200, Sven Joachim wrote:
>> >> On 2018-06-05 21:43 +0200, Sven Joachim wrote:
>> > ...
>> >> >> |
>> >> >> /usr/lib/gcc/i686-linux-gnu/7/../../../i386-linux-gnu/libncurses.a(lib_mouse.o):
>> >> >> In function `mouse_activate':
>> >> >> | (.text+0x1032): undefined reference to `gpm_fd'
>> >> >> | collect2: error: ld returned 1 exit status
>
> hmm - my recollection of this was that I'd gotten it to fail silently
> when dlsym is used.
>
>> > Given the report, I'd expect something amiss in the configure script
>> > to handle the case where I'd like libdl to load gpm (but don't know
>> > why that would be related to wattr macros...)
>>
>> Actually the static libraries in the Debian package are configured
>> --without-dlsym because of #556378[1].
>
> Perhaps we could revisit that -- I'll investigate anyway.
The change in the 20180609 patchlevel
,----
| + modify generatesd ncurses*config and ncurses.pc, ncursesw.pc, etc.,
| to list helper libraries such as gpm for static linking
`----
looks correct to me (apart from the small typo: s/generatesd/generated).
Nevertheless, if I stop building the static libraries separately,
there is this infamous complaint about dlopen() when I link a program
statically:
,----
| …/libncurses.a(lib_mouse.o): In function `load_gpm_library':
| …/lib_mouse.c:488: warning: Using 'dlopen' in statically linked applications
requires at runtime the shared libraries from the glibc version used for linking
`----
I don't see a completely satisfactory way out of that, maybe the least of
the evils is to configure the static libraries --without-gpm.
Cheers,
Sven
