From: Svante Signell <svante.signell@gmail.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Cc: gcc-bugs@gcc.gnu.org, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: gcc-snapshot: FTBFS on hurd-i386 (and other archs?)
Date: Mon, 16 Jan 2023 23:11:49 +0100 [thread overview]
Message-ID: <28135bd05eebf66ca3138612265b8b1edbfba66b.camel@gmail.com> (raw)
Source: gcc-snapshot
Version: 20230108-1
Severity: important
Tags: patch
User: debian-hurd@lists.debian.org
Usertags: hurd
X-Debbugs-CC: debian-hurd@lists.debian.org
Hi,
gcc-snapshot in sid FTBFS on hurd-i386 due to that some patches are not
applied when building gcc-snapshot. After the statement in rules.patch
ifeq ($(single_package),yes)
debian_patches =
endif
previously defined patches are cleared, causing the build failure, see
below.
debian/ files causing the problem:
debian/rules.defs:
ifneq (,$(findstring gcc-snapshot, $(PKGSOURCE)))
single_package = yes
trunk_build = yes
debian/rules.patch:
ifeq ($(single_package),yes)
debian_patches =
endif
Thanks!
reply other threads:[~2023-01-16 22:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=28135bd05eebf66ca3138612265b8b1edbfba66b.camel@gmail.com \
--to=svante.signell@gmail.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=submit@bugs.debian.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).