> Regarding the 32/64 bit thing: > > maybe testing like this is a better way: > > if test "$(uname -m)" = "x86_64"; then
It puts you into the business of exhaustively listing every possible perversion of system/arch ids. Not very maintainable/scalable for the long term. A simpler solution would be to provide a --prefer-word-length=xxx directive to configure that defaults to 32 bit. The convention for machines with > 32 bit words appears to be to put the various libraries in /lib<xxx>/blah, so you could handle 32, 64, 128, etc bit machines (like Crays or POWER6 for example) and the packagers could supply the correct value when building the package. If omitted, you get the "default" 32 bits. If present, you list the /lib<xxx> dirs before the /lib dirs for any includes. For systems that support multiple word lengths (AIX, Solaris, UNICOS, Tru64, etc), you can specify it or let it default, which would also be well-behaved for cross-compilation or building packages for different releases. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
