Bump :)
On 6 August 2015 at 16:38, Albert Antony <alb...@newtec.dk> wrote:
> Signed-off-by: Albert Antony <alb...@newtec.dk>
> ---
> rules/systemd.in | 14 ++
> rules/systemd.make | 8 +++-
> 2 files changed, 21 insertions(+), 1 deletion(-)
>
>
Sure. Updated patch on its way :)
Cheers,
Albert.
On 6 August 2015 at 10:41, Juergen Borleis j...@pengutronix.de wrote:
Hi Albert,
On Wednesday 05 August 2015 16:00:52 Albert Antony wrote:
Signed-off-by: Albert Antony alb...@newtec.dk
---
rules/systemd.in | 5 +
rules/systemd.make
Signed-off-by: Albert Antony alb...@newtec.dk
---
rules/systemd.in | 14 ++
rules/systemd.make | 8 +++-
2 files changed, 21 insertions(+), 1 deletion(-)
diff --git a/rules/systemd.in b/rules/systemd.in
index 979e32c..1ecdb2b 100644
--- a/rules/systemd.in
+++ b/rules
Signed-off-by: Albert Antony alb...@newtec.dk
---
rules/systemd.in | 5 +
rules/systemd.make | 8 +++-
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/rules/systemd.in b/rules/systemd.in
index 979e32c..f5f17ae 100644
--- a/rules/systemd.in
+++ b/rules/systemd.in
@@ -94,5
2015 16:03:36 Albert Antony wrote:
On 21 July 2015 at 15:14, Juergen Borleis j...@pengutronix.de wrote:
Why do you want to have libraries *with* debug information in your root
filesystem?
It just facilitates easier debugging in our case. We can run gdb on
the target directly, instead of via
in. I just
thought it was better to let the user have a say in the
stripped-vs-unstripped install, with the default of course being a
stripped install.
Cheers,
Albert.
On 22 July 2015 at 11:29, Juergen Borleis j...@pengutronix.de wrote:
Hi Albert,
On Wednesday 22 July 2015 10:31:45 Albert Antony
Sincere apologies for missing that. I'll send along a patch that addresses
the strip option for library installation in general. Let's abandon this
patch.
Cheers,
Albert.
On 20 July 2015 at 17:18, Marc Kleine-Budde m...@pengutronix.de wrote:
On 07/20/2015 05:11 PM, Albert Antony wrote
The strip y|n option should now work for install_lib
and install_copy_toolchain_lib, just like it works
for install_copy.
Signed-off-by: Albert Antony alb...@newtec.dk
---
rules/post/install.make | 3 ++-
scripts/install_copy_toolchain.sh | 2 +-
scripts/lib/ptxd_make_xpkg_pkg.sh | 3
the same then I guess
there is no need for it. Could you point me to where I can find out more
about auto-detection?
Cheers,
Albert.
On 21 July 2015 at 12:26, Michael Olbrich m.olbr...@pengutronix.de wrote:
On Tue, Jul 21, 2015 at 12:09:38PM +0200, Albert Antony wrote:
The strip y|n option
Hi Juergen,
On 21 July 2015 at 15:14, Juergen Borleis j...@pengutronix.de wrote:
Why do you want to have libraries *with* debug information in your root
filesystem?
It just facilitates easier debugging in our case. We can run gdb on
the target directly, instead of via gdbserver.
Given that
The option was not being passed onward, which meant that
the strip parameter passed to install_copy_toolchain_lib
was getting ignored.
---
scripts/install_copy_toolchain.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/install_copy_toolchain.sh
Hopefully the tabs are preserved in this version of the patch ;)
Signed-off-by: Albert Antony alb...@newtec.dk
---
projectroot/lib/systemd/system/crond.service | 11 +++
rules/busybox.in | 6 ++
rules/busybox.make | 7 +++
3
Signed-off-by: Albert Antony alb...@newtec.dk
---
projectroot/lib/systemd/system/crond.service | 11 +++
rules/busybox.in | 6 ++
rules/busybox.make | 7 +++
3 files changed, 24 insertions(+)
create mode 100644 projectroot
I know. It's on my todo list, but I've not found the time to implement
this
yet.
Send patches :-)
Michael
Here is an updated ptxdist-2013.01.0 patch for x86_64 support:
Index: b/platforms/architecture.in
===
---
I know. It's on my todo list, but I've not found the time to implement this
yet.
Send patches :-)
Michael
The following patch works for me. Have only patched files for the packages
I am using. Comments and suggestions appreciated :)
Cheers,
Albert.
Index:
Ah! GMail formatting messed up the previous patch. Here it is again...
in plain text :)
Albert.
Index: ptxdist-2013.01.0/platforms/architecture.in
===
--- ptxdist-2013.01.0.orig/platforms/architecture.in2013-01-08
Hi,
I am trying to build the kernel and userland for an x86_64 target using
PTXdist 2013.01.0 and the x86_64 OSELAS toolchain. Which CPU architecture
and optimization should I select in platformconfig? There isn't an x86_64
option there.
Thanks,
Albert.
--
ptxdist mailing list
BUG: BUSYBOX_IFUPDOWN requires BUSYBOX_RUN_PARTS but does not select it.
Observed in Ptxdist version: 2012.10.0
Patch needed in
installdir/lib/ptxdist-2012.10.0/config/busybox/networking/Config.in
Patch attached.
Cheers,
Albert.
busybox-ifupdown.patch
Description: Binary data
--
ptxdist
Hi,
Is it possible to have custom scripts that execute after
world.targetinstall? If so, how can they be added to the build?
Thanks and best regards,
Albert.
--
ptxdist mailing list
ptxdist@pengutronix.de
19 matches
Mail list logo
