public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "thorsten.johannvorderbrueggen@t-online.de" <thorsten.johannvorderbrueggen@t-online.de>
To: crossgcc@sourceware.org
Subject: Base support for glibc-2.24
Date: Thu, 25 Aug 2016 15:37:00 -0000	[thread overview]
Message-ID: <20160825173730.747ed260011fe34c93ba17cc@t-online.de> (raw)

Hi@all,

i try to build a cross-toolchain for armhf (https://github.com/tjohann/a20_sdk) running on void-linux ... on the target devices also runs void-linux ... so i try to sync my cross-toolchain with it ... the basic parts are working without trouble (binutils-2.27, linux-4.6.7 and gcc4.9.4 -> see my pull request -> https://github.com/crosstool-ng/crosstool-ng/pulls) ... but glibc-2.24 wont work ... i'm to blind to see ... has anyone an idea? ... any hints would be great


[INFO ]  Installing kernel headers: done in 10.10s (at 05:17)
[INFO ]  =================================================================
[INFO ]  Installing C library headers & start files
[DEBUG]    Entering '/home/tjohann/src/toolchain_a20_sdk/crosstool-ng/.build/arm-none-linux-gnueabihf/build/build-libc-startfiles'
[DEBUG]    ==> Executing: 'rm' '-rf' 'sysroot-check' 
[DEBUG]    ==> Executing: 'mkdir' '-p' 'sysroot-check' 
[DEBUG]    ==> Executing: 'touch' 'sysroot-check/seen' 'sysroot-check/unique' 
[DEBUG]    Entering 'multilib_.'
[INFO ]    =================================================================
[INFO ]    Building for multilib 1/1: ''
[DEBUG]      ==> Executing: 'mkdir' '-p' '/opt/a20_sdk/toolchain/arm-none-linux-gnueabihf/sysroot' 
[DEBUG]      Sanitized 'startfiles_dir': '/opt/a20_sdk/toolchain/arm-none-linux-gnueabihf/sysroot/usr/lib/.' -> '/opt/a20_sdk/toolchain/arm-none-linux-gnueabihf/sysroot/usr/lib'
[EXTRA]      Configuring C library
[DEBUG]      Configuring with addons  : 'nptl,ports'
[DEBUG]      Extra config args passed : '--disable-debug --disable-sanity-checks --enable-obsolete-rpc --enable-kernel=4.6.7 --with-__thread --with-tls --enable-shared --enable-add-ons=nptl,ports --with-pkgversion=crosstool-NG crosstool-ng-1.22.0-201-g11cb2dd-dirty --with-fp'
[DEBUG]      Extra CFLAGS passed      : ' -O2 -U_FORTIFY_SOURCE   -mthumb-interwork -mlittle-endian   -mcpu=cortex-a7  -mfpu=vfp3 -mhard-float   '
[DEBUG]      Placing startfiles into  : '/opt/a20_sdk/toolchain/arm-none-linux-gnueabihf/sysroot/usr/lib'
[DEBUG]      Configuring with --host  : 'arm-none-linux-gnueabihf'
[DEBUG]      ==> Executing: 'BUILD_CC=x86_64-build_pc-linux-gnu-gcc' 'CC=arm-none-linux-gnueabihf-gcc  -O2 -U_FORTIFY_SOURCE   -mthumb-interwork -mlittle-endian   -mcpu=cortex-a7  -mfpu=vfp3 -mhard-float   ' 'AR=arm-none-linux-gnueabihf-ar' 'RANLIB=arm-none-linux-gnueabihf-ranlib' '/sbin/bash' '/home/tjohann/src/toolchain_a20_sdk/crosstool-ng/.build/src/glibc-2.24/configure' '--prefix=/usr' '--build=x86_64-build_pc-linux-gnu' '--host=arm-none-linux-gnueabihf' '--cache-file=/home/tjohann/src/toolchain_a20_sdk/crosstool-ng/.build/arm-none-linux-gnueabihf/build/build-libc-startfiles/multilib_./config.cache' '--without-cvs' '--disable-profile' '--without-gd' '--with-headers=/opt/a20_sdk/toolchain/arm-none-linux-gnueabihf/sysroot/usr/include' '--disable-debug' '--disable-sanity-checks' '--enable-obsolete-rpc' '--enable-kernel=4.6.7' '--with-__thread' '--with-tls' '--enable-shared' '--enable-add-ons=nptl,ports' '--with-pkgversion=crosstool-NG crosstool-ng-1.22.0-201-g11cb2dd-dirty' '--with-fp' 
[CFG  ]      configure: loading cache /home/tjohann/src/toolchain_a20_sdk/crosstool-ng/.build/arm-none-linux-gnueabihf/build/build-libc-startfiles/multilib_./config.cache
[CFG  ]      checking build system type... x86_64-build_pc-linux-gnu
[CFG  ]      checking host system type... arm-none-linux-gnueabihf
[CFG  ]      checking for arm-none-linux-gnueabihf-gcc... arm-none-linux-gnueabihf-gcc  -O2 -U_FORTIFY_SOURCE   -mthumb-interwork -mlittle-endian   -mcpu=cortex-a7  -mfpu=vfp3 -mhard-float   
[CFG  ]      checking for suffix of object files... o
[CFG  ]      checking whether we are using the GNU C compiler... yes
[CFG  ]      checking whether arm-none-linux-gnueabihf-gcc  -O2 -U_FORTIFY_SOURCE   -mthumb-interwork -mlittle-endian   -mcpu=cortex-a7  -mfpu=vfp3 -mhard-float    accepts -g... yes
[CFG  ]      checking for gcc... x86_64-build_pc-linux-gnu-gcc
[CFG  ]      checking for arm-none-linux-gnueabihf-readelf... arm-none-linux-gnueabihf-readelf
[CFG  ]      checking for arm-none-linux-gnueabihf-g++... no
[CFG  ]      checking for arm-none-linux-gnueabihf-c++... no
[CFG  ]      checking for arm-none-linux-gnueabihf-gpp... no
[CFG  ]      checking for arm-none-linux-gnueabihf-aCC... no
[CFG  ]      checking for arm-none-linux-gnueabihf-CC... no
[CFG  ]      checking for arm-none-linux-gnueabihf-cxx... no
[CFG  ]      checking for arm-none-linux-gnueabihf-cc++... no
[CFG  ]      checking for arm-none-linux-gnueabihf-cl.exe... no
[CFG  ]      checking for arm-none-linux-gnueabihf-FCC... no
[CFG  ]      checking for arm-none-linux-gnueabihf-KCC... no
[CFG  ]      checking for arm-none-linux-gnueabihf-RCC... no
[CFG  ]      checking for arm-none-linux-gnueabihf-xlC_r... no
[CFG  ]      checking for arm-none-linux-gnueabihf-xlC... no
[CFG  ]      checking for g++... g++
[CFG  ]      configure: WARNING: using cross tools not prefixed with host triplet
[CFG  ]      checking whether we are using the GNU C++ compiler... yes
[CFG  ]      checking whether g++ accepts -g... yes
[CFG  ]      checking whether g++ can link programs... yes
[CFG  ]      checking for sysdeps preconfigure fragments... aarch64 alpha arm configure: Found compiler is configured for armv7
[CFG  ]      hppa i386 m68k microblaze mips nacl nios2 powerpc s390 sh sparc tile x86_64 
[ERROR]      configure: error: add-on directory "ports" does not exist
[ERROR]  
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Building for multilib 1/1: '''
[ERROR]  >>        called in step 'Installing C library headers & start files'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@259]
[ERROR]  >>        called from: do_libc_backend_once[scripts/build/libc/glibc.sh@252]
[ERROR]  >>        called from: CT_IterateMultilibs[scripts/functions@1659]
[ERROR]  >>        called from: do_libc_backend[scripts/build/libc/glibc.sh@86]
[ERROR]  >>        called from: do_libc_start_files[scripts/build/libc/glibc.sh@48]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@624]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds, in:
[ERROR]  >>      '/usr/local/share/doc/crosstool-ng/crosstool-ng-1.22.0-201-g11cb2dd-dirty/B - Known issues.txt'

Thanks & cheers
  Thorsten



-- 
thorsten.johannvorderbrueggen@t-online.de <thorsten.johannvorderbrueggen@t-online.de>

-- 
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.

--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2016-08-25 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25 15:37 thorsten.johannvorderbrueggen [this message]
2016-08-25 19:07 ` Waldemar Brodkorb

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=20160825173730.747ed260011fe34c93ba17cc@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).