Arch Linux

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!
Tasklist

FS#7635 - Compiling (linking actually) not possible anymore on arch64

Attached to Project: Arch Linux
Opened by Michel (michel) - Thursday, 19 July 2007, 18:09 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 25 August 2007, 15:01 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture x86_64
Severity High
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Trying to compile kmobile-toolsbeta3, I get:

/usr/lib/libbluetooth.so: file not recognized: File format not recognized
collect2: ld returned 1 exit status

This seems to be a bug in binutils or libc6:

http://www.mail-archive.com/debian-glibc%40lists.debian.org/msg34706.html



Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
* compile anything when using a fully upgraded arch64-system?
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 25 August 2007, 15:01 GMT
Reason for closing:  Not a bug
Additional comments about closing:  new toolchain is in current and works fine for all.
Comment by Michel (michel) - Thursday, 19 July 2007, 18:09 GMT
Seems to be a bug in libc6: http://www.mail-archive.com/debian-glibc%40lists.debian.org/msg34709.html

Thank you and greetings,

Michel
Comment by Andreas Radke (AndyRTR) - Thursday, 19 July 2007, 20:12 GMT
debian uses a glibc2.5 we use 2.6 tree. also we need to know if you are using current/extra or testing packages and the pkgversions (pacman -Q binutils gcc glibc).

i cannot reproduce it here. i'm compiling tons of packages in testing and stable chroots. i don't have such issues.
Comment by Jan de Groot (JGC) - Thursday, 19 July 2007, 20:23 GMT
This is caused by mixing things up. Either you're mixing up packages from current and testing (using glibc from testing, binutils from current -> won't work), or the maintainer of the packages compiled things with the toolchain in testing.

At this moment, at least on amd64, anything from testing that has to do with the toolchain (gcc, glibc, binutils) will break your compilation with binutils from current.

Loading...