public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "orgads at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/30882] New: MinGW: undefined reference to `getline' in m32c/opc2c.c
Date: Sun, 24 Sep 2023 11:27:38 +0000	[thread overview]
Message-ID: <bug-30882-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30882
           Summary: MinGW: undefined reference to `getline' in
                    m32c/opc2c.c
           Product: gdb
           Version: 13.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: orgads at gmail dot com
  Target Milestone: ---

When building with gdb on MinGW64 with simulators enabled, I get the following
warning:

../../gdb-13.2/sim/m32c/opc2c.c: In function 'main':
../../gdb-13.2/sim/m32c/opc2c.c:541:10: warning: implicit declaration of
function 'getline' [-Wimplicit-function-declaration]
  541 |   while (getline (&linebuf, &len, in) >= 0)
      |          ^~~~~~~

And it fails to link:

ld.exe: m32c/opc2c.o:opc2c.c:(.text.startup+0x123): undefined reference to
`getline'
collect2.exe: error: ld returned 1 exit status
make[1]: *** [Makefile:3343: m32c/opc2c.exe] Error 1

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

             reply	other threads:[~2023-09-24 11:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24 11:27 orgads at gmail dot com [this message]
2023-09-24 11:33 ` [Bug build/30882] " orgads at gmail dot com
2023-10-15  3:18 ` [Bug sim/30882] sim: m32c/opc2c.c: MinGW: undefined reference to `getline' vapier at gentoo dot org
2023-10-15 17:19 ` vapier at gentoo dot org
2024-03-03 11:25 ` orgads at gmail dot com

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-30882-4717@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).