| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
| |
EAPI 6, patches reformatted to be -p1 (still usable for the older
ebuilds), upstreamish[1] patch added to support mingw-w64.
dohtml changed to HTML_DOCS einstalldocs. Removed src_unpack as
unneeded (probably a holdover from a much older version).
[1]: http://lists.gnu.org/archive/html/bug-readline/2018-01/msg00001.html
Package-Manager: Portage-2.3.24, Repoman-2.3.6
Closes: https://github.com/gentoo/gentoo/pull/7616
|
| |
|
| |
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6_p81
|
|
|
|
| |
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
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="arm"
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
ports/ is no more. All mips ports were merged into glibc repository.
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/582740
Closes: https://bugs.gentoo.org/644782
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/646894
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
RepoMan-Options: --include-arches="ppc"
|
|
|
|
|
|
| |
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 RISC-V GCC port defines some extra preprocessor macros that glibc
uses to determine which RISC-V target is being compiled for. Since
crossdev doesn't use a RISC-V compiler to build the headers, this blows
up. These checks don't matter for building the headers because they're
the same on all RISC-V targets, so we just hack up the glibc build to
elide the check.
|
| |
|
|
|
|
|
| |
Update the 4.0.1 and 5.0.1 versions to rely on sandbox-2.13 unloading
support instead of using unsandbox.
|
| |
|
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
RepoMan-Options: --include-arches="ppc"
|
|
|
|
| |
Gentoo-Bug: http://bugs.gentoo.org/651302
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/651712
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
| |
Gentoo-Bug: http://bugs.gentoo.org/646492
|
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
RepoMan-Options: --ignore-arches
|
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/646492
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="sparc"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
RepoMan-Options: --ignore-arches
|
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
RepoMan-Options: --include-arches="ppc64"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.19, Repoman-2.3.6
|
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
RepoMan-Options: --include-arches="ia64"
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
|
| |
This is a breakout library for rpmatch() which is not provided
by the musl libc. See `man 3 rpmatch'.
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/646492
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|