A build that is OK if workdir is in RAMFS, fails if workdir is in BFS.

[OscarL]

Got an interesting case (and not sure if the issue belongs here or on Haiku's Trac).

Building this version of the libigloo recipe worked fine locally for me, but failed on the package builders.

After some trial and error, found that the build works everytime if the workdir is located in RAMFS (I'm using OUTPUT_DIRECTORY=/RAMDRIVE in haikuports.conf), and consistently fails when the workdirs are in BFS (just commenting out that OUTPUT_DIRECTORY line in the config).

Relevant portions of the build logs:

on RAMFS:

[...]
configure: creating ./config.status
config.status: creating Makefile
config.status: creating igloo.pc
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
make  all-am
make[1]: Entering directory '/sources/libigloo-0.9.2'
[...]

on BFS:

[...]
configure: creating ./config.status
config.status: creating Makefile
config.status: creating igloo.pc
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
 cd . && /bin/sh /sources/libigloo-0.9.2/build-aux/missing automake-1.16 --foreign
/sources/libigloo-0.9.2/build-aux/missing: line 81: automake-1.16: command not found
WARNING: 'automake-1.16' is missing on your system.
         You should only need it if you modified 'Makefile.am' or
         'configure.ac' or m4 files included by 'configure.ac'.
         The 'automake' program is part of the GNU Automake package:
         <https://www.gnu.org/software/automake>
         It also requires GNU Autoconf, GNU m4 and Perl in order to run:
         <https://www.gnu.org/software/autoconf>
         <https://www.gnu.org/software/m4/>
         <https://www.perl.org/>
make: *** [Makefile:689: Makefile.in] Error 1
[...]

Not idea how far off am I but... could it be a difference in file's timestamps handling on RAMFS vs BFS, that could cause the config script to believe that some file were modified, and thus why it wants to call automake?

Would be nice to not be forced to add "unneeded" dependencies here, but I will have to add a couple (aclocal/autoreconf) to make it work for now.

[jmairboeck]

This is likely a Haiku issue, either in BFS or RAMFS, if it is caused by file timestamps.

[korli]

When a generated file is older than its dependencies, configure wants to regenerate. The trick is to define variables like ACLOCAL, etc: https://github.com/haikuports/haikuports/blob/5cb48c106a01fde9d33ddb823b52bdb4a3e8b799/app-arch/bzip3/bzip3-1.5.1.recipe#L62

[waddlesplash]

This is likely a Haiku issue, either in BFS or RAMFS, if it is caused by file timestamps.

It's in BFS: https://dev.haiku-os.org/ticket/19213