public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cbiesinger at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug win32/27242] multiple definition of `UP'; ../readline/readline/libreadline.a(terminal.o):terminal.c:(.bss+0x98): first defined here
Date: Fri, 08 Oct 2021 21:33:42 +0000	[thread overview]
Message-ID: <bug-27242-4717-8CDhByJjw6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27242-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27242

--- Comment #2 from Christian Biesinger <cbiesinger at google dot com> ---
So this could be worked around by using system readline, presumably. But still
investigating what's going on. This is the code in readline:

#if !defined (__linux__) && !defined (NCURSES_VERSION)
#  if defined (__EMX__) || defined (NEED_EXTERN_PC)
extern 
#  endif /* __EMX__ || NEED_EXTERN_PC */
char PC, *BC, *UP;
#endif /* !__linux__ && !NCURSES_VERSION */

As far as I can tell, NEED_EXTERN_PC is never defined anywhere (??)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-10-08 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 13:35 [Bug win32/27242] New: " cbiesinger at google dot com
2021-10-07 17:28 ` [Bug win32/27242] " cbiesinger at google dot com
2021-10-08 21:33 ` cbiesinger at google dot com [this message]
2021-10-08 21:45 ` cbiesinger at google dot com
2021-10-08 21:56 ` cbiesinger at google dot com
2022-03-18 12:41 ` ssbssa at sourceware dot org

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=bug-27242-4717-8CDhByJjw6@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).