| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Updates #4991
|
|
|
|
| |
This updates glib to 2.56.4 for AArch64 build support.
|
| |
|
|
|
|
| |
Updates #4991
|
|
|
|
| |
Updates #4991
|
|
|
|
|
| |
QEMU used to honor LDFLAGS and CFLAGS and has since moved to accepting
them via --extra-cflags and --extra-ldflags options to configure.
|
|
|
|
|
|
|
|
| |
Modern versions of pkg-config include new architecture-specific symlinks
that are sometimes checked before "pkg-config". This causes builds to
detect the system pkg-config instead of the local overridden pkg-config
and fail to build properly. This overrides those new symlinks to restore
build functionality.
|
| |
|
|
|
|
|
|
| |
This improves performance because it avoids an exec each time
the _uid macro is referenced and that can be a number of times
for each config parsed.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The options are:
--with-python2
--with-python3
--with-python-version
Closes #4973
|
| |
|
|
|
|
| |
Update #4921
|
|
|
|
| |
Updates #4968
|
|
|
|
|
|
|
| |
If available, use "distro" package (introduced Python 3.6, back-ported to 2.6)
to recognize Linux distributions and versions.
Updates #4966
|
|
|
|
|
|
|
|
|
| |
This patch is being moved to the 5.2.0-1 QEMU configuration because the
Xilinx QEMU build uses the 5-1 configuration and this patch does not
apply to Xilinx's modified tree. This also adds a new patch that applies
correctly to Xilinx's modified QEMU tree.
Updates #4919
|
|
|
|
|
|
|
| |
The original version of this patch had a conflict between the two
interrupts where the program-viewable interrupt state could be
deasserted when it should have been asserted. The new version of this
patch resolves that conflict.
|
|
|
|
|
|
|
|
| |
This temporarily adds a patch to fix badly behaving CGEM peripherals
under QEMU. The referenced patch has been submitted for inclusion in
the upstream QEMU repository.
Updates #4919
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The change leaves the encoding in that currently exists because
I cannot remember why it is there. If an encoding error happens
return the same path to see if it will work.
|
|
|
|
|
|
|
|
| |
- MacOS systems do not come with makeinfo
- Fix the internal build logic. There was config logic in a
bset file that does not support logic operators. Use a
special tmp internal path to isolate the internal tools.
|
|
|
|
| |
Closes #4894
|
|
|
|
|
|
|
| |
- This is a place holder incase we stop building MPFR in
GCC.
Updates #4892
|
|
|
|
|
|
|
|
| |
- Use base64 checksums
- Change MPFR URL
Updates #4892
|
|
|
|
| |
Updates #4892
|
|
|
|
|
|
|
|
| |
- Do not build GMP when building GCC. GMP is now built
as a package for GDB. Building as a separate package
lets use control how it is built.
Updates #4892
|
|
|
|
|
|
|
|
| |
- Detect and use a virtual environment if present
- Supports MacOS with python.org in a venv
Updates #4892
|
|
|
|
| |
Updates #4892
|
|
|
|
|
|
|
| |
Binutils 2.39 and later enable by default warnings for executables
with executable stack and RWX sections. Disable them.
Closes #4881
|
| |
|
|
|
|
|
|
| |
See https://sourceware.org/bugzilla/show_bug.cgi?id=30214
Closes #4872
|
|
|
|
|
| |
GitHub has reverted the change that caused all these tarball hashes to
change and so we follow suit.
|
|
|
|
|
|
|
| |
Github has changed the way it generates on-the-fly tarball requests
which has changed the hashes of the resulting tarballs. This adjusts the
affected tarball hashes as a stop-gap until a more permanent solution
can be devised.
|
|
|
|
| |
Close #4642
|
| |
|
|
|
|
|
|
| |
SIS compiles on Mac OS X fine, but without providing --host/--build
configure options. Removing them solves the issue of configure not being
able to recognize arm64-darwin platform.
|
|
|
|
|
|
| |
GNU sed compiles on Mac OS X fine, but without providing --host/--build
configure options. Hence removing them solved the issue of configure
not being able to recognize arm64-darwin platform.
|
|
|
|
|
|
|
|
| |
- Always stage a build
- Install if installable and outter most buildset instance
Closes #4730
|
|
|
|
| |
Closes #4726
|
| |
|
|
|
|
| |
Update #4726
|
|
|
|
| |
Closes #4730
|
| |
|
|
|
|
| |
Closes #2300
|
|
|
|
| |
Updates #2300
|
|
|
|
| |
- This is a bug introduced in the recent bset tar file changes
|
|
|
|
|
|
|
|
|
|
| |
- Make a single tarfile for all buildsets built
- Use the staging tree as the tarfile source
- Use python's tarfile module
- Create a config.file object without loading a .cfg file
|