From: "thorsten.johannvorderbrueggen@t-online.de" <thorsten.johannvorderbrueggen@t-online.de>
To: crossgcc <crossgcc@sourceware.org>
Subject: Re: cross-ng building trys to copy files to '/' ?
Date: Thu, 09 Jan 2014 18:24:00 -0000 [thread overview]
Message-ID: <20140109192428.94015be2c64aa5cbb06af3a9@t-online.de> (raw)
In-Reply-To: <CAAsE_uepmdsn1YOux0U9W9D1PKJ6KpVmV4=mSh=+jjmBLY4BJA@mail.gmail.com>
On Thu, 9 Jan 2014 13:48:02 +0800
Woody Wu <narkewoody@gmail.com> wrote:
> On 9 January 2014 03:01, thorsten.johannvorderbrueggen@t-online.de
> <thorsten.johannvorderbrueggen@t-online.de> wrote:
> > On Wed, 8 Jan 2014 22:32:38 +0800
> > narkewoody@gmail.com wrote:
> >
> >> Hi,
> >>
> >> I am building ARM toolchain using cross-ng on my Slackware Linux PC.
> >> I've tried 1.17 and 1.18 - the two most recent release, but met the same
> >> error in building (ct-ng build). It seems, cross-ng was trying to
> >> install some header files into my /usr/include and then failed because
> >> it was not running as root.
> >>
> >> Can anyone help me? Below is the output:
> >>
> >> ...
> >>
> >> [ALL ] mv -f /home/woody/work/cross-ng.build/1.17.0/.build/arm-unknown-linux-gnueabi/build/build-libc-startfiles/tls.makeT /home/woody/work/cross-ng.build/1.17.0/.build/arm-unknown-linux-gnueabi/build/build-libc-startfiles/tls.make
> >> [ALL ] make[2]: Leaving directory `/home/woody/work/cross-ng.build/1.17.0/.build/src/glibc-2.9'
> >> [ALL ] make[2]: Entering directory `/home/woody/work/cross-ng.build/1.17.0/.build/src/glibc-2.9'
> >> [ALL ] /home/woody/work/cross-ng.build/1.17.0/.build/tools/bin/install -c -m 644 include/limits.h /usr/include/limits.h
> >> [ALL ] /usr/bin/ginstall: cannot remove '/usr/include/limits.h': Permission denied
> >> [ERROR] make[2]: *** [/usr/include/limits.h] Error 1
> >> [ALL ] make[2]: Leaving directory `/home/woody/work/cross-ng.build/1.17.0/.build/src/glibc-2.9'
> >> [ERROR] make[1]: *** [install-headers] Error 2
> >> [ALL ] make[1]: Leaving directory `/home/woody/work/cross-ng.build/1.17.0/.build/arm-unknown-linux-gnueabi/build/build-libc-startfiles'
> >> [ERROR]
> >> [ERROR] >>
> >> [ERROR] >> Build failed in step 'Installing C library headers & start files'
> >> [ERROR] >> called in step '(top-level)'
> >> [ERROR] >>
> >> [ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@258]
> >> [ERROR] >> called from: do_libc_backend_once[scripts/build/libc/glibc-eglibc.sh-common@384]
> >>
> >> ...
> >>
> >> --
> >> For unsubscribe information see http://sourceware.org/lists.html#faq
> >>
> >
> >
> > Hi woody,
> >
> > i used 1.18 and actual 1.19 for building my arm toolchain ... on slackware ... of course :-) ... i had no problems ... can you post your config ...
> >
> > Cheers
> > Thorsten
> >
>
> Nice to meet you Thorsten. My Slackware is 14.0. Now I paste the
> '.config' file from my work directory, please have a look at it. If
> you still need other information, please let me know.
>
> #
> # C-library
> #
> CT_LIBC="glibc"
> CT_LIBC_VERSION="2.9"
> # CT_LIBC_eglibc is not set
> # CT_LIBC_uClibc is not set
> CT_LIBC_glibc=y
> CT_LIBC_none_AVAILABLE=y
> CT_LIBC_mingw_AVAILABLE=y
> CT_LIBC_eglibc_AVAILABLE=y
> CT_LIBC_newlib_AVAILABLE=y
> CT_LIBC_uClibc_AVAILABLE=y
> CT_LIBC_glibc_AVAILABLE=y
> # CT_LIBC_GLIBC_V_2_14_1 is not set
> # CT_LIBC_GLIBC_V_2_14 is not set
> # CT_LIBC_GLIBC_V_2_13 is not set
> # CT_LIBC_GLIBC_V_2_12_2 is not set
> # CT_LIBC_GLIBC_V_2_12_1 is not set
> # CT_LIBC_GLIBC_V_2_11_1 is not set
> # CT_LIBC_GLIBC_V_2_11 is not set
> # CT_LIBC_GLIBC_V_2_10_1 is not set
> CT_LIBC_GLIBC_V_2_9=y
> # CT_LIBC_GLIBC_V_2_8 is not set
> CT_LIBC_SUPPORT_THREADS_ANY=y
> CT_LIBC_SUPPORT_NPTL=y
> CT_THREADS="nptl"
>
> #
> # Common C library options
> #
> CT_THREADS_NPTL=y
> CT_LIBC_XLDD=y
> CT_LIBC_GLIBC_MAY_FORCE_PORTS=y
> CT_LIBC_glibc_familly=y
> CT_LIBC_GLIBC_EXTRA_CONFIG_ARRAY=""
> CT_LIBC_GLIBC_CONFIGPARMS=""
> CT_LIBC_GLIBC_EXTRA_CFLAGS=""
> CT_LIBC_EXTRA_CC_ARGS=""
> # CT_LIBC_DISABLE_VERSIONING is not set
> CT_LIBC_OLDEST_ABI=""
> # CT_LIBC_GLIBC_FORCE_UNWIND is not set
> CT_LIBC_GLIBC_USE_PORTS=y
> CT_LIBC_ADDONS_LIST=""
> # CT_LIBC_LOCALES is not set
> # CT_LIBC_GLIBC_KERNEL_VERSION_NONE is not set
> CT_LIBC_GLIBC_KERNEL_VERSION_AS_HEADERS=y
> # CT_LIBC_GLIBC_KERNEL_VERSION_CHOSEN is not set
> CT_LIBC_GLIBC_MIN_KERNEL="3.6.3"
>
> #
> # glibc other options
> #
>
> #
> # WARNING !!!
> #
>
> #
> # For glibc >= 2.8, it can happen that the tarballs
> #
>
> #
> # for the addons are not available for download.
> #
>
> #
> # If that happens, bad luck... Try a previous version
> #
>
> #
> # or try again later... :-(
> #
>
> #
> # Debug facilities
> #
> CT_DEBUG_ltrace=y
> CT_LTRACE_V_0_5_3=y
> # CT_LTRACE_V_0_5_2 is not set
> CT_LTRACE_VERSION="0.5.3"
> CT_LTRACE_0_5_3_or_later=y
> CT_DEBUG_gdb=y
> CT_GDB_CROSS=y
> # CT_GDB_CROSS_STATIC is not set
> CT_GDB_CROSS_PYTHON=y
> CT_GDB_CROSS_EXTRA_CONFIG_ARRAY=""
> CT_GDB_NATIVE=y
> # CT_GDB_NATIVE_STATIC is not set
> CT_GDB_GDBSERVER=y
> CT_GDB_GDBSERVER_STATIC=y
>
> #
> # gdb version
> #
> CT_GDB_V_6_8a=y
> CT_GDB_VERSION="6.8a"
> CT_DEBUG_duma=y
> CT_DUMA_A=y
> CT_DUMA_SO=y
> CT_DUMA_V_2_5_15=y
> CT_DUMA_VERSION="2_5_15"
> CT_DEBUG_dmalloc=y
> CT_DMALLOC_V_5_5_2=y
> CT_DMALLOC_VERSION="5.5.2"
> CT_DEBUG_strace=y
> CT_STRACE_V_4_5_19=y
> # CT_STRACE_V_4_5_18 is not set
> CT_STRACE_VERSION="4.5.19"
>
> #
> # Companion libraries
> #
> CT_COMPLIBS_NEEDED=y
> CT_GMP_NEEDED=y
> CT_MPFR_NEEDED=y
> CT_COMPLIBS=y
> CT_GMP=y
> CT_MPFR=y
> CT_LIBELF_TARGET=y
> # CT_GMP_V_5_0_2 is not set
> # CT_GMP_V_5_0_1 is not set
> CT_GMP_V_4_3_2=y
> # CT_GMP_V_4_3_1 is not set
> # CT_GMP_V_4_3_0 is not set
> CT_GMP_VERSION="4.3.2"
> # CT_MPFR_V_3_1_0 is not set
> # CT_MPFR_V_3_0_1 is not set
> # CT_MPFR_V_3_0_0 is not set
> CT_MPFR_V_2_4_2=y
> # CT_MPFR_V_2_4_1 is not set
> # CT_MPFR_V_2_4_0 is not set
> CT_MPFR_VERSION="2.4.2"
>
> #
> # libelf version needed to build for target
> #
> CT_LIBELF_V_0_8_13=y
> # CT_LIBELF_V_0_8_12 is not set
> CT_LIBELF_VERSION="0.8.13"
>
> #
> # Companion libraries common options
> #
> # CT_COMPLIBS_CHECK is not set
>
> Please help! Thanks.
>
>
> --
> Life is the only flaw in an otherwise perfect nonexistence
> -- Schopenhauer
>
> narke
> public key at http://subkeys.pgp.net:11371 (narkewoody@gmail.com)
Hi woody,
i will try to build it in a qemu inst ... you want to build a toolchain for a bare metal system? ... correct?
Cheers
Thorsten
--
thorsten.johannvorderbrueggen@t-online.de <thorsten.johannvorderbrueggen@t-online.de>
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2014-01-09 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 14:33 narkewoody
2014-01-08 19:01 ` thorsten.johannvorderbrueggen
[not found] ` <CAAsE_uepmdsn1YOux0U9W9D1PKJ6KpVmV4=mSh=+jjmBLY4BJA@mail.gmail.com>
2014-01-09 18:24 ` thorsten.johannvorderbrueggen [this message]
2014-01-10 2:42 ` Woody Wu
2014-01-10 8:32 ` Bob Dunlop
2014-01-10 12:41 ` Woody Wu
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=20140109192428.94015be2c64aa5cbb06af3a9@t-online.de \
--to=thorsten.johannvorderbrueggen@t-online.de \
--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).