Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#8003 - Some packages, compiled myself, don't work properly
Attached to Project:
Arch Linux
Opened by Otakar (otula) - Wednesday, 12 September 2007, 16:52 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 05 October 2007, 21:41 GMT
Opened by Otakar (otula) - Wednesday, 12 September 2007, 16:52 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 05 October 2007, 21:41 GMT
|
DetailsDescription:
Some packages, compiled myself, don't work properly Additional info: I have problems with some packages, I compile myself. For example - linuxdc++ ends with SIGILL error with openssl compiled by me, with wxgtk compiled by me Hugin ends as folowing: hugin: symbol lookup error: /usr/lib/libwx_gtk2u_adv-2.8.so.0: undefined symbol: _ZNK8wxColour4IsOkEv. But packages from the repository work properly. I tested it on 3 different PCs with Arch (i686) always with the same faults. First I thought that problem could be my C(XX)FLAGS settings, but I've got the same result, although I use default settings, those are set after fresh installation (-march=i686 -mtune=generic -O2 -pipe) I tried run linuxdcpp through GDB, but I got the same amount of informations as when I run the program directly from console. With my own openssl it looks as follows: ... (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Program received signal SIGILL, Illegal instruction. ---Type <return> to continue, or q <return> to quit--- [Switching to Thread -1222154544 (LWP 9673)] 0xb7f5fbc1 in ssl3_ctx_ctrl () from /usr/lib/libssl.so.0.9.8 With openssl from repository it looks: ... (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Loading: Hash database [New Thread -1223345264 (LWP 9680)] Loading: Shared Files [New Thread -1231737968 (LWP 9681)] [Thread -1231737968 (LWP 9681) exited] Loading: Download Queue [New Thread -1231737968 (LWP 9682)] ... I'm using ABS's PKGBUILDs for compiling. |
This task depends upon
Comment by Jan de Groot (JGC) -
Wednesday, 12 September 2007, 20:38 GMT
What compiler do you use to compile these packages? It looks like you're using some different linker or compiler, as we can't reproduce these things. The SIGILL in OpenSSL looks like an over-optimization done by your compiler, the undefined symbols in wxgtk/hugin would suggest an incompatible linker used.
Comment by Otakar (otula) -
Thursday, 13 September 2007, 05:13 GMT
I'm using ld from package binutils 2.18-2 and gcc 4.2.1 from package gcc 4.2.1-3.1, both from current/base repository.
Comment by Jan de Groot (JGC) -
Wednesday, 19 September 2007, 21:25 GMT
In case of openssl: OpenSSL contains bugs that cause it to generate invalid code when compiled with GCC 4.2. The package in the repositories was built using gcc 4.1. A patch has been added to fix this issue.
Comment by Otakar (otula) -
Thursday, 20 September 2007, 06:56 GMT
Thanks, it's working now fine. I suppose, the cause of problems with other programs is incompatibility with gcc-4.2 too.
Comment by Francois Charette (Firmicus) -
Friday, 05 October 2007, 17:54 GMT
Perhaps this task should be closed now?