Bug 22477 - Unknown type name ' __uint128_t'
Summary: Unknown type name ' __uint128_t'
Status: RESOLVED INVALID
Alias: None
Product: glibc
Classification: Unclassified
Component: build (show other bugs)
Version: 2.26
: P2 critical
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
: 22482 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-11-22 10:33 UTC by lkpandey950
Modified: 2017-11-23 17:38 UTC (History)
3 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-


Attachments
It is screenshot of error while making glibc (140.17 KB, image/png)
2017-11-22 10:33 UTC, lkpandey950
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lkpandey950 2017-11-22 10:33:33 UTC
Created attachment 10628 [details]
It is screenshot of error while making glibc

I am on android 5.1 kernel 3.10.65+ aarch64

I am trying to compile glibc in Kali Nethunter but when I executed make then an error was came , error is given in screenshot
Comment 1 Joseph Myers 2017-11-22 13:42:08 UTC
All GCC versions supported for building glibc support the __uint128_t type on 64-bit systems, so you must be building with an unsupported compiler.  Please work with the libc-help mailing list on understanding the problems with your build environment and why configure didn't detect them.  You'll need to post information such as the complete output of the configure script (text, not image) and the options passed to it, and probably the contents of config.log.
Comment 2 Auxilus 2017-11-23 04:15:14 UTC
First of all thnx Joseph for your reply

Click on pastebin link to see all required things like configure script output , config.log output and make error.

I can't paste here my frst account got blocked due to spam...that's why I am giving pastebin link

Link :-----> https://pastebin.com/NkUDd1Gp

Please help...
Comment 3 joseph@codesourcery.com 2017-11-23 16:37:54 UTC
You're trying to build an aarch64 glibc with an arm compiler.  That can't 
possibly work.  Please use the libc-help mailing list, not Bugzilla, for 
any further questions about how to build glibc.
Comment 4 Joseph Myers 2017-11-23 16:39:27 UTC
*** Bug 22482 has been marked as a duplicate of this bug. ***
Comment 5 Carlos O'Donell 2017-11-23 17:25:02 UTC
For the record, the key piece of information from the pastebin is this:

Configured with: ../src/configure -v --with-pkgversion='Debian 7.2.0-12' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=arm-linux-gnueabihf- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libitm --disable-libquadmath --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-sjlj-exceptions --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=hard --with-mode=thumb --disable-werror --enable-checking=release --build=arm-linux-gnueabihf --host=arm-linux-gnueabihf --target=arm-linux-gnueabihf

Which shows the compiler used by the user is a "arm-linux-gnueabihf" 32-bit ARM compiler, and the user is trying to use this to compile a 64-bit AArch64 glibc.
Comment 6 Auxilus 2017-11-23 17:28:57 UTC
It means that Kali Nethunter can only compile glibc for arm not aarch64 or arm64
?
Comment 7 Carlos O'Donell 2017-11-23 17:38:11 UTC
(In reply to Auxilus from comment #6)
> It means that Kali Nethunter can only compile glibc for arm not aarch64 or
> arm64
> ?

Please ask these questions on libc-help@sourceware.org.