From: Thorsten Johannvorderbrueggen <myha...@googlemail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: Problem with ./xbps-src -a armv7hf -N pkg base-system
Date: Sun, 2 Aug 2015 02:13:30 -0700 (PDT) [thread overview]
Message-ID: <7c322c1f-0fb3-47bf-a499-ed64d7bd1771@googlegroups.com> (raw)
In-Reply-To: <55313082-4079-4f25-8869-77825406f1c5@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 2611 bytes --]
Hi@all,
i invest some more time to search for a reason ... the base-system build
breaks by building ncurses ... so i thought that it would be useful to
check if it crossbuilds outside a base-system build ...
-> i first tried to build it in the same void-package repo where i first
did a base-system build ... i faced the same problem (what i expected :-)
...)
-> next i cloned the void-package repo again and binary-bootstrapped it ...
and then i crossbuild ncurses with ./xbps-src -a armv7hf-musl pkg ncurses
... and to my surprise it builds without any breakage ....
Note: This is my fith day with void-linux ... so pls give me some hints if
i did something in a wrong way :-)
Cheers
Thorsten
Am Freitag, 31. Juli 2015 20:47:05 UTC+2 schrieb Thorsten
Johannvorderbrueggen:
>
> Hi@all,
>
> i have another problem :-) ... so armv7hf-musl wont work at the moment so
> i tried the "normal" glibc build ...
>
> ./xbps-src -a armv7hf -N pkg base-system
>
> SNIP
>
> => ncurses-5.9_14: building (dependency of base-system) ...
> [host] ncurses-5.9_14: found (/host/binpkgs)
> => ncurses: building (dependency of base-system) ...
> => ncurses-5.9_14: installing host dependency 'ncurses-5.9_14' ...
> => ncurses-5.9_14: running do-fetch hook: 00-distfiles ...
> => ncurses-5.9_14: verifying checksum for distfile 'ncurses-5.9.tar.gz'...
> OK.
> => ncurses-5.9_14: running do-extract hook: 00-distfiles ...
> => ncurses-5.9_14: extracting distfile(s), please wait...
> => ncurses-5.9_14: running post-extract hook: 00-patches ...
> => ncurses-5.9_14: patch applied: no-xopen.patch.
> => ncurses-5.9_14: running pre-configure hook: 00-gnu-configure-asneeded
> ...
> => ncurses-5.9_14: running pre-configure hook: 01-override-config ...
> => ncurses-5.9_14: running pre-configure hook: 02-script-wrapper ...
> => ncurses-5.9_14: running do_configure ...
> checking for egrep... grep -E
> Configuring NCURSES 5.9 ABI 5 (Fri Jul 31 20:33:58 CEST 2015)
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... armv7l-unknown-linux-gnueabihf
> checking target system type... armv7l-unknown-linux-gnueabihf
> Configuring for linux-gnueabihf
> checking for prefix... /usr
> checking for armv7l-linux-gnueabihf-gcc... armv7l-linux-gnueabihf-gcc
> checking for C compiler default output... configure: error: C compiler
> cannot create executables
> => ERROR: ncurses-5.9_14: failed to run do_configure() at line 29.
>
> Here it end with that error ... if i take a look at the template for
> ncurses it looks good ... so i think it should work ...
>
> Cheers
> Thorsten
>
[-- Attachment #1.2: Type: text/html, Size: 2908 bytes --]
next prev parent reply other threads:[~2015-08-02 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 18:47 Thorsten Johannvorderbrueggen
2015-08-02 9:13 ` Thorsten Johannvorderbrueggen [this message]
2015-08-03 7:15 ` Juan RP
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=7c322c1f-0fb3-47bf-a499-ed64d7bd1771@googlegroups.com \
--to="myha..."@googlemail.com \
--cc="void..."@googlegroups.com \
/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 NNTP newsgroup(s).