Create a cache file with the right values, or call configure with those values set in the environment.
OK, i ran configure with -C one time without cross compiler env set, to obtain the variables another time with -C to use the config.cache . I could not find anything related to the check whether size_t is signed. I found a variable which i set that way:
ignored_signed_size=${ignore_signed_size=1}
What's wrong with that?
Cheers Martin
P.S.: Is there a way to obtain all variables in an easy way, or to obtain the variable that has to be set by hand?
Frag' nicht - Du könntest eine Antwort erhalten. (Markus Mehring in d.a.arnooo)
On December 29, 2006 11:50:33 PM +0100 Martin Höfling <martin.hoefling@gmx.de> wrote:
Create a cache file with the right values, or call configure with those values set in the environment.
OK, i ran configure with -C one time without cross compiler env set, to obtain the variables another time with -C to use the config.cache . I could not find anything related to the check whether size_t is signed. I found a variable which i set that way:
ignored_signed_size=${ignore_signed_size=1}
What's wrong with that?
Ah. In this case the configure test is a custom one and isn't written to support cross-compiling. You'll have to patch the configure script until Timo can fix it.
P.S.: Is there a way to obtain all variables in an easy way, or to obtain the variable that has to be set by hand?
Not that I know of.
-frank
On Fri, 2006-12-29 at 16:04 -0800, Frank Cusack wrote:
On December 29, 2006 11:50:33 PM +0100 Martin Höfling <martin.hoefling@gmx.de> wrote:
Create a cache file with the right values, or call configure with those values set in the environment.
OK, i ran configure with -C one time without cross compiler env set, to obtain the variables another time with -C to use the config.cache . I could not find anything related to the check whether size_t is signed. I found a variable which i set that way:
ignored_signed_size=${ignore_signed_size=1}
What's wrong with that?
Ah. In this case the configure test is a custom one and isn't written to support cross-compiling. You'll have to patch the configure script until Timo can fix it.
I finally got around to doing this: http://dovecot.org/list/dovecot-cvs/2007-February/007748.html
Did I miss any checks?
participants (3)
-
Frank Cusack
-
Martin Höfling
-
Timo Sirainen