Discussion:
[UrJTAG-dev] Failing to compile URJTAG
r***@web.de
2017-03-06 13:39:08 UTC
Permalink
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Geert Stappers
2017-03-06 15:20:51 UTC
Permalink
Greetings,
I am currently trying to compile UrJTAG using Cygwin after having added a
single fflush command to the code to receive the output without having to fill
the printf-buffer while redirecting the StandardOutput.
./configure --host=i586-mingw32msvc --with-ftd2xx=~/ftd2 --with-inpout32
After having added the ftd2xx.h file to the usbconn directories in
/tap and /include as an error message demanded of me, I seem to be
gcc  -g -O2 -I~/ftd2 -Wall   -o jtag.exe jtag.o -Lcmd -lcmd -Ltap -ltap -Lpart
-lpart -Llib -ljtaglib -Lflash -lflash -Ltap -ltap -Lflash -lflash -Lbus -lbus
-lm ~/ftd2/ftd2xx.lib -lintl -Lsvf -lsvf -Lbsdl -lbsdl   -lusb
/usr/lib/gcc/x86_64-pc-cygwin/5.4.0/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lpart
/usr/lib/gcc/x86_64-pc-cygwin/5.4.0/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lsvf
collect2: Fehler: ld gab 1 als Ende-Status zurück
As is apparent, the linker seems to be incompatible with libpart.a and libsvf.a.
I have added every single "devel" or library package the Cygwin setup offers me.
Does someone know what I am doing wrong?
libsvf and libpart are libraries generated from urjtag source.

I don't known how cygwin handles such libraries.

My advice is to compare the cygwin buildlog with a Linux buildlog such as
at https://buildd.debian.org/status/fetch.php?pkg=urjtag&arch=arm64&ver=0.10%2Br2052-1&stamp=1481752319&raw=0


Hope this helps
Regards
Geert Stappers
Åke Rehnman
2017-03-06 16:09:50 UTC
Permalink
Hi,

the problem probably arised much earlier where libpart and libsvf and
was compiled.

Run make again without cleaning and those errors should be clearly
visible through all garbage on the console.

As a side note, unless someone has fixed the configure script UrJtag
doesn't build under cygwin with ftdi-drivers.

/Ake
Post by Geert Stappers
Greetings,
I am currently trying to compile UrJTAG using Cygwin after having added a
single fflush command to the code to receive the output without having to fill
the printf-buffer while redirecting the StandardOutput.
./configure --host=i586-mingw32msvc --with-ftd2xx=~/ftd2 --with-inpout32
After having added the ftd2xx.h file to the usbconn directories in
/tap and /include as an error message demanded of me, I seem to be
gcc  -g -O2 -I~/ftd2 -Wall  -o jtag.exe jtag.o -Lcmd -lcmd -Ltap -ltap -Lpart
-lpart -Llib -ljtaglib -Lflash -lflash -Ltap -ltap -Lflash -lflash -Lbus -lbus
-lm ~/ftd2/ftd2xx.lib -lintl -Lsvf -lsvf -Lbsdl -lbsdl  -lusb
/usr/lib/gcc/x86_64-pc-cygwin/5.4.0/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lpart
/usr/lib/gcc/x86_64-pc-cygwin/5.4.0/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lsvf
collect2: Fehler: ld gab 1 als Ende-Status zurück
As is apparent, the linker seems to be incompatible with libpart.a and libsvf.a.
I have added every single "devel" or library package the Cygwin setup offers me.
Does someone know what I am doing wrong?
libsvf and libpart are libraries generated from urjtag source.
I don't known how cygwin handles such libraries.
My advice is to compare the cygwin buildlog with a Linux buildlog such as
at https://buildd.debian.org/status/fetch.php?pkg=urjtag&arch=arm64&ver=0.10%2Br2052-1&stamp=1481752319&raw=0
Hope this helps
Regards
Geert Stappers
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
UrJTAG-development mailing list
https://lists.sourceforge.net/lists/listinfo/urjtag-development
Geert Stappers
2017-03-06 16:15:43 UTC
Permalink
Post by Åke Rehnman
Post by Geert Stappers
I am currently trying to compile UrJTAG using Cygwin
./configure --host=i586-mingw32msvc --with-ftd2xx=~/ftd2 --with-inpout32
After having added the ftd2xx.h file to the usbconn directories in
/tap and /include as an error message demanded of me, I seem to be
gcc  -g -O2 -I~/ftd2 -Wall  -o jtag.exe jtag.o -Lcmd -lcmd -Ltap -ltap -Lpart
-lpart -Llib -ljtaglib -Lflash -lflash -Ltap -ltap -Lflash -lflash -Lbus -lbus
-lm ~/ftd2/ftd2xx.lib -lintl -Lsvf -lsvf -Lbsdl -lbsdl  -lusb
/usr/lib/gcc/x86_64-pc-cygwin/5.4.0/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lpart
/usr/lib/gcc/x86_64-pc-cygwin/5.4.0/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lsvf
collect2: Fehler: ld gab 1 als Ende-Status zurück
As is apparent, the linker seems to be incompatible with libpart.a and libsvf.a.
I have added every single "devel" or library package the Cygwin setup offers me.
Does someone know what I am doing wrong?
libsvf and libpart are libraries generated from urjtag source.
I don't known how cygwin handles such libraries.
My advice is to compare the cygwin buildlog with a Linux buildlog such as
at https://buildd.debian.org/status/fetch.php?pkg=urjtag&arch=arm64&ver=0.10%2Br2052-1&stamp=1481752319&raw=0
the problem probably arised much earlier where libpart and libsvf
and was compiled.
Run make again without cleaning and those errors should be clearly
visible through all garbage on the console.
And rerunning configure wouldn't harm.
Post by Åke Rehnman
As a side note, unless someone has fixed the configure script UrJtag
doesn't build under cygwin with ftdi-drivers.
These days we do accept patches.


Groeten
Geert Stappers
--
Leven en laten leven
Åke Rehnman
2017-03-06 16:30:58 UTC
Permalink
And these are the changes in the configure script. I don't recall
exactly why I just removed the check for mingw ONLY but what I do
remember is gcc will not link any libraries unless they start with lib.

So the workaround was to remove the check and rename the library to
libftd2xx.a if i recall...

/Ake

urjtag/configure.ac | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/urjtag/configure.ac b/urjtag/configure.ac
index 3c0ce81..7758fb4 100644
--- a/urjtag/configure.ac
+++ b/urjtag/configure.ac
@@ -295,7 +295,7 @@ AS_IF([test "x$with_ftd2xx" = xyes -o
"x$with_ftd2xx" = xcheck], [
AS_IF([test "x$with_ftd2xx" != xno], [
HAVELIBFTD2XX=yes
case $host in
- *cygwin*|*mingw*)
+ *cygwin*|*xxxmingw*)
CFLAGS="$CFLAGS -I$with_ftd2xx"
AS_IF([test -d "$with_ftd2xx/i386"], [
FTD2XXLIB="$with_ftd2xx/i386/ftd2xx.lib"
@@ -328,7 +328,7 @@ AC_ARG_WITH([inpout32],
[], [with_inpout32=auto])

case $host in
- *cygwin*|*mingw*) ;;
+ *cygwin*|*xxxmingw*) ;;
*) with_inpout32=no ;;
esac
Post by Geert Stappers
Post by Åke Rehnman
Post by Geert Stappers
I am currently trying to compile UrJTAG using Cygwin
./configure --host=i586-mingw32msvc --with-ftd2xx=~/ftd2 --with-inpout32
After having added the ftd2xx.h file to the usbconn directories in
/tap and /include as an error message demanded of me, I seem to be
gcc  -g -O2 -I~/ftd2 -Wall  -o jtag.exe jtag.o -Lcmd -lcmd -Ltap -ltap -Lpart
-lpart -Llib -ljtaglib -Lflash -lflash -Ltap -ltap -Lflash -lflash -Lbus -lbus
-lm ~/ftd2/ftd2xx.lib -lintl -Lsvf -lsvf -Lbsdl -lbsdl  -lusb
/usr/lib/gcc/x86_64-pc-cygwin/5.4.0/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lpart
/usr/lib/gcc/x86_64-pc-cygwin/5.4.0/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lsvf
collect2: Fehler: ld gab 1 als Ende-Status zurück
As is apparent, the linker seems to be incompatible with libpart.a and libsvf.a.
I have added every single "devel" or library package the Cygwin setup offers me.
Does someone know what I am doing wrong?
libsvf and libpart are libraries generated from urjtag source.
I don't known how cygwin handles such libraries.
My advice is to compare the cygwin buildlog with a Linux buildlog such as
at https://buildd.debian.org/status/fetch.php?pkg=urjtag&arch=arm64&ver=0.10%2Br2052-1&stamp=1481752319&raw=0
the problem probably arised much earlier where libpart and libsvf
and was compiled.
Run make again without cleaning and those errors should be clearly
visible through all garbage on the console.
And rerunning configure wouldn't harm.
Post by Åke Rehnman
As a side note, unless someone has fixed the configure script UrJtag
doesn't build under cygwin with ftdi-drivers.
These days we do accept patches.
Groeten
Geert Stappers
Geert Stappers
2017-03-06 17:33:43 UTC
Permalink
Post by Åke Rehnman
Post by Geert Stappers
Post by Åke Rehnman
Post by Geert Stappers
My advice is to compare the cygwin buildlog with a Linux buildlog such as
at https://buildd.debian.org/status/fetch.php?pkg=urjtag&arch=arm64&ver=0.10%2Br2052-1&stamp=1481752319&raw=0
the problem probably arised much earlier where libpart and libsvf
and was compiled.
Run make again without cleaning and those errors should be clearly
visible through all garbage on the console.
And rerunning configure wouldn't harm.
Post by Åke Rehnman
As a side note, unless someone has fixed the configure script UrJtag
doesn't build under cygwin with ftdi-drivers.
These days we do accept patches.
Let me rephrase that

There were days we didn't care about sent patches.
We did not even review them.
Those days should be over.
Post by Åke Rehnman
And these are the changes in the configure script. I don't recall
exactly why I just removed the check for mingw ONLY but what I do
remember is gcc will not link any libraries unless they start with lib.
So the workaround was to remove the check and rename the library to
libftd2xx.a if i recall...
I do read that as "I got a succesfull compile, but don't know exactly why,
probably renaming ftd2xx.a into libftd2xx.a"
Post by Åke Rehnman
urjtag/configure.ac | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/urjtag/configure.ac b/urjtag/configure.ac
index 3c0ce81..7758fb4 100644
--- a/urjtag/configure.ac
+++ b/urjtag/configure.ac
@@ -295,7 +295,7 @@ AS_IF([test "x$with_ftd2xx" = xyes -o
"x$with_ftd2xx" = xcheck], [
AS_IF([test "x$with_ftd2xx" != xno], [
HAVELIBFTD2XX=yes
case $host in
- *cygwin*|*mingw*)
+ *cygwin*|*xxxmingw*)
CFLAGS="$CFLAGS -I$with_ftd2xx"
AS_IF([test -d "$with_ftd2xx/i386"], [
FTD2XXLIB="$with_ftd2xx/i386/ftd2xx.lib"
@@ -328,7 +328,7 @@ AC_ARG_WITH([inpout32],
[], [with_inpout32=auto])
case $host in
- *cygwin*|*mingw*) ;;
+ *cygwin*|*xxxmingw*) ;;
*) with_inpout32=no ;;
esac
Patch seen and it would be applied.

The change might have made a different,
but that is most likely due new timestamp on configure.ac
_plus_ rerunning autoconf, configure and make.

Regex '*mingw*' matches also '*xxxmingx*'


Groeten
Geert Stappers
--
Leven en laten leven
Geert Stappers
2017-03-06 18:05:34 UTC
Permalink
Post by Geert Stappers
Post by Åke Rehnman
Post by Geert Stappers
Post by Åke Rehnman
As a side note, unless someone has fixed the configure script UrJtag
doesn't build under cygwin with ftdi-drivers.
These days we do accept patches.
Let me rephrase that
There were days we didn't care about sent patches.
We did not even review them.
Those days should be over.
Post by Åke Rehnman
diff --git a/urjtag/configure.ac b/urjtag/configure.ac
index 3c0ce81..7758fb4 100644
--- a/urjtag/configure.ac
+++ b/urjtag/configure.ac
@@ -328,7 +328,7 @@ AC_ARG_WITH([inpout32],
[], [with_inpout32=auto])
case $host in
- *cygwin*|*mingw*) ;;
+ *cygwin*|*xxxmingw*) ;;
*) with_inpout32=no ;;
esac
Patch seen and it would be applied.
Patch seen and it would not be applied.
Post by Geert Stappers
The change might have made a different,
but that is most likely due new timestamp on configure.ac
_plus_ rerunning autoconf, configure and make.
Regex '*mingw*' matches also '*xxxmingx*'
Groeten
Geert Stappers
--
Leven en laten leven
Loading...