On 10/08/2013 02:44 PM, Sander Stoks wrote:
> Hello,
> 
>  
> 
> 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 – 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
> 
>  
> 
> and look in the build-target/cifs-utils-5.2/config.log, I see that it
> has been configured with –disable-cifsupcall –disable-cifscreds
> –disable-cifsidmap –disable-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 prepare” decide what exactly to add to the
> ./configure command line?

In "rules/cifs-utils.make" line 32ff.

regards,
Marc

-- 
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   |