From: "Jürgen Beisert" <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Sander Stoks <Sander.Stoks@phenom-world.com>
Subject: Re: [ptxdist] Where do configure options for simple autotools packages come from?
Date: Tue, 8 Oct 2013 15:20:14 +0200 [thread overview]
Message-ID: <201310081520.14687.jbe@pengutronix.de> (raw)
In-Reply-To: <24635EE72167A34F98C0A19CAD298DE7149E4775@SBS01.phenom.local>
Hi Sander,
On Tuesday 08 October 2013 14:44:29 Sander Stoks wrote:
> I am trying to understand how ptxdist decides which configuration options
> to pass. My specific case is that I want to make a package for cifs-utils.
> I could not find any rules file for this, but I read in the manual that if
> a source package is "autotoolized", i.e., contains a simple "configure"
> script, there is no need for a rules file
Where did you read there is "not need for a rule file"? Each package in PTXdist
needs a rule file. The content of this rule may vary, depending on the
package's build system.
> I assume it will simply call
> ./configure, with the necessary parameters to enable cross compiling.
>
> However, it seems to add other things too, and I can't figure out where it
> finds these options. When I do this:
>
> ptxdist prepare cifs-utils
As Marc has stated: there is already a cifs-utils package present in PTXdist.
That is why it works in your case.
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-10-08 13:20 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
2013-10-08 13:35 ` Marc Kleine-Budde
2013-10-08 13:20 ` Jürgen Beisert [this message]
[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=201310081520.14687.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=Sander.Stoks@phenom-world.com \
--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