Re: [PATCH] libc/eglibc: Add eglibc 2.16

[Bryan Hundven <bryanhundven at gmail dot com>]

On Mon, Jul 2, 2012 at 8:37 PM, Bryan Hundven <bryanhundven@gmail.com> wrote:
> # HG changeset patch
> # User Bryan Hundven <bryanhundven@gmail.com>
> # Date 1341286616 25200
> # Node ID 6fdf77081379812820e813274d0f15ff830d3309
> # Parent  c917c398e95919856980a6ef32c23bfa055deb9b
> libc/eglibc: Add eglibc 2.16
>
> Patches don't need to come forward, as they are in this branch.
>
> Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
>
> diff -r c917c398e959 -r 6fdf77081379 config/libc/eglibc.in
> --- a/config/libc/eglibc.in     Mon Jul 02 20:31:06 2012 -0700
> +++ b/config/libc/eglibc.in     Mon Jul 02 20:36:56 2012 -0700
> @@ -18,6 +18,11 @@
>  # Don't remove next line
>  # CT_INSERT_VERSION_BELOW
>
> +config LIBC_EGLIBC_V_2_16
> +    bool
> +    prompt "2_16"
> +    select LIBC_EGLIBC_2_16_or_later
> +
>  config LIBC_EGLIBC_V_2_15
>      bool
>      prompt "2_15"
> @@ -86,6 +91,7 @@
>      string
>  # Don't remove next line
>  # CT_INSERT_VERSION_STRING_BELOW
> +    default "2_16" if LIBC_EGLIBC_V_2_16
>      default "2_15" if LIBC_EGLIBC_V_2_15
>      default "2_14" if LIBC_EGLIBC_V_2_14
>      default "2_13" if LIBC_EGLIBC_V_2_13
> @@ -99,6 +105,10 @@
>      default "2_5" if LIBC_EGLIBC_V_2_5
>      default "trunk" if LIBC_EGLIBC_V_TRUNK
>
> +config LIBC_EGLIBC_2_16_or_later
> +    bool
> +    select LIBC_EGLIBC_2_15_or_later
> +
>  config LIBC_EGLIBC_2_15_or_later
>      bool
>      select LIBC_EGLIBC_2_14_or_later

Just to note, something in (e)glibc-2.16 breaks gdb (and possibly
other tools) wrt the siginfo structure.

It seems to be fixed in gdb's mainline here:

http://sourceware.org/git/?p=gdb.git;a=commit;h=a7f9ca9cb797d653dc7919538e1dfa0c26010331

but this is not in any of the other gdb branches.

Probably need to make these tools depend on (e)glibc <= 2.15 until we
can get a working set of patches. Or just not apply this change...
yet.

-Bryan

--
For unsubscribe information see http://sourceware.org/lists.html#faq