mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Custom kernel archive
Date: Wed, 4 Jan 2012 11:00:13 +0100	[thread overview]
Message-ID: <20120104100013.GF21393@pengutronix.de> (raw)
In-Reply-To: <CAM7q1Lmqvxm4AzKpzefpOXn_r4Xm1xe++=wDX1L-Qe+93RyLvA@mail.gmail.com>

Hi,

On Tue, Dec 27, 2011 at 02:02:37PM -0800, Jeff Horn wrote:
> I am using Ptxdist 2011.07.0 and I am trying to build the kernel from an
> archive generated by git archive.  I have a local kernel git tree and once
> the kernel is built and tested (loaded over nfs) I thought I could compress
> it and add it to the src directory and then add the version to my platform
> config.  When I do that I get several errors that mv will not overwrite
> just created during extract.  If I manually uncompress the archive and then
> just add the kernel state flags the compile stage works fine.  I'm not
> using the local kernel option because I was hoping I could just add the
> archive to the src folder and have the build run from that.  Does this
> sound doable?

It should work. Is this a clean build? What's the exact error? Please send
the relevant section of the logfile.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2012-01-04 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-27 22:02 Jeff Horn
2012-01-04 10:00 ` Michael Olbrich [this message]
2012-01-06 17:09   ` Jeff Horn

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=20120104100013.GF21393@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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