| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: https://bugs.gentoo.org/574384
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/651536
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/651534
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/651534
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/651586
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/651584
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/651672
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/623942
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
RepoMan-Options: --include-arches="ia64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
RepoMan-Options: --include-arches="ia64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
RepoMan-Options: --include-arches="ia64"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
RepoMan-Options: --include-arches="ppc"
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
| |
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.7
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
RepoMan-Options: --ignore-arches
|
|
|
|
|
|
| |
This files are all bundled with repoman now.
See: https://github.com/gentoo/portage/commit/2ecf4e2b0ebdf727f2210f3b7db600e781cff1c4
|
|
|
|
| |
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.27, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.8
|
|
|
|
|
|
|
| |
This release adds support for plugin module systems.
See: https://wiki.gentoo.org/wiki/Project:Portage/Repoman-Module-specs
Package-Manager: Portage-2.3.27_p1, Repoman-2.3.8
|
|
|
|
|
|
|
| |
#651952 - INSTALL_MASK: honor install time config for binary packages
Closes: https://bugs.gentoo.org/651952
Package-Manager: Portage-2.3.27_p1, Repoman-2.3.8
|
|
|
|
|
|
|
|
| |
- EAPI6ify
- Enable tests ( don't appear to do network IO )
- Cleanup unwanted tests
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/651800
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/642796
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/642796
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
Closes: https://github.com/gentoo/gentoo/pull/7649
|
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
Closes: https://github.com/gentoo/gentoo/pull/7674
|
|
|
|
| |
Package-Manager: Portage-2.3.26, Repoman-2.3.7
|
|
|
|
|
|
|
| |
Drops stable keywords for s390 and sh
Package-Manager: Portage-2.3.26, Repoman-2.3.7
Closes: https://github.com/gentoo/gentoo/pull/7691
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/7687
|