|Subject:||Re: bug#49308: GNU sed for Tru6 configure CFLAGS?|
|Date:||Thu, 5 Aug 2021 02:21:38 +0000|
> Does the compiler complain that the "mbtowc_with_lock" function has an
> unresolved symbol relating to 'pthreads' ?
I believe it was a link error.
It's been a few weeks. :)
I can go and look, but also passing -pthread or -pthreads is fairly common "in the ecosystem" (across
the random set of stuff I built).
The -pthread flag implies something like -D_MT -lpthread.
Informally, if you are talking about locks, you
are talking about pthreads (or Windows), and the
various -pthread / -pthreads switches make sense,
or in any case, imho, on platforms that give it
any meaning, are fairly harmless.
Yeah, I know you might map an extra .so unnecessarily.
From: Assaf Gordon <email@example.com>
Sent: Wednesday, August 4, 2021 9:29 PM
To: Jay K <firstname.lastname@example.org>; email@example.com <firstname.lastname@example.org>
Cc: Larkin Nickle <email@example.com>; firstname.lastname@example.org List <email@example.com>
Subject: Re: bug#49308: GNU sed for Tru6 configure CFLAGS?
On 2021-07-01 12:35 a.m., Jay K wrote:
> Hi. I built GNU sed for Tru64.
> With native cc, not gcc. I realize it is an old system.
> $ uname -srm
> OSF1 V5.1 alpha
> $ which cc
> $ cc -V
> Compaq C V6.5-303 (dtk) on HP Tru64 UNIX V5.1B (Rev. 2650)
> Compiler Driver V6.5-302 (dtk) cc Driver
> It seemed to require:
> ./configure CFLAGS="-pthread"
> Otherwise, there was an unresolved mbtowc_with_lock.
To be more precise:
Does the compiler complain that the "mbtowc_with_lock" function has an
unresolved symbol relating to 'pthreads' ?
or that the symbol "mbtowc_with_lock" is unresolved ?
> Perhaps configure.ac can/should do that automatically?
> Perhaps this can/should somehow be done more globally, beyond sed?
> i.e. I should refer to autoconf mailing list?
'mbtowc_with_lock' comes from the gnulib module 'mbtowc-lock':
I see the file has several #ifdefs for specific systems,
perhaps Tru64 can be added?
Gnulib experts can perhaps answer this better.
(But as you're aware, there's a limited amount of support for older
|[Prev in Thread]||Current Thread||[Next in Thread]|