Re: wrong bfd recognized

Luca Pizzamiglio
2012-01-02T10:04:03Z

Hi Joel,

sorry for the confusion, I'm not used to write this kind of ChangeLog
entry. My fault.

2012-01-02 Luca Pizzamiglio <luca.pizzamiglio@gmail.com>

* gdb/configure.ac (LDFLAGS in ELF support's check): changing path
priority in LDFLAGS
LDFLAGS is redefined putting an external-defined value at the end.

I hope that works now! This rules doesn't fit well with autoconf files :)
Feel free to modify it, if it's still wrong.

thanks for the support

Luca

On Thu, Dec 29, 2011 at 1:17 PM, Joel Brobecker <brobecker@adacore.com> wrote:
> Luca
>
>> > Could you write a ChangeLog entry for your patch?
>> > I will put it in.
> [...]
>> Ok. A possible entry could be:
>>
>> improved bfd local static library detection in the configure script
>
> Unfortunately, this is not what a ChangeLog entry should look like.
> I suspect you thought that we were asking for some text to be used
> as revision history?  Here is what a ChangeLog entry looks like:
>
> 2011-12-27  Doug Evans  <dje@google.com>
>
>        * dwarf2read.c (struct dwarf2_cu): Delete members first_fn, last_fn,
>        cached_fn.
>        (struct function_range): Delete.
>        (initialize_cu_func_list, add_to_cu_func_list): Delete.  All callers
>        updated.
>        (check_cu_functions): Ditto.
>
> You can have a look at the couple of sections that explain ChangeLogs
> in the GNU Coding Standards (the link brings you directly to the
> relevant section):
>
>    http://www.gnu.org/prep/standards/standards.html#Change-Logs
>
> Please let me know if you have any problems creating one and I will
> write it for you (this time!).
>
> --
> Joel