From: Fergus Daly <fergusd84@outlook.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: gcc v.11.3.0 failing - possible cause gcc or libreadline.a?
Date: Thu, 15 Dec 2022 08:06:01 +0000 [thread overview]
Message-ID: <DB6P18901MB0055CB2FA11847A55C63B1B4A4E19@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DB6P18901MB005508B5FFA1E5B9969C371AA4E09@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM>
>> In a gcc build script terminating with the instruction
>> gcc -w -static -o myexe -O3 ./myarchive.a -lreadline -lncurses -lm
>> I have suddenly started getting very many instances of both of
>> ld: /usr/src/debug/readline-8.2-2/terminal.c:nn various: undefined reference to `{various}'
>> ld: /usr/src/debug/readline-8.2-2/display.c:nn various: undefined reference to `{various}'
>> and the build fails.
The problem was with readline not gcc
and I assume originates in myarchive.a and the required switch -lreadline in the gcc line
rather than in readline: nevertheless I reverted both libreadline-devel and libreadline7
from 8.22 to 7.03 and the problem went away.
next prev parent reply other threads:[~2022-12-15 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 10:42 Fergus Daly
2022-12-15 8:06 ` Fergus Daly [this message]
2022-12-17 22:40 ` Brian Inglis
2022-12-19 12:13 ` Fergus Daly
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=DB6P18901MB0055CB2FA11847A55C63B1B4A4E19@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM \
--to=fergusd84@outlook.com \
--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).