public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rh100605 at aol dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/26209] New: Compiling Glibc-2.11.1 on Raspberrypi4 fails as config.guess returns armv7l unknown
Date: Mon, 06 Jul 2020 15:52:40 +0000	[thread overview]
Message-ID: <bug-26209-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=26209

            Bug ID: 26209
           Summary: Compiling Glibc-2.11.1 on Raspberrypi4 fails as
                    config.guess returns armv7l unknown
           Product: glibc
           Version: 2.11
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: rh100605 at aol dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

I am trying to compile an old gligc-2.11.1 on a Raspberry pi 4. As the
configure script fails with armv7l unsupported, I cannot start make.
I do not have any problem with compiling OpenSSL or other packages on the RPi4.

I thought that the script config.guess was faulty, the owner
config-patches@gnu.org  (Ben Ellison) says that he does not know what is wrong.
The compiler when configured for native reports alot more information see below
The problem falls between the compiler and the config.guess script. 
Below is the detail....

Ben Elliston (bje@air.net.au)
To:you Details
I don't know the answer to this, sorry. You will need to ask the glibc
folks.
Cheers,
Ben
 (rh100605@aol.com)
To:bje@air.net.au Details
Ben
The actual invocation of configure with error messages is below. My thoughts
are that the term "armv7l" will need translation to be understood by the
compiler. I think it means armv7  32bit without hard floating point, but as
most of the code in an Rpi4 is armhf ( hard float 32bit) as in the eabi, this
is misleading. The cpu is in fact 64bit capable but Rpi OS's do not use this.


pi@raspberrypi:~/Downloads/glibc-build $ sudo ../glibc-2.11.1/configure
--prefix=/opt/glibc/2.11.1 --enable-kernel=2.6.3$
checking build system type... armv7l-unknown-linux-gnueabihf
checking host system type... armv7l-unknown-linux-gnueabihf
checking for gcc... gcc
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
configure: running configure fragment for add-on libidn
configure: running configure fragment for add-on nptl
checking sysdep dirs... configure: error: The armv7l is not supported.



The compiler asked for -march and -mcpu as native, gets more detail from
somewhere and gives

pi@raspberrypi:~/Downloads/glibc-build $ gcc -mcpu=native -march=native -Q
--help=target
The following options are target specific:
  -mabi=                                aapcs-linux
  -mabort-on-noreturn                   [disabled]
  -mandroid                             [disabled]
  -mapcs                                [disabled]
  -mapcs-frame                          [disabled]
  -mapcs-reentrant                      [disabled]
  -mapcs-stack-check                    [disabled]
  -march=                               armv8-a+crc+simd
  -marm                                 [enabled]
  -masm-syntax-unified                  [disabled]
  -mbe32                                [enabled]
  -mbe8                                 [disabled]
  -mbig-endian                          [disabled]
  -mbionic                              [disabled]
  -mbranch-cost=                        -1
  -mcallee-super-interworking           [disabled]
  -mcaller-super-interworking           [disabled]
  -mcmse                                [disabled]
  -mcpu=                                cortex-a72
  -mfix-cortex-m3-ldrd                  [disabled]
  -mflip-thumb                          [disabled]
  -mfloat-abi=                          hard
  -mfp16-format=                        none
  -mfpu=                                vfp
  -mglibc                               [enabled]
  -mhard-float                          
  -mlittle-endian                       [enabled]
  -mlong-calls                          [disabled]
  -mmusl                                [disabled]
  -mneon-for-64bits                     [disabled]
  -mpic-data-is-text-relative           [enabled]
  -mpic-register=                       
  -mpoke-function-name                  [disabled]
  -mprint-tune-info                     [disabled]
  -mpure-code                           [disabled]
  -mrestrict-it                         [disabled]
  -msched-prolog                        [enabled]
  -msingle-pic-base                     [disabled]
  -mslow-flash-data                     [disabled]
  -msoft-float                          
  -mstructure-size-boundary=            8
  -mthumb                               [disabled]
  -mthumb-interwork                     [disabled]
  -mtls-dialect=                        gnu
  -mtp=                                 cp15
  -mtpcs-frame                          [disabled]
  -mtpcs-leaf-frame                     [disabled]
  -mtune=                               
  -muclibc                              [disabled]
  -munaligned-access                    [enabled]
  -mvectorize-with-neon-double          [disabled]
  -mvectorize-with-neon-quad            [enabled]
  -mword-relocations                    [disabled]

  Known ARM ABIs (for use with the -mabi= option):
    aapcs aapcs-linux apcs-gnu atpcs iwmmxt

  Known __fp16 formats (for use with the -mfp16-format= option):
    alternative ieee none

  Known ARM FPUs (for use with the -mfpu= option):
    auto crypto-neon-fp-armv8 fp-armv8 fpv4-sp-d16 fpv5-d16 fpv5-sp-d16 neon
    neon-fp-armv8 neon-fp16 neon-vfpv3 neon-vfpv4 vfp vfp3 vfpv2 vfpv3
vfpv3-d16
    vfpv3-d16-fp16 vfpv3-fp16 vfpv3xd vfpv3xd-fp16 vfpv4 vfpv4-d16

  Valid arguments to -mtp=:
    auto cp15 soft

  Known floating-point ABIs (for use with the -mfloat-abi= option):
    hard soft softfp

  TLS dialect to use:
    gnu gnu2

Cheers
Rob

-----Original Message-----
From: Ben Elliston <bje@air.net.au>
To: rh100605@aol.com
Sent: Fri, Jul 3, 2020 1:30 pm
Subject: Re: config.guess fails on Raspberry pi4 giving arm7l which is
unrecognised by GNU compilers /scripts for glibc-version build

config.guess (which I maintaing) is working:

  configure:2018: checking build system type
  configure:2036: result: armv7l-unknown-linux-gnueabihf
  configure:2058: checking host system type
  configure:2073: result: armv7l-unknown-linux-gnueabihf

The configure script for glibc is obviously failing somewhere
[reply] [−]Comment 1Jonathan Wakely 2020-07-06 12:21:49 UTC
(In reply to Rob Hookham from comment #0)
> I don't know the answer to this, sorry. You will need to ask the glibc
> folks.


This bugzilla is for GCC not glibc.

See https://www.gnu.org/software/libc/bugs.html for glibc bugs.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-07-06 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 15:52 rh100605 at aol dot com [this message]
2020-07-06 17:13 ` [Bug libc/26209] " schwab@linux-m68k.org
2020-07-06 17:49 ` rh100605 at aol dot com
2020-07-06 18:04 ` adhemerval.zanella at linaro dot org
2020-07-06 21:10 ` rh100605 at aol dot com

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=bug-26209-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).