Opened 4 years ago
Closed 4 years ago
#20 closed defect (fixed)
Qutecom doesn't build on x68_64
| Reported by: | henryju | Owned by: | vadim |
|---|---|---|---|
| Priority: | blocker | Milestone: | QuteCom 2.2-RC4 |
| Component: | 3rd party libs | Version: | 2.2-RC1 |
| Keywords: | Cc: |
Description
Hi,
Can't compile on my system.
[ 48%] Building CXX object libs/3rdparty/googlebreakpad/CMakeFiles/googlebreakpad.dir/src/common/linux/dump_symbols.o /home/julien/Linux/qutecom/qutecom-2.2/libs/3rdparty/googlebreakpad/src/common/linux/dump_symbols.cc: In function ‘void<unnamed>::FixAddress(void*)’: /home/julien/Linux/qutecom/qutecom-2.2/libs/3rdparty/googlebreakpad/src/common/linux/dump_symbols.cc:141: erreur: cast from ‘void*’ to ‘Elf64_Word’ loses precision
The problem was discussed on the mailing list but I think a ticket is a better way to track progress.
http://lists.qutecom.org/pipermail/qutecom-dev/2008-October/000442.html
Tried what was suggested by Vadim and Chi-Thanh but without success.
Note that sources evolved since they gave the tip so line numbers don't match anymore.
Change History (4)
comment:1 in reply to: ↑ description Changed 4 years ago by bero
comment:2 Changed 4 years ago by cavedon
Here is the patch I used for Debian package for excluding googlebreakpad on non x86 archs
comment:3 Changed 4 years ago by cervajs
- Milestone changed from QuteCom 2.2-RC2 to QuteCom 2.2-RC4
comment:4 Changed 4 years ago by vadim
- Resolution set to fixed
- Status changed from new to closed
This patch is applied
Note: See
TracTickets for help on using
tickets.

There's a fix for that in the upstream googlebreakpad bug tracker, at
http://code.google.com/p/google-breakpad/issues/detail?id=239#c8
However, I think the best thing to do in qutecom would be adding a compile time switch to disable the use of breakpad, given qutecom itself is far more portable than breakpad.