From: Sander Stoks <Sander.Stoks@phenom-world.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
"ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Where do configure options for simple autotools packages come from?
Date: Tue, 8 Oct 2013 13:24:46 +0000 [thread overview]
Message-ID: <24635EE72167A34F98C0A19CAD298DE7149E48F8@SBS01.phenom.local> (raw)
In-Reply-To: <52540217.3020608@pengutronix.de>
Marc wrote:
>> So how does “ptxdist prepare” decide what exactly to add to the
>> ./configure command line?
> In "rules/cifs-utils.make" line 32ff.
Interesting - I thought all the rules files were under a local subdirectory. There are a bunch of .in and .make files in the "rules" subdirectory (but not the cifs-utils ones). I found these in /usr/local/lib/ptxdist-2013.04.0/rules.
I didn't want to edit those, but I found that simply copying the cifs-utils files to the "rules" directory in my own project hierarchy, successfully overrules the other ones.
However, it turns out these particular flags were not disabled for nothing: Some dependencies were missing, and they were disabled later on in the configuration anyway:
WARNING: krb5.h not found, consider installing krb5-libs-devel. Disabling cifs.upcall.
(same for keyutils-libs-devel and libwbclient-devel).
I guess I'll have to try and install packages for those as well...
Kind regards for the help so far,
Sander
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-10-08 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 12:44 Sander Stoks
2013-10-08 13:01 ` Marc Kleine-Budde
2013-10-08 13:24 ` Sander Stoks [this message]
2013-10-08 13:35 ` Marc Kleine-Budde
2013-10-08 13:20 ` Jürgen Beisert
[not found] ` <24635EE72167A34F98C0A19CAD298DE7149E497D@SBS01.phenom.local>
2013-10-08 13:58 ` Jürgen Beisert
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=24635EE72167A34F98C0A19CAD298DE7149E48F8@SBS01.phenom.local \
--to=sander.stoks@phenom-world.com \
--cc=mkl@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