From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/25252] dwz: returns exit status 1, causing FTBFS in deal.ii
Date: Tue, 02 Mar 2021 12:11:44 +0000 [thread overview]
Message-ID: <bug-25252-11298-5LnWud6A1h@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25252-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25252
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Mark Wielaard from comment #4)
> There seems to have been 2 issues here.
>
> One was the "Too many DIEs, not optimizing" which was solved by adding -L
> 100000000. The downstream debian bug was closed:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946255
>
Ack.
> The second was the exit code being wrong. Comment #1 has a patch for that.
> Which doesn't seem to have been applied. But I don't know how to trigger
> that, so cannot check whether it is still needed.
Should be fixed by https://sourceware.org/pipermail/dwz/2021q1/001027.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-02 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 [Bug default/25252] New: " ginggs at debian dot org
2019-01-01 0:00 ` [Bug default/25252] " vries at gcc dot gnu.org
2019-01-01 0:00 ` vries at gcc dot gnu.org
2019-01-01 0:00 ` ginggs at debian dot org
2021-02-18 23:55 ` mark at klomp dot org
2021-03-02 12:11 ` vries at gcc dot gnu.org [this message]
2021-03-04 9:01 ` vries at gcc dot gnu.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-25252-11298-5LnWud6A1h@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@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).