mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Tim Jaacks <tim.jaacks@garz-fricke.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] Problem while using PTXdist with external kernel dir
Date: Thu, 10 May 2012 11:45:44 +0200	[thread overview]
Message-ID: <D99582E5322435468A77E74BB0039E7B1D23C4F623@SRV02.hamburg.garz-fricke.de> (raw)

Hello,

we are using PTXdist with an external kernel dir in local_src. The directories are correctly used, the
extract step says " local directory instead of tar file, linking build dir". If we call "ptxdist go", the
whole platform gets correctly built.
However, the directories we created (local_src/kernel.<platform> and
local_src/kernel-header.<platform>) are only links to other places in our build tree. Sometimes we
delete those links (when switching between different platforms) and re-create them later on (targeting
the same, unchanged directory). If we now re-run "ptxdist go", the kernel-header package sometimes gets
rebuilt, even though the state files are still present and nothing changed within the build tree. We have
not managed to determine under which exact circumstances this happens, sometimes it gets rebuilt,
sometimes not.
Does anybody have an idea, why this is the case and how we can prevent this? It is quite annoying, because we
have a lot of packages which depend on the kernel headers, which are then rebuilt as well, and that takes a
lot of time.

Mit freundlichen Grüßen / Best regards
Tim Jaacks

Development Engineer
Garz & Fricke GmbH
Tempowerkring 2, 21079 Hamburg - Germany
Amtsgericht Hamburg HRB 60514
Geschäftsführer: Manfred Garz, Matthias Fricke
Phone: +49 40 791899 - 55
Fax:   +49 40 791899 - 39
www.garz-fricke.com

-- 
ptxdist mailing list
ptxdist@pengutronix.de

                 reply	other threads:[~2012-05-10  9:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=D99582E5322435468A77E74BB0039E7B1D23C4F623@SRV02.hamburg.garz-fricke.de \
    --to=tim.jaacks@garz-fricke.com \
    --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