| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
When bootstrapping a cross-toolchain don't pull in libidn2 into
the host as it's not stable yet everywhere (requires KEYWORDS
fiddling) and is not needed on host (it's cross-glibc).
Reported-by: Mahmoud Jaoune
Bug: https://bugs.gentoo.org/681742
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
Patchset 11 is the same as patchset 10 rebased on top of
current master. One minor conflict is fixed in patch removal.
Reported-by: jospezial
Closes: https://bugs.gentoo.org/679980
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The change adds new USE=ssp to optionally disable protection of
glibc's internals. Before the change protection was
unconditionally enabled.
It's useful to disable ssp to validate if stack protection
causes any damage (glibc bugs like https://sourceware.org/PR24202
or gcc bugs like https://gcc.gnu.org/PR81996).
And also useful to get more predictable binaries like in
https://bugs.gentoo.org/679788.
Reported-by: Agostino Sarubbo
Bug: https://bugs.gentoo.org/679788
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
Let's not allow users to "deinstall" native glibc.
Reported-by: Toralf Förster
Closes: https://bugs.gentoo.org/677474
Package-Manager: Portage-2.3.59, Repoman-2.3.12
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Builds, and tests are ok-ish, no further testing done yet
FAIL: nss/tst-nss-files-alias-leak
FAIL: nss/tst-nss-test3
FAIL: rt/tst-cputimer1
FAIL: rt/tst-cputimer2
FAIL: rt/tst-cputimer3
FAIL: conform/*/*/linknamespace
(the latter because of system 2.27)
Package-Manager: Portage-2.3.59, Repoman-2.3.12
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix by Bart Oldeman:
Stop touching C-translit.h, as it's now always automatically generated in the
build directory. Touching it creates a 0-byte file that causes missing symbols
when it's included instead of the generated file.
See here for the glibc change:
https://sourceware.org/git/?p=glibc.git;a=commit;h=053c52b17739a584ee73d336e547b15abcdabd49
Closes: https://bugs.gentoo.org/674080
Signed-off-by: Bart Oldeman <bartoldeman@gmail.com>
Package-Manager: Portage-2.3.53, Repoman-2.3.12
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.52, Repoman-2.3.12
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.52, Repoman-2.3.12
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/673124
Package-Manager: Portage-2.3.52, Repoman-2.3.12
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.52, Repoman-2.3.12
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
The ewarn lacks '<gcc-6' guard. Let's drop ewarn completely.
Reported-by: Alexander Tsoy
Closes: https://bugs.gentoo.org/669410
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11
|
|
|
|
|
| |
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
|
|
|
| |
Before unmasking this flag we still need to add checks for binutils >=2.29
and gcc >=8 ...
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Today crossdev does not install baselayout into /usr/${CTARGET}.
As a result /usr/${CTARGET}/usr/lib was not created by any ebuilds.
glibc ebuild used to create /usr/lib but recently added
install-qa-check.d/95empty-dirs by portage broke that assumption.
This change uses keepdir to ensure presense of /usr/${CTARGET}/usr/lib.
Longer term crossdev will attempt to use baselayout.
Reported-by: Vadim A. Misbakh-Soloviov <git@mva.name>
Bug: https://bugs.gentoo.org/652724
Package-Manager: Portage-2.3.43, Repoman-2.3.10
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/9069
|
|
|
|
|
|
|
|
|
|
|
| |
Normally multiarch should be enabled (where available).
But sometimes disabling multiarch is useful:
- to workaround or validate bugs specific to selected
runtime arch or IFUNC handling.
- to get code that matches -march= CFLAGS setting
Bug: https://bugs.gentoo.org/659030
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Breakage example (before this change):
# CFLAGS="-O2 -march=core2 -mno-sse4.2" emerge -v1 =glibc-2.27-r4
Here user's CFLAGS were able to override (this bug) glibc's
CFLAGS additions like:
sysdeps/i386/i686/multiarch/Makefile:CFLAGS-strspn-c.c += -msse4
'strspn' was built as 'gcc -msse4 -mno-sse4.2' and failed:
smmintrin.h:631:1: error: inlining failed in call to always_inline
‘_mm_cmpistri’: target specific option mismatch
This happens because we passed user's CFLAGS via CPPFLAGS:
Makerules:COMPILE.c = $(CC) -c $(CFLAGS) $(CPPFLAGS)
To avoid this kind of overrides this change injects user's CFLAGS
into CC/CXX. Above example will use 'gcc -mno-sse4.2 -msse4' order.
Reported-by: Philipp Psurek
Bug: https://bugs.gentoo.org/657760
Closes: https://bugs.gentoo.org/659030
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
| |
Keeping the bug open until we've been talking to upstream
about it.
Bug: https://bugs.gentoo.org/657458
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
| |
The getaddrinfo function, when called with the AI_IDN or AI_CANONIDN flags,
will use the system libidn2 library to perform IDNA encoding. Version 2.0.5
or later is recommended, otherwise there will be some failures in the glibc
test suite.
Bug: https://bugs.gentoo.org/635012
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
| |
Reported-by: Tomas Mozes
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CFLAGS=-mfpu=neon tricked glibc into not building memcpy()
implementation. It's caused by the fact that -mfpu=neon
was passed when building .c files, but was not passed
when building .S files.
This change passes CFLAGS to CPPFLAGS to apply to .S files.
Reported-by: Markus Meier
Closes: https://bugs.gentoo.org/657760
Bug: https://sourceware.org/PR23273
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
| |
[12:38:42] <Zorry> dilfridge: you can remove the einfo "Installing
Hardened Gentoo SSP and FORTIFY_SOURCE handler" and cp files too
[12:38:53] <Zorry> for glibc
[12:50:17] <dilfridge> ok
[12:50:20] <dilfridge> will do
Closes: https://bugs.gentoo.org/601718
Package-Manager: Portage-2.3.36, Repoman-2.3.9
|
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/654524
Bug: https://bugs.gentoo.org/647070
Package-Manager: Portage-2.3.36, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.36, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
See https://github.com/gentoo/gcc-multilib-bootstrap/ for the source.
This is as good as we can do at the moment. Tested by building an
x32 glibc on a normal amd64 system.
For the glibc-2.26 stabilization we still need new files for PowerPC.
Current status:
* amd64, x32, x86: Files from gcc-6.4
* s390, s390x: Files from gcc-5.4 (does this work?)
* ppc, ppc64: no files, since only gcc-4.9 available
* n32, n64, o32: no files, last mips stages are years old, not useful
Bug: https://bugs.gentoo.org/647070
Package-Manager: Portage-2.3.31, Repoman-2.3.9
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/601718
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
|
| |
Noticed as warnings on non-existing path when installing
=cross-powerpc64le-foo-linux-gnu/glibc-2.27-r1
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
| |
glibc-2.27 needs 2 more sanity checks from native compiler to pass configure:
libc_cv_compiler_powerpc64le_binary128_ok=yes
libc_cv_target_power8_ok=yes
Notices when tried clean toolchain botstrap for bug #652724
Bug: https://bugs.gentoo.org/652724
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
|
| |
Changed 'preconfigure' mangling from using sed to using CPPFLAGS.
While at it move the hack closer to ./configure call.
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
| |
ports/ is no more. All mips ports were merged into glibc repository.
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
| |
This pulls in commit from 2.27-r1
"sys-libs/glibc: Add support for building RISC-V headers"
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The error is found by wm_ attempting to build a cross-compiler
CHOST=powerpc-unknown-linux-gnu CTARGET=mips64-unknown-linux-gnu
Boostrap failed on glibc-headers (./configure phase) as:
configure:2623: powerpc-unknown-linux-gnu-gcc -mabi=n32 -c \
-O1 -pipe -U_FORTIFY_SOURCE conftest.c >&5
powerpc-unknown-linux-gnu-gcc: error: \
unrecognized command line option '-mabi=n32'; did you mean '-mabi=d32'?
Note how target's ABI is mexed into host's compiler flags.
The error above happens on every host=non-multilib target=multilib combination.
I've reproduced it on:
CHOST=i686-pc-linux-gnu CTARGET=mips64-unknown-linux-gnu
The fix is not to inject target's CFLAGS ABI into CC for
USE=headers-only bootstrap step as we don't have cross-compiler yet.
Tested by successfully bootstrapping cross-compiler on
CHOST=i686-pc-linux-gnu CTARGET=mips64-unknown-linux-gnu
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
| |
painful(tm)
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
| |
do_run_test() was called unconditionally for all CBUILD/CHOST/CTARGET
combinations. This broke pkg_setup() for cross-*/glibc ebuild.
Change moves do_run_test() back under native guard.
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To recover broken system automatically from bug #646424
we need to skip IA32 ABI checks as those require multiabi
glibc checks at glibc build time.
There is no need to impose it as a requirement. Fail test
only if it compiled successfully and failed at runtime.
Bug: https://bugs.gentoo.org/326693
Bug: https://bugs.gentoo.org/646424
Package-Manager: Portage-2.3.20, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.20, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
|
| |
multilib.eclass has a EMULTILIB_PKG="true" knob to declare package
as multilib-compatible. This knob was lost in glibc-2.27 in commit
e77866cf2155f9b9a74c015589f3ac95a8edc2be
("sys-libs/glibc: Various cleanups. Work in progress.")
Closes: https://bugs.gentoo.org/646424
Package-Manager: Portage-2.3.20, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.23, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.23, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
|
| |
mips and mips64 were fixed upstream in https://sourceware.org/PR22624
Bug: https://sourceware.org/PR22624
Closes: https://bugs.gentoo.org/640130
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/279260
Bug: https://bugs.gentoo.org/645016
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|