[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [coldsync-hackers] understanding the configure script



On Tue, 29 Oct 2002, David Banning wrote:
> I am moving along here on getting this working on my FreeBSD
> machine. You are recommending (via FAQ) that I use USB support.
> In fact, that is the default for FreeBSD. The problem is that
> the configure script seems to not acknowledge the USB support.
>
> I have checked the 3 files/variables that are checked by the script
> and confirmed that they are there.
>
> I wonder, when it's looking for and evaluating whether certain files
> are there, whether it has the base path wrong.
>
> My problem is that I don't understand the programming well enough to
> know -where- and -how- it's looking for the files/variables.
>
> If it's there, I don't see it, or I don't understand the logic.
>
> Can someone help me along here?
> Maybe it calling a routine in another file?
>
> The area of the configure file I indentify follows;

	You may want to look at "configure.in" rather than "configure",
since "configure" is generated from "configure.in".

> echo "configure:3897: checking for BSD USB support" >&5
>
>         # This code snippet checks several things:
>         #   1) <dev/usb/usb.h> exists
>         #   2) It contains 'struct usb_device_info'
>         #   3) That struct contains a 'vendorNo' field.
>         # All three conditions must be true for USB support to be enabled
>         cat > conftest.$ac_ext <<EOF
> #line 3905 "configure"
> #include "confdefs.h"
>                 #include <dev/usb/usb.h>
> int main() {
>                 struct usb_device_info udi;
>                  udi.vendorNo = 0x082d;
> ; return 0; }
> EOF

	This snippet of code is the real core of the configuration:
'configure' tries to compile this program, and if it compiles, then the
machine has USB support. If not, then it doesn't.
	If you think this has failed, then take a look at "config.log",
which should give details on exactly what failed, how the compiler was
invoked, and so forth. Try compiling it by hand and see what happens.

-- 
Andrew Arensburger                      Actually, these _do_ represent the
arensb@ooblick.com                      opinions of ooblick.com!
                        Generic Tagline V 6.01


-- 
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.