Duane Ellis wrote:
Dirk>> Btw.: For ftd2xx: Do you like to add the host_os = linux part of
the patch I just sent?
**COMMITTED** - partially.
I fixed the "host_os=linux-gnu" problem. - via portions of your patch.
You did it correctly.
I'm not sure about the other part, where you mess with the prefix...
You are right with "mess".
Are you sure that is still needed?
No, not needed any more.
Or did my earlier commit fix this?
Yes. As I'm no configure expert I did the prefix stuff wrong and your
changes fix it correctly.
====
As for "linux" verses "linux-gnu" .... I do not know...
Perhaps you have a *NEWER* or *DIFFERENT* version of 'config.guess' on
your pc.
Different distribution:
> ./config.guess
i686-suse-linux
I wonder how many other bumps we will find :-(
Let us see ;)
Thanks for your fixes!
The changes in attachment fix a
checking for libftd2xx.a (linux)... ./configure: line 5512: linux:
command not found
warning for me.
Dirk
Btw.: I'm dirk2 at #openjtag. Sometimes IRC can be faster than mails ;)
Add missing ';' and 'test'.
Signed-off-by: Dirk Behme <[email protected]>
---
configure.in | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Index: trunk/configure.in
===================================================================
--- trunk.orig/configure.in
+++ trunk/configure.in
@@ -55,7 +55,7 @@ then
LDFLAGS="$LDFLAGS -L$OCDxprefix/lib"
# RPATH becomes an issue on Linux only
- if test $host_os = linux-gnu || $host_os = linux
+ if test $host_os = linux-gnu || test $host_os = linux ;
then
LDFLAGS="$LDFLAGS -Wl,-rpath,$OCDxprefix/lib"
fi
@@ -500,7 +500,7 @@ if test $build_ft2232_ftd2xx = yes ; the
AC_MSG_CHECKING([for libftd2xx.a (linux)])
# Must be linux -
# Cause FTDICHIP does not supply a MAC-OS version
- if test $host_os != linux-gnu && $host_os != linux ; then
+ if test $host_os != linux-gnu && test $host_os != linux ; then
AC_MSG_ERROR([The (linux) ftd2xx library from FTDICHIP.com is linux
only. Try --enable-ft2232-libftdi instead])
fi
# Are we given a TAR directory?
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
