From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from remote.phenom-world.com ([88.159.5.253]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1VTWeR-00036m-PV for ptxdist@pengutronix.de; Tue, 08 Oct 2013 14:44:37 +0200 From: Sander Stoks Date: Tue, 8 Oct 2013 12:44:29 +0000 Message-ID: <24635EE72167A34F98C0A19CAD298DE7149E4775@SBS01.phenom.local> Content-Language: en-US MIME-Version: 1.0 Subject: [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="===============0611037264==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: "ptxdist@pengutronix.de" --===============0611037264== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_24635EE72167A34F98C0A19CAD298DE7149E4775SBS01phenomloca_" --_000_24635EE72167A34F98C0A19CAD298DE7149E4775SBS01phenomloca_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, I am trying to understand how ptxdist decides which configuration options t= o 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" sc= ript, there is no need for a rules file - I assume it will simply call ./co= nfigure, 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 and look in the build-target/cifs-utils-5.2/config.log, I see that it has b= een configured with -disable-cifsupcall -disable-cifscreds -disable-cifsidm= ap -disable-cifsacl, among some other stuff. But if I go into this directo= ry myself and do a simple ./configure there, then these flags are *not* add= ed. So how does "ptxdist prepare" decide what exactly to add to the ./configure= command line? Kind thanks in advance, Sander Stoks --_000_24635EE72167A34F98C0A19CAD298DE7149E4775SBS01phenomloca_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

 

I am trying to understand how p= txdist 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 s= imple “configure” script, there is no need for a rules file = 211; I assume it will simply call ./configure, with the necessary parameter= s 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=

 

and look in the build-target/ci= fs-utils-5.2/config.log, I see that it has been configured with –disa= ble-cifsupcall –disable-cifscreds –disable-cifsidmap –dis= able-cifsacl, among some other stuff.  But if I go into this directory myself and do a simple ./configure there, then these flags are *= not* added.

 

So how does “ptxdist prep= are” decide what exactly to add to the ./configure command line?=

 

Kind thanks in advance,

Sander Stoks<= /p>

 

--_000_24635EE72167A34F98C0A19CAD298DE7149E4775SBS01phenomloca_-- --===============0611037264== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ptxdist mailing list ptxdist@pengutronix.de --===============0611037264==--