Incomplete configure (autoconfig)
Posted: Fri Jan 30, 2009 5:37 am
I'm just wondering, when I call configure (the autoconfig script) and it's checking my system, why do some things say "no" yet the the program still compiles.
e.g.
Why would it check for "sys/pstat.h" if it didn't depend on it? Yet it compiles fine without it. Does the code change to adapt to not having that file?
I've noticed some other things fail as well, like checking for compiler features or certain functions, yet it still builds.
How are these tests performed:
By parsing the headers or compiling sample code? (which seems like a lot)
Also, it determined I had a functioning C compiler, then a while later I saw:
!
e.g.
Code: Select all
checking for sys/file.h... yes
checking for sys/param.h... yes
checking for limits.h... yes
checking for stdlib.h... yes
checking for malloc.h... yes
checking for string.h... yes
checking for unistd.h... yes
checking for strings.h... yes
checking for sys/time.h... yes
checking for time.h... yes
checking for sys/resource.h... yes
checking for sys/stat.h... yes
checking for sys/mman.h... yes
checking for fcntl.h... yes
checking for alloca.h... yes
checking for sys/pstat.h... no
checking for sys/sysmp.h... no
checking for sys/sysinfo.h... no
checking for machine/hal_sysinfo.h... no
checking for sys/table.h... no
checking for sys/sysctl.h... no
checking for sys/systemcfg.h... no
checking for stdint.h... yes
checking for stdio_ext.h... noI've noticed some other things fail as well, like checking for compiler features or certain functions, yet it still builds.
How are these tests performed:
Code: Select all
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yesAlso, it determined I had a functioning C compiler, then a while later I saw:
Code: Select all
checking for int... yes