public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Livio Soares <livio@eecg.toronto.edu>
Cc: Theodore Ts'o <tytso@mit.edu>, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] Fix for scripts/builddeb (non-x86, and with output option)
Date: Mon, 17 Jan 2011 23:32:47 +0100	[thread overview]
Message-ID: <4D34C38F.70807@suse.cz> (raw)
In-Reply-To: <4D34C237.306@eecg.toronto.edu>

On 17.1.2011 23:27, Livio Soares wrote:
> 
>    Hi Michal and Ted,

Hi,

please do not send patches privately, CC at least the linux-kbuild
mailing list. I'll have a look at your patch tomorrow.

Michal

> 
>    I've just tried to build Debian  packages on the git version of the
> Linux  kernel, and  the  build  failed while  trying  to generate  the
> headers package.  The  problem seems to come from 2  issues: (1) I use
> the 'O=' option to place build files out of the source tree, and (2) I
> build using both x86 and powerpc architectures.
> 
>    The build seems to have been broken by commit:
> cd8d60a20a4516016c117ac0f1ac7b06ff606f7e 
> 
>    I'm attaching  a patch  that fixes both  issues on my  system. Feel
> free to tweak/adapt if you see any problems with it.
> 
>    Cheers,
> 
> 		Livio
> 
> Signed-off-by: Livio Soares <livio@eecg.toronto.edu>
> 
> From 24aa58ab53b9adfa1a6f8269e470d5f554627be9 Mon Sep 17 00:00:00 2001
> From: Livio Soares <livio@eecg.toronto.edu>
> Date: Mon, 17 Jan 2011 15:29:06 -0500
> Subject: [PATCH] Two fixes to builddeb script, regarding the built of header package:
> 
> 1) Previous behavior assumed the build was executed inside the
>    source tree (no 'O=' option).
> 
> 2) Previous behavior assumed 'x86' architecture.
> ---
>  scripts/package/builddeb |   10 +++++-----
>  1 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/scripts/package/builddeb b/scripts/package/builddeb
> index b0b2357..418d3fa 100644
> --- a/scripts/package/builddeb
> +++ b/scripts/package/builddeb
> @@ -238,13 +238,13 @@ EOF
>  fi
>  
>  # Build header package
> -find . -name Makefile -o -name Kconfig\* -o -name \*.pl > /tmp/files$$
> -find arch/x86/include include scripts -type f >> /tmp/files$$
> -(cd $objtree; find .config Module.symvers include scripts -type f >> /tmp/objfiles$$)
>  destdir=$kernel_headers_dir/usr/src/linux-headers-$version
>  mkdir -p "$destdir"
> -tar -c -f - -T /tmp/files$$ | (cd $destdir; tar -xf -)
> -(cd $objtree; tar -c -f - -T /tmp/objfiles$$) | (cd $destdir; tar -xf -)
> +(cd $srctree; find . -name Makefile -o -name Kconfig\* -o -name \*.pl > /tmp/files$$;
> +    find arch/${SRCARCH}/include include scripts -type f >> /tmp/files$$;
> +    tar -c -f - -T /tmp/files$$ | (cd $destdir; tar -xf -) )
> +(cd $objtree; find .config Module.symvers include scripts -type f >> /tmp/objfiles$$; 
> +    tar -c -f - -T /tmp/objfiles$$ | (cd $destdir; tar -xf -) )
>  rm -f /tmp/files$$ /tmp/objfiles$$
>  arch=$(dpkg --print-architecture)
>  


       reply	other threads:[~2011-01-17 22:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D34C237.306@eecg.toronto.edu>
2011-01-17 22:32 ` Michal Marek [this message]
2011-01-18 11:24   ` [PATCH] Fix for scripts/builddeb (non-x86, and with output option) maximilian attems
2011-01-18 14:00     ` maximilian attems

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D34C38F.70807@suse.cz \
    --to=mmarek@suse.cz \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=livio@eecg.toronto.edu \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox