This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Fix jit-reader.h for multilib
- From: Yao Qi <yao at codesourcery dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Mon, 12 Jan 2015 10:33:37 +0800
- Subject: Re: [patch] Fix jit-reader.h for multilib
- Authentication-results: sourceware.org; auth=none
- References: <20150107173634 dot GA13295 at host2 dot jankratochvil dot net> <87387htths dot fsf at codesourcery dot com> <20150111131353 dot GA9107 at host2 dot jankratochvil dot net>
Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> # multi-lib safety means that files with the same pathname (which is
> # /usr/include, contrary to /usr/lib vs. /usr/lib64 for example)
> # contain exactly the same content.
>
Thanks, that is clear to me now.
> See also:
> https://fedoraproject.org/wiki/PackagingDrafts/MultilibTricks#File_conflicts
>
>
> When we discuss it personally I do not think multilib should be applied to the
> GDB package as there is nothing like /usr/lib{,64}/libgdb.so. There is only
> /usr/bin/gdb and that has always just one arch on one system. So installing
> gdb.i686 and gdb.x86_64 simultaneously does not have any benefits / makes
> sense. But despites this I need it for Red Hat packaging so I am fine to also
> keep it just as a downstream patch. OTOH I guess other OS packagers may also
> face it so it may be easier for everyone to do it upstream.
Is multi-lib safety a Fedora/Red Hat specific packaging rule? or do
other distributions need this too? If answer is yes, I don't object to
your patch as it adjusts the order of looking for desired types.
--
Yao (éå)