GNU bug report logs -
#49308
GNU sed for Tru6 configure CFLAGS?
Previous Next
Reported by: Jay K <jayk123 <at> hotmail.com>
Date: Thu, 1 Jul 2021 07:23:01 UTC
Severity: normal
Done: Paul Eggert <eggert <at> cs.ucla.edu>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 49308 in the body.
You can then email your comments to 49308 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-sed <at> gnu.org:
bug#49308; Package
sed.
(Thu, 01 Jul 2021 07:23:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Jay K <jayk123 <at> hotmail.com>:
New bug report received and forwarded. Copy sent to
bug-sed <at> gnu.org.
(Thu, 01 Jul 2021 07:23:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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
/usr/bin/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.
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?
Fyi, tests mostly passed, but 2 failures, look like test harness problem:
FAIL: testsuite/comment-n
=========================
diff: Cannot compare character special file.
FAIL testsuite/comment-n.sh (exit status: 1)
FAIL: testsuite/execute-tests
=============================
diff: Cannot compare character special file.
0000000 62 00
b \0
0000002
0000000 62 00
b \0
0000002
FAIL testsuite/execute-tests.sh (exit status: 1)
I should probably try with GNU diff, later.
Thank you,
- Jay
Information forwarded
to
bug-sed <at> gnu.org:
bug#49308; Package
sed.
(Wed, 04 Aug 2021 21:30:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 49308 <at> debbugs.gnu.org (full text, mbox):
(adding gnulib@)
Hello,
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
> /usr/bin/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':
https://git.savannah.gnu.org/cgit/gnulib.git/tree/lib/mbtowc-lock.h
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
systems...)
regards,
- assaf
Reply sent
to
Paul Eggert <eggert <at> cs.ucla.edu>:
You have taken responsibility.
(Wed, 04 Aug 2021 21:47:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Jay K <jayk123 <at> hotmail.com>:
bug acknowledged by developer.
(Wed, 04 Aug 2021 21:47:01 GMT)
Full text and
rfc822 format available.
Message #13 received at 49308-done <at> debbugs.gnu.org (full text, mbox):
On 8/4/21 2:29 PM, Assaf Gordon wrote:
> (But as you're aware, there's a limited amount of support for older
> systems...)
Yes, HP dropped support for Tru64 in 2012, and a good rule of thumb for
GNU code is to not worry about an OS if it's so old that even its own
maintainer doesn't worry about it.
Gnulib finally got around to dropping support for Tru64 in 2019, in the
sense that we removed some documentation about it (we haven't bothered
cleaning up the code). Although we don't worry about Tru64 now, we might
accept simple clean patches written by Someone Else, patches that don't
affect other platforms.
In the meantime I'm closing the sed bug report as this is not really a
sed issue.
Information forwarded
to
bug-sed <at> gnu.org:
bug#49308; Package
sed.
(Thu, 05 Aug 2021 15:00:01 GMT)
Full text and
rfc822 format available.
Message #16 received at 49308 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
> 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.
- Jay
________________________________
From: Assaf Gordon <assafgordon <at> gmail.com>
Sent: Wednesday, August 4, 2021 9:29 PM
To: Jay K <jayk123 <at> hotmail.com>; 49308 <at> debbugs.gnu.org <49308 <at> debbugs.gnu.org>
Cc: Larkin Nickle <me <at> larbob.org>; bug-gnulib <at> gnu.org List <bug-gnulib <at> gnu.org>
Subject: Re: bug#49308: GNU sed for Tru6 configure CFLAGS?
(adding gnulib@)
Hello,
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
> /usr/bin/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':
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.savannah.gnu.org%2Fcgit%2Fgnulib.git%2Ftree%2Flib%2Fmbtowc-lock.h&data=04%7C01%7C%7C9684e1475a5e409f239008d9578efdc9%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637637093914845575%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Vxw5U%2B2Wo6O7OT%2FYoAlYcNNL4HXNVAfq1dhCPFa39OE%3D&reserved=0
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
systems...)
regards,
- assaf
[Message part 2 (text/html, inline)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org.
(Fri, 03 Sep 2021 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 229 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.