public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/27811] [11 Regression] arm-linux-gnueabihf and aarch64-linux-gnu fail to configure in sim, sim/aarch64
Date: Mon, 03 May 2021 14:58:42 +0000	[thread overview]
Message-ID: <bug-27811-4717-IrQNY5NmL9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27811-4717@http.sourceware.org/bugzilla/>

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

Simon Marchi <simark at simark dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simark at simark dot ca

--- Comment #8 from Simon Marchi <simark at simark dot ca> ---
(In reply to Matthias Klose from comment #7)
> for aarch64:
> 
> configured with: --build=aarch64-linux-gnu
> 	 --host=aarch64-linux-gnu
> 	 --prefix=/usr
> 	 --libexecdir=${prefix}/lib/gdb
> 	 --disable-werror
> 	 --disable-maintainer-mode
> 	 --disable-dependency-tracking
> 	 --disable-silent-rules
> 	 --disable-gdbtk
> 	 --disable-shared
> 	 --without-system-readline
> 	 --srcdir=/<<PKGBUILDDIR>>
> 	 --with-expat
> 	 --with-system-zlib
> 	 --without-guile
> 	 --without-babeltrace
> 	 --with-debuginfod
> 	 --with-babeltrace
> 	 --with-system-gdbinit=/etc/gdb/gdbinit
> 	 --with-system-gdbinit-dir=/etc/gdb/gdbinit.d
> 	 --enable-tui
> 	 --with-lzma
> 	 --with-python=python3
> 	 --with-xxhash
> 	 --with-mpfr

Side-note: it's interesting that configure complains about not finding a
suitable dependency tracking method, even if the build is with
--disable-dependency-tracking.

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

  parent reply	other threads:[~2021-05-03 14:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03  6:53 [Bug build/27811] New: " doko at debian dot org
2021-05-03  6:56 ` [Bug build/27811] " doko at debian dot org
2021-05-03  7:23 ` doko at debian dot org
2021-05-03  7:25 ` doko at debian dot org
2021-05-03  7:33 ` schwab@linux-m68k.org
2021-05-03  7:38 ` doko at debian dot org
2021-05-03  7:46 ` doko at debian dot org
2021-05-03  7:59 ` doko at debian dot org
2021-05-03 14:00 ` tromey at sourceware dot org
2021-05-03 14:12 ` doko at debian dot org
2021-05-03 14:58 ` simark at simark dot ca [this message]
2021-05-04  0:59 ` wilson at gcc dot gnu.org
2021-06-29 11:49 ` doko at debian dot org
2021-06-29 14:59 ` doko at debian dot org
2021-10-31 16:58 ` [Bug sim/27811] " vapier 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-27811-4717-IrQNY5NmL9@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).