Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@freebsd.org>, gdb-patches@sourceware.org
Subject: Re: spurious change regenerating gdb/config.in?
Date: Wed, 19 Oct 2016 13:09:00 -0000	[thread overview]
Message-ID: <47b926c4-7191-7f6d-30d2-e36e148d7a5f@redhat.com> (raw)
In-Reply-To: <5948067.MWKfYDzD67@ralph.baldwin.cx>

On 10/19/2016 04:08 AM, John Baldwin wrote:
> On Wednesday, October 19, 2016 01:09:53 AM Pedro Alves wrote:
>> If I run autoheader on the gdb/ dir, I see this spurious
>> change come out:
>>
>> diff --git c/gdb/config.in w/gdb/config.in
>> index c82a5b4..3790d10 100644
>> --- c/gdb/config.in
>> +++ w/gdb/config.in
>> @@ -453,12 +453,12 @@
>>  /* Define to 1 if your system has struct lwp. */
>>  #undef HAVE_STRUCT_LWP
>>  
>> -/* Define to 1 if `struct ptrace_lwpinfo' is a member of `pl_tdname'. */
>> -#undef HAVE_STRUCT_PTRACE_LWPINFO_PL_TDNAME
>> -
>>  /* Define to 1 if `struct ptrace_lwpinfo' is a member of `pl_syscall_code'. */
>>  #undef HAVE_STRUCT_PTRACE_LWPINFO_PL_SYSCALL_CODE
>>  
>> +/* Define to 1 if `struct ptrace_lwpinfo' is a member of `pl_tdname'. */
>> +#undef HAVE_STRUCT_PTRACE_LWPINFO_PL_TDNAME
>> +
>>  /* Define to 1 if your system has struct reg in <machine/reg.h>. */
>>  #undef HAVE_STRUCT_REG
>>
>>
>> This is with pristine FSF autoconf 2.64.  I suspect this is
>> just because the config.in in master was generated by some
>> other autoconf version.  To confirm, does anyone else
>> see this?
> 
> I don't see this, but feel free to fix.  It is likely my fault somehow as I
> added the associated check.  I had used a pristine FSF autoconf (built and
> installed to a custom prefix to avoid it using any other autoconf), so I'm
> not sure why it is different.

OK, thanks.  It's not a big deal.  Was just wondering whether
the issue was on my side.  Since Yao confirms, it doesn't look
like it.

If when you regen on your side, you still see it like you originally had
it, I wonder whether this is a sorting bug in autoheader or one of
the utilities it might spawn (perl, shell, etc.?) somewhere.  It seems
like the HAVE_FOO #undef/#define's in config.in are alphabetically
sorted.  If I regen, it's fixing the sort.  Seems like these macros
are the longest named ones in the file, that may be related.

Anyway, I'll push it in in a sec.

Thanks,
Pedro Alves


  reply	other threads:[~2016-10-19 13:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19  0:10 Pedro Alves
2016-10-19  3:23 ` John Baldwin
2016-10-19 13:09   ` Pedro Alves [this message]
2016-10-19 15:55   ` Maciej W. Rozycki
2016-10-19  8:01 ` Yao Qi

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=47b926c4-7191-7f6d-30d2-e36e148d7a5f@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@freebsd.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