From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC PATCH] doc: Add section on creating new layers
Date: Wed, 4 Sep 2019 12:30:58 +0200 [thread overview]
Message-ID: <20190904103058.jurluq6q35ysruas@pengutronix.de> (raw)
In-Reply-To: <20190903141202.hf3o753xvp6prbwk@pengutronix.de>
On Tue, Sep 03, 2019 at 04:12:02PM +0200, Michael Olbrich wrote:
> I cannot reproduce this. It works as expected for me. The last log message
> may be a clue, I would expect
>
> "Saving 'test-bsp/configs/platform-v7a/platformconfig'."
> or
> "Saving 'test-bsp/base/configs/platform-v7a/platformconfig'."
>
> but not "test-bsp/DistroKit/....". So maybe the symlink handling does not
> work correctly.
>
> What's the output of 'p migrate'?
See in the log below.
> What happens if 'base' is a symlink to '../DistroKit'?
I tried three different things:
1. clean DistroKit checked out as base/ directory inside the BSP:
=> works as intended.
rhi@dude test-bsp $ git clone ../DistroKit base
Cloning into 'base'...
done.
rhi@dude test-bsp $ ll
total 0
drwxr-xr-x 10 rhi ptx 212 Sep 3 15:55 base
rhi@dude test-bsp $ p menuconfig
error: 'selected_platformconfig' is missing
try 'ptxdist platform <platformconfig>'
rhi@dude test-bsp $ cd base/; p platform configs/platform-v7a/platformconfig; cd ..
info: selected platformconfig:
'configs/platform-v7a/platformconfig'
found and using toolchain:
'/opt/OSELAS.Toolchain-2018.12.0/arm-v7a-linux-gnueabihf/gcc-8.2.1-glibc-2.28-binutils-2.31.1-kernel-4.19-sanitized/bin'
rhi@dude test-bsp $ p menuconfig
[... change project name ...]
#
# configuration written to .config
#
configuration written to .config
*** End of the configuration.
*** Execute 'ptxdist go' to build the project or try 'ptxdist help'.
Saving 'test-bsp/configs/ptxconfig'.
Saving 'test-bsp/configs/ptxconfig.diff'.
rhi@dude test-bsp $ ll
total 0
drwxr-xr-x 10 rhi ptx 212 Sep 3 15:55 base
drwxr-xr-x 2 rhi ptx 66 Sep 4 10:59 configs
drwxr-xr-x 2 rhi ptx 78 Sep 4 10:59 platform-v7a
2. DistroKit checked out as DistroKit inside the BSP, symlink base/:
=> writes to the config in the wrong layer.
rhi@dude test-bsp $ git clone ../DistroKit DistroKit
Cloning into 'DistroKit'...
done.
rhi@dude test-bsp $ ln -s DistroKit/ base
rhi@dude test-bsp $ ll
total 0
lrwxrwxrwx 1 rhi ptx 10 Sep 4 11:55 base -> DistroKit/
drwxr-xr-x 10 rhi ptx 155 Sep 4 11:55 DistroKit
rhi@dude test-bsp $ p menuconfig
error: 'selected_platformconfig' is missing
try 'ptxdist platform <platformconfig>'
rhi@dude test-bsp $ cd base/; p platform configs/platform-v7a/platformconfig; cd ..
info: selected platformconfig:
'configs/platform-v7a/platformconfig'
found and using toolchain:
'/opt/OSELAS.Toolchain-2018.12.0/arm-v7a-linux-gnueabihf/gcc-8.2.1-glibc-2.28-binutils-2.31.1-kernel-4.19-sanitized/bin'
rhi@dude test-bsp $ p menuconfig
[... change project name ...]
configuration written to .config
*** End of the configuration.
*** Execute 'ptxdist go' to build the project or try 'ptxdist help'.
Saving 'test-bsp/DistroKit/configs/ptxconfig'.
rhi@dude test-bsp $ ll
total 0
lrwxrwxrwx 1 rhi ptx 10 Sep 4 11:55 base -> DistroKit/
drwxr-xr-x 10 rhi ptx 212 Sep 4 12:14 DistroKit
drwxr-xr-x 2 rhi ptx 78 Sep 4 12:14 platform-v7a
rhi@dude test-bsp $ p migrate
Updating 'test-bsp/DistroKit/configs/ptxconfig'...
#
# configuration written to .config
#
Updating 'test-bsp/DistroKit/configs/platform-v7a/platformconfig'...
#
# configuration written to .config
#
rhi@dude test-bsp $ ll
total 0
lrwxrwxrwx 1 rhi ptx 10 Sep 4 12:25 base -> DistroKit/
drwxr-xr-x 10 rhi ptx 212 Sep 4 12:25 DistroKit
drwxr-xr-x 2 rhi ptx 78 Sep 4 12:26 platform-v7a
3. DistroKit cloned outside the BSP, symlink base/
=> works as intended.
rhi@dude test-bsp $ git clone ../distrokit ../DistroKit
Cloning into '../DistroKit'...
done.
rhi@dude test-bsp $ ln -s ../DistroKit base
rhi@dude test-bsp $ ll
total 0
lrwxrwxrwx 1 rhi ptx 12 Sep 4 12:19 base -> ../DistroKit
rhi@dude test-bsp $ p menuconfig
error: 'selected_platformconfig' is missing
try 'ptxdist platform <platformconfig>'
rhi@dude test-bsp $ cd base/; p platform configs/platform-v7a/platformconfig; cd ..
info: selected platformconfig:
'configs/platform-v7a/platformconfig'
found and using toolchain:
'/opt/OSELAS.Toolchain-2018.12.0/arm-v7a-linux-gnueabihf/gcc-8.2.1-glibc-2.28-binutils-2.31.1-kernel-4.19-sanitized/bin'
rhi@dude test-bsp $ p menuconfig
[... change project name ...]
#
# configuration written to .config
#
configuration written to .config
*** End of the configuration.
*** Execute 'ptxdist go' to build the project or try 'ptxdist help'.
Saving 'test-bsp/configs/ptxconfig'.
Saving 'test-bsp/configs/ptxconfig.diff'.
rhi@dude dude test-bsp $ ll
total 0
lrwxrwxrwx 1 rhi ptx 12 Sep 4 12:19 base -> ../DistroKit
drwxr-xr-x 2 rhi ptx 66 Sep 4 12:20 configs
drwxr-xr-x 2 rhi ptx 78 Sep 4 12:19 platform-v7a
So it seems I hit a special case there in my last mail…
--
Roland Hieber | r.hieber@pengutronix.de |
Pengutronix e.K. | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-09-04 10:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 11:50 Alexander Dahl
2019-09-03 12:00 ` Roland Hieber
2019-09-03 12:22 ` Alexander Dahl
2019-09-03 13:08 ` Michael Olbrich
2019-09-03 13:38 ` Roland Hieber
2019-09-03 14:12 ` Michael Olbrich
2019-09-04 10:30 ` Roland Hieber [this message]
2019-09-04 12:55 ` Roland Hieber
2019-09-03 13:48 ` Alexander Dahl
2019-09-03 14:22 ` Michael Olbrich
2019-09-03 18:49 ` Alexander Dahl
2019-09-04 5:37 ` Michael Olbrich
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=20190904103058.jurluq6q35ysruas@pengutronix.de \
--to=rhi@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