From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Message-ID: <52540217.3020608@pengutronix.de> Date: Tue, 08 Oct 2013 15:01:11 +0200 From: Marc Kleine-Budde MIME-Version: 1.0 References: <24635EE72167A34F98C0A19CAD298DE7149E4775@SBS01.phenom.local> In-Reply-To: <24635EE72167A34F98C0A19CAD298DE7149E4775@SBS01.phenom.local> Subject: Re: [ptxdist] Where do configure options for simple autotools packages come from? Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0266392545==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Cc: Sander Stoks This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============0266392545== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VMQORu88aAVFshfOJ4JS31BwAdTHMMcVS" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --VMQORu88aAVFshfOJ4JS31BwAdTHMMcVS Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 10/08/2013 02:44 PM, Sander Stoks wrote: > Hello, >=20 > =20 >=20 > 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 th= e > manual that if a source package is =E2=80=9Cautotoolized=E2=80=9D, i.e.= , contains a > simple =E2=80=9Cconfigure=E2=80=9D script, there is no need for a rules= file =E2=80=93 I assume > it will simply call ./configure, with the necessary parameters to enabl= e > cross compiling. >=20 > =20 >=20 > However, it seems to add other things too, and I can=E2=80=99t figure o= ut where > it finds these options. When I do this: >=20 > =20 >=20 > ptxdist prepare cifs-utils >=20 > =20 >=20 > and look in the build-target/cifs-utils-5.2/config.log, I see that it > has been configured with =E2=80=93disable-cifsupcall =E2=80=93disable-c= ifscreds > =E2=80=93disable-cifsidmap =E2=80=93disable-cifsacl, among some other s= tuff. But if I > go into this directory myself and do a simple ./configure there, then > these flags are **not** added. >=20 > =20 >=20 > So how does =E2=80=9Cptxdist prepare=E2=80=9D decide what exactly to ad= d to the > ./configure command line? In "rules/cifs-utils.make" line 32ff. regards, Marc --=20 Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions | Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de | --VMQORu88aAVFshfOJ4JS31BwAdTHMMcVS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlJUAhcACgkQjTAFq1RaXHOZFgCaAymWvFm0tLdVDn1m7nh+0hgP /R0AniHAd07ZgcejUcJFbFlJWJ+Np1FU =jbND -----END PGP SIGNATURE----- --VMQORu88aAVFshfOJ4JS31BwAdTHMMcVS-- --===============0266392545== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ptxdist mailing list ptxdist@pengutronix.de --===============0266392545==--