public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/30450] New: Build failure (linux-low.cc:5393:45: error: expected ':' before ')' token) with musl-1.2.4
Date: Tue, 16 May 2023 06:22:15 +0000	[thread overview]
Message-ID: <bug-30450-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30450
           Summary: Build failure (linux-low.cc:5393:45: error: expected
                    ':' before ')' token) with musl-1.2.4
           Product: gdb
           Version: 13.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: sam at gentoo dot org
                CC: brobecke at sourceware dot org
  Target Milestone: ---

musl-1.2.4 drops LFS shims (see https://bugs.gentoo.org/903611#c0).

I get the following with musl-1.2.4:
```
[...]
x86_64-gentoo-linux-musl-g++     -I. -I. -I./../gdb/regformats -I./..
-I./../include -I./../gdb -I./../gnulib/import -I../gnulib/import -I./.. -I..  
-pthread -Wall -Wpointer-arith -Wno-unused -Wunused-value
-Wunused-variable -Wunused-function -Wno-switch -Wno-char-subscripts
-Wempty-body -Wunused-but-set-parameter -Wunused-but-set-variable
-Wno-sign-compare -Wno-error=maybe-uninitialized -Wno-mismatched-tags -Ws
uggest-override -Wimplicit-fallthrough=3 -Wduplicated-cond -Wshadow=local
-Wdeprecated-copy -Wdeprecated-copy-dtor -Wredundant-move
-Wmissing-declarations -Wstrict-null-sentinel -Wformat -Wformat-nonliteral
-DGDBSERVER -O2 -pipe -march=native -fdiagnostics-color=always
-frecord-gcc-switches -D_GLIBCXX_ASSERTIONS     -c -o linux-low.o -MT
linux-low.o -MMD -MP -MF ./.deps/linux-low.Tpo linux-low.cc
linux-low.cc: In function 'int proc_xfer_memory(CORE_ADDR, unsigned char*,
const gdb_byte*, int)':
linux-low.cc:5393:45: error: expected ':' before ')' token
 5393 |                  ? write (fd, writebuf, len));
      |                                             ^
      |                                             :
linux-low.cc:5393:45: error: expected primary-expression before ')' token
linux-low.cc:5393:45: error: expected ':' before ')' token
 5393 |                  ? write (fd, writebuf, len));
      |                                             ^
      |                                             :
linux-low.cc:5393:45: error: expected primary-expression before ')' token
make[2]: *** [Makefile:545: linux-low.o] Error 1
```

This is already fixed on master in
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=2e977d9901393ea1bacbe1896af0929e968bc811.

Could this be backported to the 13 branch? Thanks!

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

             reply	other threads:[~2023-05-16  6:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16  6:22 sam at gentoo dot org [this message]
2023-05-16 16:53 ` [Bug build/30450] " cvs-commit at gcc dot gnu.org
2023-05-16 16:53 ` tromey at sourceware dot org
2023-05-16 16:55 ` sam at gentoo 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-30450-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).