From: Eli Zaretskii <eliz@gnu.org>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org, gdb@sourceware.org
Subject: Re: GDB ARIndex cleanup
Date: Thu, 26 Mar 2009 20:53:00 -0000 [thread overview]
Message-ID: <ur60km4gf.fsf@gnu.org> (raw)
In-Reply-To: <000001c9ae14$24fb7cd0$6ef27670$@u-strasbg.fr>
> From: "Pierre Muller" <muller@ics.u-strasbg.fr>
> Cc: <gdb@sourceware.org>, "'Eli Zaretskii'" <eliz@gnu.org>
> Date: Thu, 26 Mar 2009 14:09:49 +0100
>
> 2) GNU/Linux issues.
>
> This is more difficult for me to fix, as
> the difference between "Linux kernel" and "GNU/Linux system"
> is still kind of fuzzy...
>
> Could someone else look into those issues?
Can you publish the list of files where this issue arises? Are the
files you mentioned in this mail the only ones?
> 3) I also recompiled doschk program
> so that the list of incompatibilities with
> the DOS limitations is generated again...
>
> Eli, there are probably several directories that we could
> disregard for this, but I think that
> there are also real issues left.
There shouldn't be any. But to see that, you need to prepare a GDB
tarball, then untar it using djunpack.bat as explained in
gdb/config/djgpp/README, and _then_ run doschk on the resulting tree.
That's because the file-name conflicts are supposed to be solved by
remapping in gdb/config/djgpp/fnchange.lst, which djunpack.bat uses.
> Here is a list of Linux detected problems:
They can all stay "Linux", except for this one:
> lines 39,43p gdb/ppc-linux-tdep.h
> int ppc_linux_trap_reg_p (struct gdbarch *gdbarch);
>
> /* Linux target descriptions. */
> extern struct target_desc *tdesc_powerpc_32l;
> extern struct target_desc *tdesc_powerpc_altivec32l;
next prev parent reply other threads:[~2009-03-26 20:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 15:29 Pierre Muller
2009-03-26 20:53 ` Eli Zaretskii [this message]
2009-03-27 8:23 ` Pierre Muller
2009-03-27 8:47 ` Eli Zaretskii
2009-03-27 14:12 ` Eli Zaretskii
2009-03-27 15:35 ` Eli Zaretskii
2009-04-02 15:12 ` Thiago Jung Bauermann
2009-04-02 19:40 ` Eli Zaretskii
2009-04-02 20:34 ` Joel Brobecker
2009-03-26 23:18 ` Joel Brobecker
2009-03-27 2:22 ` Daniel Jacobowitz
2009-03-27 8:43 ` Pierre Muller
2009-03-27 16:04 ` Joel Brobecker
2009-03-27 16:46 ` Daniel Jacobowitz
2009-04-14 23:06 ` [RFC] GDB ARIndex Linux rule cleanup Pierre Muller
2009-04-14 23:23 ` Mark Kettenis
2009-04-14 23:38 ` Pedro Alves
2009-04-14 23:41 ` Joel Brobecker
2009-04-15 7:06 ` Pierre Muller
2009-04-15 7:33 ` Eli Zaretskii
2009-04-15 14:00 ` Ulrich Weigand
2009-04-15 14:21 ` Pedro Alves
2009-04-15 15:32 ` Ulrich Weigand
2009-04-15 15:54 ` Pedro Alves
2009-04-15 14:25 ` Eli Zaretskii
2009-04-15 15:15 ` Daniel Jacobowitz
2009-04-15 15:23 ` Ulrich Weigand
2009-04-15 15:34 ` Mark Kettenis
2009-04-15 16:00 ` Eli Zaretskii
2009-04-15 16:04 ` Eli Zaretskii
2009-04-15 17:34 ` Ulrich Weigand
2009-04-15 18:07 ` Eli Zaretskii
2009-04-15 18:55 ` Ulrich Weigand
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=ur60km4gf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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