From: "Nicolas de Pesloüan" <nicolas.2p.debian@gmail.com>
To: John Stoffel <john@stoffel.org>
Cc: linux-kernel@vger.kernel.org, mmarek@suse.cz,
linux-kbuild@vger.kernel.org
Subject: Re: 2.6.38-rc3 - make deb-pkg bombs out
Date: Fri, 04 Feb 2011 09:02:14 +0100 [thread overview]
Message-ID: <4D4BB286.6090500@gmail.com> (raw)
In-Reply-To: <19787.9875.652.181110@quad.stoffel.home>
Le 03/02/2011 23:05, John Stoffel a écrit :
>>>>>> "John" == John Stoffel<john@stoffel.org> writes:
>
> I've updated this email to include the maintainer and the linux-kbuild
> mailing list.
>
> John> I've been trying to do a 'make deb-pkg' on 2.6.38-rc? and not
> John> having any luck. I was going to report this error for -rc2, but
> John> saw -rc3 this morning so I grabbed it and tried it out.
>
> John> I can successfully build the kernel on x86_64 (Ubuntu 10.10
> John> system, dual core Athlon, 4gb RAM, current directory mounted via
> John> NFS), but when I do:
>
> John> fakeroot make O=/var/tmp/build deb-pkg
>
> Turns out the problem is with the "O=/var/tmp/build" since it works to
> build the deb-pkg target in the current directory just fine, using the
> same .config and same arguements.
>
> I guess I'll start to bisect this and see when it last worked.
> Looking at the scripts/package/builddeb script, it just needs to be
> updated to use the O=/some/path in the find command. I think. But I
> don't know the build system at all.
Hi John,
I submitted a patch that fix this problem on January 24th.
http://www.spinics.net/lists/linux-kbuild/msg04131.html
Despite a Tested-by: and an Acked-by:, this patch apparently didn't reach main line until now.
Nicolas.
next prev parent reply other threads:[~2011-02-04 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 17:48 2.6.38-rc3 - make deb-pkg bombs out John Stoffel
2011-02-03 22:05 ` John Stoffel
2011-02-04 8:02 ` Nicolas de Pesloüan [this message]
2011-02-04 17:59 ` John Stoffel
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=4D4BB286.6090500@gmail.com \
--to=nicolas.2p.debian@gmail.com \
--cc=john@stoffel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.