muniversal and use_autoconf

Joshua Root jmr at macports.org
Mon Aug 3 00:42:08 PDT 2009


On 2009-8-3 16:35, Jeremy Huddleston wrote:
> It looks like updated configure scripts (via use_autoconf) aren't
> getting propagated to the arch-specific dir.  Has something changed
> recently in recent base+muniversal that might be affecting this, or is
> it an outstanding issue?
> 
> ~/src/macports-trunk/dports/audio/cdparanoia $ ls -l
> work/cdparanoia-III-10.2*/configure
> -rwxrwxr-x  1 root  wheel  176456 Aug 16  2006
> work/cdparanoia-III-10.2-x86_64/configure
> -rwxrwxr-x  1 root  wheel  146246 Aug  2 23:25
> work/cdparanoia-III-10.2/configure
> 
> ~/src/macports-trunk/dports/audio/cdparanoia $ grep autoconf Portfile
> depends_build    port:autoconf
> use_autoconf    yes
> 
> 
> I filed a ticket since I couldn't find an existing one...
> http://trac.macports.org/ticket/20534

The auto* commands get run in configure_main, so if you override the
configure phase (as muniversal does), that never happens unless you do
it yourself.

- Josh


More information about the macports-dev mailing list