public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: "jakub at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/24328] [dwz] Combining files with different pointer sizes switches off multifile mode
Date: Mon, 15 Mar 2021 10:12:52 +0000	[thread overview]
Message-ID: <bug-24328-11298-MHu9CU6O8I@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24328-11298@http.sourceware.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at redhat dot com> ---
The invoker needs to tell dwz the name of the file, so if there are multiple,
it would need to tell multiple names and the question would be how to figure
out what should go where.

I think this is something that should be done in rpm scripts instead, find out
the separate sets, choose the supplemental name for each set, run dwz multiple
times on them and make sure it is all packaged.

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

  parent reply	other threads:[~2021-03-15 10:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 [Bug default/24328] New: " vries at gcc dot gnu.org
2019-01-01  0:00 ` [Bug default/24328] " vries at gcc dot gnu.org
2019-01-01  0:00 ` vries at gcc dot gnu.org
2019-01-01  0:00 ` vries at gcc dot gnu.org
2021-03-15  9:16 ` mliska at suse dot cz
2021-03-15 10:08 ` rguenth at gcc dot gnu.org
2021-03-15 10:12 ` jakub at redhat dot com [this message]
2021-03-15 10:18 ` rguenth at gcc dot gnu.org
2021-03-15 10:25 ` 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-24328-11298-MHu9CU6O8I@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).