Can't compile Slackware ARM x-toolchain on 14.0 32 bit.
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've never built this, but it looks like Slackware's man page for ar is broken since the bfdname section is missing. Here is an online one for V2.22, down the bottom is the specification for the --target parameter.
Having a quick look at the target specification link, I guess that your bfdtarget is not correct (as indeed ar is telling you); possibly a more likely candidate could be i486-linux-gnu? What does the build log say for the x86_64 build?
The error occurs at lines 1429 & 1476. Libbfd is described at Wikipedia and there are plenty of hits from google.
It's got to be the "slackware" component of the name, right? It's set at line 130 (i.e. log line 130) for build and host systems and then the target system is set. Perhaps you need to edit the Makefile and insert a sed clause that removes the "-slackware" component so that the BFD clause changes from i486-slackware-linux-gnu to i486-linux-gnu, assuming it is set with a make or shell command.
Could be the blind leading the blind here, but that would be my first attempt to fix it. Also, I happened to note while going through some man pages the following
Code:
archive_entry_uname [] (3) - functions for manipulating archive entry descriptions
archive_entry_uname [] (3p) - functions for manipulating archive entry descriptions
and
libarchive [] (3) - functions for reading and writing streaming archives
libarchive [] (3p) - functions for reading and writing streaming archives
libarchive [] (5) - formats - archive formats supported by the libarchive library
libarchive_internals [] (3) - description of libarchive internal interfaces
libarchive_internals [] (3p) - description of libarchive internal interfaces
which may be relevant since your errors are coming from ar.
Good luck.
Last edited by padeen; 02-06-2013 at 06:24 PM.
Reason: stupid thumbs down icon appeared from nowhere -- removed.
'i486-slackware-linux-gnu' I'd say that more likely it's the '-gnu' part that causes the problem. binutils and others expect 'properly formed' target name which include -gnu or other libc names. Slackware, of course does not have that, so tools which have their own routines for determining the arch complain and fail over it. A small patch will fix the sources, or linking all references to i486-slackware-linux to i486-slackware-linux-gnu.
The binutils-2.22.52.0.2 in arm 14.0's x-toolchain seems to have a problem building on slackware x86. I updated to binutils-2.23.52.0.1 in x-toolchain current, and the problem goes away. I'll try out my tool-chain and hope it works. I want a locked down tool-chain on the latest stable version because I don't think I will be changing slackware arm versions on my raspberry pi ever. So I want to make it easy to know what was used than to remember what current meant.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.