Errors compiling in Ubuntu Hardy

Asked by Sciamano

Hi,
I've posted this question in another thread, but since I received no comments, I thought it might be more visible if I opened a new one.

I've installed the QT package from http://www.qtsoftware.com/, and now I have version 4.5.2 installed on my Kubuntu Hardy.
qmake seems to go ok, but when I send the make command, here is what comes up:

cd src/igotu/ && make -f Makefile
make[1]: Entering directory `/home/luca/Sources/igotu2gpx-0.2.3/src/igotu'
echo !_TAG_FILE_FORMAT 2 dummy > /home/luca/Sources/igotu2gpx-0.2.3/tags; echo !_TAG_FILE_SORTED 1 dummy >> /home/luca/Sources/igotu2gpx-0.2.3/tags; sed -i 's/ /\t/g' /home/luca/Sources/igotu2gpx-0.2.3/tags; cd /home/luca/Sources/igotu2gpx-0.2.3 && ctags -R --c++-kinds=+p-n --fields=+iaS --extra=+fq --exclude=.build -f - src | sed 's/igotu:://g;s/\tnamespace:igotu//g' | LC_ALL=C sort >> tags || cd .
/bin/sh: ctags: not found
make[1]: Leaving directory `/home/luca/Sources/igotu2gpx-0.2.3/src/igotu'
cd src/igotu2gpx/ && make -f Makefile
make[1]: Entering directory `/home/luca/Sources/igotu2gpx-0.2.3/src/igotu2gpx'
make[1]: Nothing to be done for `first'.
make[1]: Leaving directory `/home/luca/Sources/igotu2gpx-0.2.3/src/igotu2gpx'
cd src/igotugui/ && make -f Makefile
make[1]: Entering directory `/home/luca/Sources/igotu2gpx-0.2.3/src/igotugui'
make[1]: Nothing to be done for `first'.
make[1]: Leaving directory `/home/luca/Sources/igotu2gpx-0.2.3/src/igotugui'
cd data/ && make -f Makefile
make[1]: Entering directory `/home/luca/Sources/igotu2gpx-0.2.3/data'
make[1]: Nothing to be done for `first'.
make[1]: Leaving directory `/home/luca/Sources/igotu2gpx-0.2.3/data'
cd contrib/tango/ && make -f Makefile
make[1]: Entering directory `/home/luca/Sources/igotu2gpx-0.2.3/contrib/tango'
make[1]: Nothing to be done for `first'.
make[1]: Leaving directory `/home/luca/Sources/igotu2gpx-0.2.3/contrib/tango'

Any suggestion?
Thanks!

Question information

Language:
English Edit question
Status:
Answered
For:
igotu2gpx Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Michael Hofmann (mh21) said :
#1

> I've posted this question in another thread, but since I received no comments, I thought it might be more visible if I opened a new one.
Even developers have vacation sometimes :-). Your make seems to go ok,
you should have somew binaries in bin/debug.

Revision history for this message
Sciamano (sciamano72) said :
#2

> Even developers have vacation sometimes :-).

Of course! I was not complaining! I wasn't sure if the other thread being marked as "solved" would have prevented you to see the new question, that's all!

> Your make seems to go ok,
> you should have somew binaries in bin/debug.

I have!
If I launch igotu2gpx I get the: "Usage: igotu2gpx dump|info|diff [OPTIONS...]" so that part seems ok. But if I launch the GUI I get:

igotugui: symbol lookup error: igotugui: undefined symbol: _Z7qstrcmpRK10QByteArrayPKc

and nothing happens.

Thanks
Luca

Revision history for this message
Michael Hofmann (mh21) said :
#3

Hmm, this sounds weird. Can you rebuild the whole source tree by running "tools/all-rebuild.sh" (or rm -r bin; find . -name .build -exec rm -r {} +; make distclean; qmake; make)?

Revision history for this message
Sciamano (sciamano72) said :
#4

Hm... :-/
This is what I (don't) get:

luca@desktop:~/Sources/igotu2gpx-0.2.3$ sh tools/all-rebuild.sh
[: 13: ==: unexpected operator
qmake
clebs.pri:13: Unknown test function: defineTest
clebs.pri:37: Unknown test function: defineTest
clebs.pri:54: Unknown test function: defineTest
clebs.pri:61: Unknown test function: defineTest
clebs.pri:68: Unknown test function: defineTest
clebs.pri:76: Unknown test function: defineTest
clebs.pri:88: Unknown test function: defineTest
clebs.pri:97: Unknown test function: defineTest
clebs.pri:105: Unknown test function: defineTest
clebs.pri:119: Unknown test function: defineTest
clebs.pri:133: Unknown test function: defineTest
clebs.pri:161: Unknown test function: CONFIG
clebs.pri:238: Unknown test function: for
clebs.pri:264: Unknown test function: clebsVerbose
clebs.pri:272: Unknown test function: clebsVerbose
clebs.pri:285: Unknown test function: clebsVerbose
clebs.pri:290: Unknown test function: clebsVerbose
igotu.pro:10: Unknown test function: clebsDirs
igotu.pro:11: Unknown test function: clebsDirs
igotu.pro:12: Unknown test function: clebsDirs
igotu.pro:14: Unknown test function: clebsDirs
igotu.pro:15: Unknown test function: clebsDirs
make: Nothing to be done for `first'.

Revision history for this message
Michael Hofmann (mh21) said :
#5

You have the devel package for qt3 installed :-). You need to use qmake-qt4 instead of qmake. Can you change the line
  qmake $QMAKEARGS
to
  qmake-qt4 $QMAKEARGS
in tools/all-rebuild.sh and try again?

By the way, the previous error with the missing symbol sounds a bit as if you link with one version of Qt (the newer downloaded version I think), but on runtime the system libraries are used. Is there a special reason why the version supplied with Hardy (4.3.4) does not work for you?

Revision history for this message
Sciamano (sciamano72) said :
#6

I changed the line as requested, here is what I get now:

luca@desktop:~/Sources/igotu2gpx-0.2.3$ sh tools/all-rebuild.sh
[: 13: ==: unexpected operator
qmake
Project MESSAGE: ------------------------------------
Project MESSAGE: Required dependencies:
Project MESSAGE: ------------------------------------
Project MESSAGE: Looking for qtversion440 : no
Project ERROR: Please install the necessary (devel) packages for qtversion440!
make: *** No targets specified and no makefile found. Stop.

As far as the reason why the version supplied with Hardy (4.3.4) does not work for me goes, it is because I kept getting the same errors as above, without the last line (make:*** etc. etc.). That's why I tried installing the latest version from the qtsoftware.com site.

Revision history for this message
Sciamano (sciamano72) said :
#7

No solution? :-(

Revision history for this message
Michael Hofmann (mh21) said :
#8

A bit cheating, but you can install qt 4.4.0 by enabling hardy-backports (see http://packages.ubuntu.com/search?suite=default&section=all&arch=any&searchon=names&keywords=libqt4-dev and https://help.ubuntu.com/community/UbuntuBackports) and uninstalling the qt version you downloaded. I will try to release the next version also for Hardy, shouldn't be too hard actually.

Revision history for this message
Sciamano (sciamano72) said :
#9

Sorry for the delay, I was out of the country.
I will try backporting (although it usually not recommended by the people on the ubuntu forums), but a Hardy version of igotu2gpx would be very much appreciated! :-)

Revision history for this message
Michael Hofmann (mh21) said :
#10

The beta version of igotu2gpx 0.3 (0.2.91) is also released for Hardy, although I did not test it. It should work with the 4.3 Qt that comes with Hardy. Maybe you can give it a try.

Revision history for this message
Sciamano (sciamano72) said :
#11

I tried and installation works. That's great!
But when I launch, I get the following error:

Unable to download configuration from GPS tracker: Unable to send data to device: Protocol error

This was the qmake-qt4 output, in case you need it:

Project MESSAGE: ------------------------------------
Project MESSAGE: Required dependencies:
Project MESSAGE: ------------------------------------
Project MESSAGE: Looking for qtversion430 : yes
Project MESSAGE: Looking for boost-po : yes
Project MESSAGE: ------------------------------------
Project MESSAGE: Suggested dependencies:
Project MESSAGE: ------------------------------------
Project MESSAGE: Looking for libmarble : no
Project MESSAGE: Looking for libusb : yes
Project MESSAGE: Looking for libusb10 : no
Project MESSAGE: Looking for chrpath : yes
Project MESSAGE: ------------------------------------
Project MESSAGE: Additional features:
Project MESSAGE: ------------------------------------
Project MESSAGE: Building with marblevisualizer : no
Project MESSAGE: Building with libusbconnection : yes
Project MESSAGE: Building with libusb10connectio: no
Project MESSAGE: ------------------------------------

Thanks!

Revision history for this message
Michael Hofmann (mh21) said :
#12

Ok, this is at least something.

Be sure that the blue led of the tracker is blinking steadily when you try to connect to the GPS tracker. If it is still not working, could you post the output of "igotu2gpx -v info"?

Revision history for this message
Sciamano (sciamano72) said :
#13

That was it!
It correctly connected and identified my GT120.
Then I downloaded the gps tracks and disconnected the GT120. Now the tracker is dead... no leds, and nothing happens when I push the button...
Also, lsusb does not find the tracker anymore!
Any suggestions? Did I brick the tracker? :-(

Revision history for this message
Sciamano (sciamano72) said :
#14

Ok, I restarted the PC and when I connect the GT120 the blue led starts blinking.
But I can't do anything else (pushing the button does not turn the tracker on/off nor any led shows up...) :-(
Any suggestions?

Revision history for this message
Sciamano (sciamano72) said :
#15

luca@desktop:~$ igotu2gpx -v info
usb_set_debug: Setting debugging level to 255 (on)
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_busses: Found 007
usb_os_find_busses: Found 006
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
Downloading configuration...
usb_os_find_devices: Found 001 on 007
usb_os_find_devices: Found 016 on 006
usb_os_find_devices: Found 004 on 006
usb_os_find_devices: Found 002 on 006
usb_os_find_devices: Found 001 on 006
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 005 on 003
usb_os_find_devices: Found 002 on 003
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 003 on 001
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
USB error: could not get bound driver: No data available
Command: 930101030000000000000000000000
Result:
Command: 930a00000000000000000000000000
Result: 34760300021c00011100
Command: 9305040003019f0000000000000000
Result: c22015
Command: 930b03001d00000000000000000000
Result: 000000
Command: 930507100004030000000000000000
Result: 010c8b30ff0fff3c00f1ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff000000003c3c0004011501c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f01010101280000000000000000000000003c3c0005000000c80c012c32c8140101010202050a0a186a0c3504e200bb01171e000108080404020202020000200f0101010128000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000a0a2001980ffd27beb004bc862002892af00017700013a188405a70c880924b0b3000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003211a0a2000997000000c8000000c80227b0b3000000000000000000000000003217a0a2000fa7000003e8002dc6c00000070800010319b0b30000000000000032000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000102030405060708090a0b0c0d0e0f
Command: 930101000000000000000000000000
Result:
Serial number: 226868
Firmware version: 2.28
Model: GT-120
Number of points: 0
Schedule date: Wednesday, October 15, 2008
Schedule date offset: 0 day(s)
Schedule table: disabled
Log interval: 5 s
Interval change: above 10 km/h, use 2 s
LEDs: enabled
Button: enabled
Security version: 0
Password: disabled, []

Revision history for this message
Michael Hofmann (mh21) said :
#16

I don't think you can brick the tracker (the firmware is in ROM).

Normally, the tracker does not react to button presses when connected. When not connected, a long button press should turn it on/off. If that does not work (and also multiple connection/disconnection attempts fail), you could try whether you can reset it with @trip PC.

Revision history for this message
Sciamano (sciamano72) said :
#17

I know, the problem is the tracker is not reacting when disconnected.
I tried resetting with @trip PC, and the procedure worked. I also tried reconfiguring (checking that it was set to manual operation), but still I can't turn the tracker on.
Also, when connecting it to the PC, I used to see both leds (red and blue) on. Now only the blue one blinks.
Something has gone wrong here... :(

Revision history for this message
Michael Hofmann (mh21) said :
#18

Hmm, the red one only gives feedback about the rechargeable battery inside, so if you play around too much the battery is maybe just charged enough.

Revision history for this message
Sciamano (sciamano72) said :
#19

I have the opposite impression: that the battery went dead...
That would explain why the tracker seems to work when plugged to the USB socket.

Revision history for this message
Michael Hofmann (mh21) said :
#20

If this is really the case, maybe http://www.a-trip.com/forum/viewtopic.php?t=130 would make it possible that you could still use it (although it wouldn't be as pretty as before).

Revision history for this message
Sciamano (sciamano72) said :
#21

Thanks for your suggestion, but it would make the GT120 too big, bulky and heavy... and the reason I love the i-gotU is that it's so light and small!
I already have another tracker/logger (a QStarz BT-Q1000P) and I will go on using that one until I find a way to change the internal battery of the GT120. I don't think this is impossible!
And if it is... well, I guess I'll stop recommending this device to my friends because it's unacceptable that it dies after just a little more than one year of use...

Can you help with this problem?

Provide an answer of your own, or ask Sciamano for more information if necessary.

To post a message you must log in.