| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This produces a list of currently supported targets. Here "supported"
means "built in make universe" on the theory that those targets are
more supported than any that might work in 'make buildworld TARGET=x
TARGET_ARCH=y' since the latter are less tested.
Suggested by: rwatson
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement MACHINE_ARCH=mips64e[lb] to build N64 images. This replaces
MACHINE_ARCH=mipse[lb] TARGET_ABI=n64.
MACHINE_ARCH=mipsn32e[lb] has been added, but currently requires
WITHOUT_CDDL due to atomic issues in libzfs. I've not investigated
this much, but implemented this to preserve as much of the TARGET_ABI
functionality that I could. Since its presence doesn't affect the
working cases, I've kept it in for now.
Added mips64e[lb] to make universe, so more kernels build.
And I think this (finally) closes the curtain on the tbemd tree.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
not the one we build as part of make world. This means that make
universe will fail if building on a too-old current or any stable
system prior to a few days ago in weird ways (parse errors from
shell). This copes with these old systems in two ways:
(1) Works around the WARNING: issue by filtering all warnings that
sneak onto stdout.
(2) if TARGET_ARCH_${kernel} winds up being empty, then we error out
immediately with a semi-useful error message. This usually comes from
config not groking -m.
Ideally, we'd use a buildworld's config here, but that's tricky, so
I'll leave that detail to others to fix (it has to be done post make
world for the arch rather than at the top level makefile). This
should make 'make universe' usable from recent 8-stable systems
(recent == last few months or so) for building -current. They have
-m, but spewed warnings out stdout. Older systems will now at least
get a firm error early rather than a confusing error late.
|
|
|
|
|
| |
of annoying warnings when dealing with arm. The arm config files need
to be fixed, but this restricts the output to a more useful place.
|
|
|
|
|
|
|
| |
and powerpc64 to universe for the first time. In general, provide
(slightly hacky) knowledge of multi-architecture TARGETs to universe as
well as the ability to distinguish the correct toolchain for a given
kernel using config -m.
|
|
|
|
|
|
|
|
|
| |
semantics for JFLAG with tinderbox as for universe. Previously doing
'make JFLAG=-j4 tinderbox' was equivalent to 'make -j4 universe'
(i.e. 4 worlds in parallel) rather than 'make JFLAG=-j4 universe'
(i.e. worlds in sequence, each built with -j4).
MFC after: 1 month
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
TARGET_BIG_ENDIAN is now completely dead, except where it was
originally supposed to be used (internally in the toolchain building).
TARGET_ARCH has changed in three cases:
(1) Little endian mips has changed to mipsel.
(2) Big endian mips has changed to mipseb.
(3) Big endian arm has changed to armeb.
Some additional changes are needed to make 'make universe' work on arm
and mips after this change, so those are commented out for now.
UPDATING information will be forthcoming. Any remaining rough edges
will be hammered out in -current.
|
|
|
|
|
| |
Reviewed by: imp
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
| |
of kernel hackery, add MAKE_JUST_WORLDS so that we can take part in
the 'make universe' goodnes without using unecessary time and resources.
|
|
|
|
| |
build(7), many people look here for a quick reminder...
|
|
|
|
|
| |
It was just a local modification to build the i386 and amd64 more
quickly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove __gnu89_inline.
Now that we use C99 almost everywhere, just use C99-style in the pmap
code. Since the pmap code is the only consumer of __gnu89_inline, remove
it from cdefs.h as well. Because the flag was only introduced 17 months
ago, I don't expect any problems.
Reviewed by: alc
It was backed out, because it prevented us from building kernels using a
7.x compiler. Now that most people use 8.x, there is nothing that holds
us back. Even if people run 7.x, they should be able to build a kernel
if they run `make kernel-toolchain' or `make buildworld' first.
|
|
|
|
|
|
|
|
| |
then directly assign the result.
Submitted by: jmallett
MFC after: 24 days
X-MFC with: r201815
|
|
|
|
|
|
| |
Submitted by: nyan[1], imp[2]
MFC after: 27 days
X-MFC with: r201815
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
make universe, split the logic into two parts:
- 1st to build worlds and generate kernel configs like LINT.
- 2nd to build kernels for a given TARGET architecture correctly
finding all newly generated configs, not knowing anything about
LINT anymore. (*)
(*) If you know better/cleaner/... ways to do this, let me know.
Discussed on/with: arch, jhb, rwatson
MFC after: 1 month
|
|
|
|
| |
Discussed with: imp
|
|
|
|
|
|
| |
you can build the cross development tools and install them as
$XDEV-freebsd-xxx for each tool. This allows one to use autoconf to
find the tools for cross building scenarios.
|
|
|
|
|
|
|
|
| |
`make universe'. This catches a few more arm and, once enabled, mips
configs and permits having local configs named like NOINET6.
Reviewed by: phk
MFC after: 4 weeks
|
|
|
|
|
|
|
|
| |
a developer can rest reasonably assured that the tinderbox will not
be broken. This target leverages most of 'universe' but will exit
non-zero and output a summary at the end.
"make tinderbox"
|
|
|
|
|
|
|
| |
fails. The error message includes a reference to the relevant log file.
Approved by: phk
MFC after: 1 week
|
|
|
|
|
| |
SRCCONF was omitted here to be able to build non standard trees
with universe as well.
|
|
|
|
|
|
|
| |
src.conf with possibe non-default options.
Reviewed by: ru
MFC after: 10 days
|
|
|
|
|
| |
Note that sun4v is currently broken on T2000 hardware so it's pretty
much a lame duck at this point.
|
|
|
|
|
|
| |
no active development on it for over a year now and it isn't
reliable under a simple buildworld. Developers can't be expected to
test code targeted for it.
|
|
|
|
|
| |
This is useful when wanting to retry a broken build using NOCLEAN and the
buildworlds are known to have completed.
|
|
|
|
|
|
|
| |
general mergemaster line.
MFC after: 3 days
Suggested by: Ben Laurie
|
|
|
|
|
|
| |
PR: misc/99735
Reported by: Philip M. Gollucci <pgollucci@p6m7g8.com>,
Maxim Konovalov <maxim@macomnet.ru>
|
|
|
|
| |
set incorrectly.
|
|
|
|
|
| |
MFC after: 1 week
Reviewed by: ru
|
|
|
|
| |
Submitted by: jmallet@
|
|
|
|
|
|
| |
only matters in the early stages of bootstrapping, of course, but gnu make can't
handle bsd make Makefiles at all if they use any of the 'dot' directives, which
src/Makefile has in abudnance.
|
|
|
|
| |
chflags is failed.
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and that controls which platforms are being built as part of a "make
universe". By default TARGETS is set to the 8 platforms currently
being built. This variable is useful for running or re-running a
"make universe" with only a selected set of platforms. This makes the
universe target slightly more useful in cases the universe is limited
to a developer's scope or objectives. For example, when a universe
failed for a particular platform and fixes need to be tested for that
particular platform then a developer can restart the universe for
only that platform, even if the initial universe is still building
other platforms.
|
| |
|
|
|
|
| |
DTrace.
|
|
|
|
|
| |
use with DTrace because the normal buildworld will do that when the
tools are built.
|
| |
|
|
|
|
|
|
| |
"make TARGET=<machine> build*", now that it actually works.
Prompted by: imp
|
|
|
|
|
|
|
|
|
|
|
| |
HISTORICAL_MAKE_WORLD from the text that's output. This was committed
against the previous consensus. Leave the documentation in this file
as a compromose. The HISTORICAL_MAKE_WORLD knob is intentionally
obfuscated and we only trust people smart enough to read the Makefile
to use it. All others have no business using it due to its danger,
unless DESTDIR is set.
Dissentors: grog, obrien, trhodes
|
| |
|
|
|
|
|
|
|
|
|
| |
undocumented HISTORICAL_MAKE_WORLD variable and set it. Note it
here so the blow up will not really be a surprise to people who
read.
Link the buildingworld chapter of our handbook in the README
while I'm here.
|
|
|
|
|
|
|
|
|
|
|
| |
environment for cross building (the same one you'd get interactively
in make buildenv). This cannot be a simple
make -f Makefile.inc1 -V WMAKEENV
because in PATH is not set correctly unless one takes a trip through
the Makefile/Makefile.inc1 indirection, the logic of which is too
large to reproduce outside of Makefiles.
|
|
|
|
|
|
|
|
| |
the build infrastructure: "make doxygen"
Changes to the man pages will be made when some defaults are revisited.
Requested by: gnn
|
| |
|
|
|
|
| |
Suggested by: phk
|