Author wrobell
Recipients Arfrever, BreamoreBoy, David.Kern, Greg.Hellings, WhiteTiger, eric.araujo, rpetrov, wrobell
Date 2011-05-26.17:45:50
SpamBayes Score 6.3638e-05
Marked as misclassified No
Message-id <1306431951.28.0.0111112269967.issue3754@psf.upfronthosting.co.za>
In-reply-to
Content
looking into configure.in the above fails due to following check

  AC_MSG_CHECKING(for %lld and %llu printf() format support)

the check compiles and tries to _run_ a bit of software to determine lld/llu support.

that of course fails (we are cross compiling). this is similar problem to ptmx/ptc problem (we do not know if host have support for ptmx/ptc).

i wonder if the following would be acceptable

1. if in cross compilation mode, the configure.in could load config-cross.site.
2. the config-cross.site would define variables for ptmx/ptc, long long format and other checks which consist of running code snippets
3. appropriate checks (i.e. ptmx/ptc, lld/llu) would not be run in cross compilation mode. variables from config-cross.site would be used instead.
4. it would be a developer responsibility to set appropriate values for his platform in config-cross.site file.

does above sound like a solution?
History
Date User Action Args
2011-05-26 17:45:51wrobellsetrecipients: + wrobell, eric.araujo, rpetrov, Arfrever, WhiteTiger, BreamoreBoy, David.Kern, Greg.Hellings
2011-05-26 17:45:51wrobellsetmessageid: <1306431951.28.0.0111112269967.issue3754@psf.upfronthosting.co.za>
2011-05-26 17:45:50wrobelllinkissue3754 messages
2011-05-26 17:45:50wrobellcreate