From: Roland Hieber <rohieb@rohieb.name>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] ibrdtn: add packaging rules for IBR-DTN and dtndht
Date: Sun, 28 Aug 2016 07:27:06 +0200 [thread overview]
Message-ID: <c7b66471-b33f-4000-3d16-31bcc9a045f5@rohieb.name> (raw)
In-Reply-To: <20160818065342.463fc7qfeixtb4vt@pengutronix.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 2528 bytes --]
Hi,
Thanks for the feedback!
On 18.08.2016 08:53, Michael Olbrich wrote:
> I've made several comments below, that apply to more that one place. Please
> fix it everywhere.
>
> And check your configure options. You need to specify everything that is
> optional or may be auto detected. Please look at some other rules for
> guidance or ask me if you are unsure if an option should be specified.
Okay, everything optional or auto-detected should be pinned down now.
I've basically ignored every configure option relating to the toolchain,
like --enable-static, --enable-maintainer-mode, --with-pic,
--with-gnu-ld, etc. Some of the packages take paths for CPPUnit, but I
ignored that too since tests are not run.
>> diff --git a/projectroot/lib/systemd/system/ibrdtnd.service b/projectroot/lib/systemd/system/ibrdtnd.service
>> [...]
>> +[Service]
>> +ExecStartPre=/bin/mkdir -p /etc/ibrdtn/bpsec /etc/ibrdtn/certs
>> +ExecStartPre=/bin/chown root:root -R /etc/ibrdtn/bpsec /etc/ibrdtn/certs
>
> The rootfs may be read-only. These directories should be created in the
> targetinstall stage.
Right! I now mkdir'd the folder in the targetinstall stage using
${ROOTDIR}, but it seems the rootdir contents are all created with my
user and chown'd to root in the images stage later, so I didn't care for
chown'ing them in the targetinstall stage (which additionally would have
required (fake)root while building).
> Break like this:
>
> DTNDHT_CONF_OPT := \
> $(CROSS_AUTOCONF_USR) \
>> + --$(call ptx/wwo, PTXCONF_DTNDHT_WITH_OPENSSL)-openssl \
>
> no '\' for the last line.
Old habit of mine to get fewer unneccessary changes in diffs when adding
options in the future. But okay, I've left it out for now :)
I also added a LIBC_M dependency in the packages that needed it because
the build output showed "-lm" in libtool calls. I tried to discover
additional runtime dependencies, but didn't find a good way to determine
which objects are loaded at run time – on my machine I would have used
ldd for that, but I can't do that for ARM binaries. Is there a way
without actually running the binary (in qemu)? The Guru Guide chapter
on Managing External Runtime Dependencies is very sparse on that topic.
For the ibr* packages I also added the GitHub releases as additional
URLs, but the dtndht tarballs on GitHub have different checksums than
the tarballs from the official site. Is there a way to handle that
(other than ignore one site)?
- Roland
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-08-28 5:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 14:53 Roland Hieber
2016-08-18 6:53 ` Michael Olbrich
2016-08-23 4:41 ` Roland Hieber
2016-08-25 11:02 ` Michael Olbrich
2016-08-25 15:11 ` Robert Schwebel
2016-08-28 5:27 ` Roland Hieber [this message]
2016-08-28 7:36 ` Robert Schwebel
2016-08-28 18:36 ` Roland Hieber
2016-09-01 9:58 ` Michael Olbrich
2016-09-01 15:09 ` Alexander Dahl
2016-08-29 7:42 ` Juergen Borleis
2016-08-18 10:15 ` Michael Olbrich
2016-08-28 5:32 ` [ptxdist] [PATCH v2] " Roland Hieber
2016-09-07 13:48 ` Michael Olbrich
2016-09-08 1:07 ` Roland Hieber
2016-09-08 6:35 ` 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=c7b66471-b33f-4000-3d16-31bcc9a045f5@rohieb.name \
--to=rohieb@rohieb.name \
--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