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

Re: Missing m68k builds for the point release



	Hi Christian,

On Mon, 7 Jan 2008, Christian T. Steigies wrote:
> On Mon, Jan 07, 2008 at 08:48:01AM +0100, Geert Uytterhoeven wrote:
> > As we just got 2.6.24-rc7, I expect 2.6.25 near the end of March.
> 
> I am having some trouble keeping m68k up-to-date in the debian svn, is this
> always the list of the latest patches?
> http://linux-m68k-cvs.ubb.ca/~geert/linux-m68k-patches-2.6/

Yes, it's against Linus' current tree.

> and when a new releaese is ready, you put it into something like this:
> http://linux-m68k-cvs.ubb.ca/~geert/linux-m68k-patches-2.6.23
> ?

Yes. And any critical changes to linux-m68k-patches-2.6 are applied to
linux-m68k-patches-2.6.23 as well.

At some day I plan to put these patches in git...

> I noticed that some of the patches have changed (just little bits, but
> enough to make the patch fail), so I am thinking of copying your structure

They may indeed change, when Linus' tree changes.

> in the debian svn, ie having a new directory for every version. Then
> adding/updating patches could be done almost automatically.

> But I discovered another problem in the build, which was not there
> previously. After the kernel and modules have been built, some files from
> the build tree are being removed:
> 
> rm $(PACKAGE_DIR)/lib/modules/$(REAL_VERSION)/{build,source,modules.*}
> 
> I had to change it to this for m68k to succeed:
> 
> rm $(PACKAGE_DIR)/lib/modules/$(REAL_VERSION)-m68k/{build,source,modules.*}
> 
> REAL_VERSION = $(UPSTREAMVERSION)$(ABINAME)$(LOCALVERSION)
> 
> But it seems this is not the correct solution:
>  On Sat, Jan 05, 2008 at 09:44:02PM +0000, Christian T. Steigies wrote:
>  > adjust path for {build,source,modules.*} for m68k only
>  
>  This is a workaround for some generic problem. The kernel thinks it have
>  a different EXTRAVERSION than the package. Please revert and fix the
>  real problem.
>  
>  Bastian
> 
> There is a clue hidden here for what the real problem is, maybe you can
> solve the puzzle?

Perhaps you have `CONFIG_LOCALVERSION="-m68k"' in your .config?

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds


Reply to: