From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: autoconf tests for iconv fail with undefined refs
Date: Sat, 19 Feb 2022 16:53:46 -0700 [thread overview]
Message-ID: <6a469569-1ee5-c4d3-994d-372b1533c96f@SystematicSw.ab.ca> (raw)
In-Reply-To: <20220220083755.7555.50F79699@gmail.com>
On 2022-02-19 16:37, Lemures Lemniscati wrote:
> On Sat, 19 Feb 2022 10:11:06 -0700, Brian Inglis
>> On 2022-02-18 22:26, Lemures Lemniscati wrote:
>>> On Fri, 18 Feb 2022 12:33:30 -0700, Brian Inglis
>>>> Any idea why autoconf tests for iconv now fail with undefined refs to iconv{_open,,_close}! >>>> STC attached, log, -E output. Tried also with -l iconv.
>>> https://cygwin.com/cgi-bin2/jobs.cgi?srcpkg=playground&id=3861
>>> This will successfully build libisocodes-1.2.4 but some tests fail.
>> Not so worried about that, just noticed that iconv conftest also failed in my recent findutils build which I released, missing libiconv functions and presumably substituting gnulib functions, although the iconv conftest passed in github scallywag.
>> This may be the result of a change in gnulib or autoconf, which now sometimes fails when it should not.
> Although `gcc iconv-test.c -liconv` should pass, it might have been used
> for test, a command like either `gcc -liconv iconv-test.c`,
> or `gcc iconv-test.c`.
After conftest if iconv... is in libc, the next conftest compiles adding
-liconv, and still fails.
I'm going to look for most recent successful iconv conftest in
config.log and compare the logs and configure scripts iconv sections to
those in the failing findutils and libisocodes, to see if I can track it
back to gnulib or autoconf changes to the compile flags or options, or
at least enough info to file a bug report upstream somewhere.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-02-19 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 19:33 Brian Inglis
2022-02-19 5:26 ` Lemures Lemniscati
2022-02-19 17:11 ` Brian Inglis
2022-02-19 23:37 ` Lemures Lemniscati
2022-02-19 23:53 ` Brian Inglis [this message]
2022-02-20 1:10 ` Lemures Lemniscati
2022-02-19 7:51 ` Lemures Lemniscati
2022-02-19 15:46 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a469569-1ee5-c4d3-994d-372b1533c96f@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).