[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [patches] AVR32 port

On Thu, 7 May 2009, Bradley Smith wrote:

> I think using said patch is probably a sensible solution, where can I find
> this patch? Also in the current systems I've got, I've neglected to put a
> DEFAULT symbol version at all, meaning everything is using symbol versions
> right down to GLIBC_2.0 etc. Is there anyway to do a symbol version bump
> to GLIBC_2.11 without having to completely start from scratch? Obviously
> things are going to need to be recompiled anyway due to the elf machine
> number, but it would be nice to be able to rebuild everything using the
> currently built packages, rather than cross building everything from
> scratch again. Obviously this isn't a problem with the elf machine number
> due to ELF_MACHINE_ALT1 as you mentioned, but is this possible with a
> symbol version bump such as this?

For such a symbol version bump you would need to rebuild everything from 
scratch.  Putting in the DEFAULT when you work out the libc ABI is one of 
the many pitfalls that can arise it doing a new toolchain port, which 
illustrate why it's a good idea to try to get things submitted to the 
relevant upstreams as early as possible so such things can be pointed out 
by the people aware of the issues.

The patch is

2008-12-05  Joseph Myers  <joseph@xxxxxxxxxxxxxxxx>
            Ulrich Drepper  <drepper@xxxxxxxxxx>

        * scripts/firstversion.awk: Use custom comparison function to compare
        version numbers.
        * scripts/versions.awk: Use sort invocation which can handle
        multi-digit sub-version numbers.

which you should be able to extract from FSF glibc CVS for the relevant 

Joseph S. Myers