From: Renaud Allard <renaud@allard.it>
To: crossgcc@sourceware.org
Subject: Using crosstool-ng on OpenBSD
Date: Mon, 23 Jan 2012 07:52:00 -0000 [thread overview]
Message-ID: <4F1D11AA.6010602@allard.it> (raw)
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
Hello,
While it may seem strange to some, I am trying to compile a toolchain on
an OpenBSD (5.0 amd64) machine.
I have installed all GNU alternatives to common programs:
cat /usr/local/lib/ct-ng-1.13.2/paths.mk
export install=/usr/bin/install
export bash=/usr/local/bin/bash
export grep=/usr/local/bin/ggrep
export make=/usr/local/bin/gmake
export sed=/usr/local/bin/gsed
export libtool=/usr/local/bin/libtool
export libtoolize=/usr/local/bin/libtoolize
export objcopy=/usr/bin/objcopy
export objdump=/usr/bin/objdump
export readelf=/usr/bin/readelf
export patch=/usr/bin/patch
However ct-ng build fails on me because it is not able to uncompress the
archives.
[DEBUG] ==> Executing: 'mkdir' '-p' 'linux-3.0.4'
[DEBUG] ==> Executing: 'tar' '--strip-components=1' '-C'
'linux-3.0.4' '-xv' '-f' '-'
[FILE ] tar: unknown option -- -
But the is no way (except linking tar to gtar in the system, which is
probably not a good idea) to use gtar instead of tar.
It would probably be interesting to add the option to use gtar in the
configure process.
Best Regards
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4510 bytes --]
next reply other threads:[~2012-01-23 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 7:52 Renaud Allard [this message]
2012-01-23 17:39 ` Yann E. MORIN
2012-01-23 17:50 ` Renaud Allard
2012-01-23 18:25 ` Yann E. MORIN
2012-01-23 18:30 ` Renaud Allard
2012-01-23 22:14 ` Yann E. MORIN
2012-02-01 21:15 ` Yann E. MORIN
2012-02-01 21:44 ` Renaud Allard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F1D11AA.6010602@allard.it \
--to=renaud@allard.it \
--cc=crossgcc@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).