From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] advice on makefile
Date: Thu, 10 Apr 2008 13:56:57 +0200 [thread overview]
Message-ID: <87tzi9apo6.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1207827171.6817.432.camel@nigel-x60> (Nigel Kukard's message of "Thu\, 10 Apr 2008 11\:32\:51 +0000")
>>>>> "Nigel" == Nigel Kukard <nkukard@lbsd.net> writes:
Hi,
Nigel> find $(RPM_DIR) -name '*.rej' | xargs --no-run-if-empty rm
>>
>> What are those .rej files?
Nigel> RPM5 v4.4.9 contained .rej files in the tar.gz, which made patch-kernel
Nigel> choke. Dirty I know ... but yea
Yddrk.
>> Please use sed for replacing text.
Nigel> Removed that line. it was hanging around from my previous
Nigel> cleanup ... :\
Ok.
>> It looks like you need to depend on beecrypt and neon installing into
>> STAGING_DIR.
Nigel> I do this later on....
Nigel> rpm: libbeecrypt libneon libpopt ...
Nigel> Problem is I don't want to depend on the fixed library names
Nigel> .... would you suggest I depend on
Nigel> $(STAGING_DIR)/usr/lib/libbeecrypt.so ... etc?
Yes, but that breaks parallel builds. You have to tell make that it
cannot start the configure step until those other libraries are
installed into STAGING_DIR.
I know that the current approach of having to hardcode the file name
used in the library .mk isn't really nice. We should probably come up
with an agreement regarding a fixed target name / file for libraries
to clean this up. Notice that this has to be a physical file name as a
PHONY target like <package>-staging-install always will be considered
out-of-date, so the configure target will rerun everytime you run
make.
You can see the avahi package for an example.
>> Is all of this needed? Normally you just need to set prefix=/usr and
>> use DESTDIR when installing into STAGING_DIR / TARGET_DIR.
Nigel> I can try filter it out a bit, but 4.4.9 was very very picky.
Ok.
Nigel> --program-prefix= \
Nigel> --disable-build-versionscript \
Nigel> --without-selinux \
Nigel> --without-python \
>>
>> We have a python package. Maybe we should add something like the
>> DISABLE_NLS stuff for it?
Nigel> Lets get rpm in without python, then improve on the extras later :)
Ok, it was more of generic note.
Nigel> mandir=$(STAGING_DIR)/usr/man \
>>
>> Is this needed? Doesn't make install support DESTDIR=$(STAGING_DIR)?
Nigel> 4.4.9 was a nightmare ... I started from scratch, then added line by
Nigel> line. I'll try 5.0.x and filter out.
Ok.
>> Well, RPM_BINARIES=rpm, so if you don't forsee more programs to be
>> added, just drop the loop.
Nigel> yea ... i'm busy trying to determine if more are required
Ok.
Nigel> rpm: libbeecrypt libneon libpopt $(RPM_TARGET_LIBS) $(RPM_TARGET_BINARIES)
>>
>> The rpm target shouldn't depend on the full installation in TARGET_DIR
>> of libeecrypt / libneon / libpopt, instead the configure target should
>> depend on those libraries installing into $(STAGING_DIR).
Nigel> I looked in some other .mk's and saw they normally depend on
Nigel> the package name?
Yeah, quite some packages are broken in this regard :/
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-04-10 11:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 11:32 [Buildroot] advice on makefile Nigel Kukard
2008-04-10 11:56 ` Peter Korsgaard [this message]
2008-04-10 14:11 ` Nigel Kukard
2008-04-10 14:35 ` Peter Korsgaard
2008-04-10 14:51 ` Nigel Kukard
2008-04-12 9:25 ` Hamish Moffatt
2008-04-12 13:16 ` Peter Korsgaard
2008-04-10 17:28 ` Nigel Kukard
2008-04-10 17:30 ` Nigel Kukard
2008-04-10 18:09 ` Peter Korsgaard
[not found] ` <1207851468.6817.498.camel@nigel-x60>
2008-04-10 18:59 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2008-04-10 7:52 Nigel Kukard
2008-04-10 8:37 ` Peter Korsgaard
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=87tzi9apo6.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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