Messages in this thread | | | Date | Sun, 20 Oct 2013 12:28:07 -0700 | From | Guenter Roeck <> | Subject | Re: [000/121] 3.2.51-rc1 review |
| |
On 10/20/2013 11:05 AM, Ben Hutchings wrote: > On Sun, 2013-10-20 at 09:23 -0700, Guenter Roeck wrote: >> On 10/20/2013 04:56 AM, Ben Hutchings wrote: >>> On Sun, 2013-09-08 at 09:52 -0700, Guenter Roeck wrote: >>>> On 09/08/2013 01:18 AM, Geert Uytterhoeven wrote: >>>>> On Sun, Sep 8, 2013 at 9:10 AM, Guenter Roeck <linux@roeck-us.net> wrote: >>>>>> m68k-linux-ld: error: no memory region specified for loadable section >>>>>> `.note.gnu.build-id' >>>>> >>>>> I can't seem to find an explicit fix for that since v3.2. >>>>> Perhaps the fix is a side effect of f84f52a5c15db7d14a534815f27253b001735183 >>>>> ("m68knommu: clean up linker script"). >>>>> >>>> >>>> Kind of. Turns out it requires the following patches. >>>> >>>> 40c1b9cf (m68k: consolidate the vmlinux.lds linker scripts) >>>> ed865e31 (m68k: use non-MMU linker script for ColdFire MMU builds) >>>> f84f52a5 (m68knommu: clean up linker script) >>>> >>>> With those patches applied, all my m68k builds (mmu and nommu) pass with 3.2. >>> >>> I've queued these up for 3.2. The first looks quite a big change in >>> terms of lines, but most of that is just renaming a file so I think it's >>> within the spirit of the stable rules. The third is also pretty big as >>> m68knommu seems so broken in 3.2 that I suppose it is OK. >>> >>> Ben. >>> >> Hi Ben, >> >> is that in your patch list yet ? Just wondering, because the latest nommu build still failed. > > I've only just pushed them. >
Yes, I see that m68k-nommu build failures are all gone now.
Great!
Thanks, Guenter
| |