On 01/07/2011 22:22, Drasko DRASKOVIC wrote:
On Fri, Jul 1, 2011 at 10:50 PM, Spencer Oliver<[email protected]> wrote:
On 01/07/2011 21:23, Drasko DRASKOVIC wrote:
Strange.
configure should be passing --disable-option-checking to any submodules.
can you try a test something like
./configure --enable-maintainer-mode --disable-option-checking ...
Yes, great ! Adding explicit --disable-option-checking option makes
./configure pass the critical point in jimctl and to continue to the
end :
Thats a start anyway :)
=== configuring in jimtcl (/home/ddraskovic/sandbox/github/openocd/jimtcl)
configure: running /bin/sh ./configure.gnu '--prefix=/usr/local'
'--enable-maintainer-mode' '--disable-option-checking'
'--enable-ft2232-libftdi' 'CFLAGS= -I/home/ddraskovic/libftdi/include'
'LDFLAGS= -L/home/ddraskovic/libftdi/lib' --cache-file=/dev/null
--srcdir=.
Host System...i686-pc-linux-gnu
Build System...i686-pc-linux-gnu
C compiler...ccache cc -I/home/ddraskovic/libftdi/include
C++ compiler...ccache c++ -I/home/ddraskovic/libftdi/include
Checking for stdlib.h...ok
Checking for long long...ok
Checking for sys/socket.h...ok
Checking for netinet/in.h...ok
Checking for arpa/inet.h...ok
Checking for netdb.h...ok
Should we *always* use this --disable-option-checking during
configuration or it should be done transparently by configure script
itself ?
It should be done by configure to all submodules.
But then again if the above was the cause then this would effect all builds.
Could you send the config.log of a working and non working configure?
Please find config.log for the cases with --disable-option-checking
and without (ends with ERROR) attached.
could you send the log of the previous working version where you did not
need to pass --disable-option-checking
Cheers
Spen
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
