| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
build libkse. This should fix WITHOUT_LIBTHR builds as a side effect.
|
|
|
|
|
|
| |
to use GNU tools. Remove the _WITH_GNUAR knob.
Prodded by: obrien
|
|
|
|
| |
Prodded by: obrien
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
source upgrades by falling back to GNU ar(1) as necessary. Option
WITH_BSDAR is gone. Option _WITH_GNUAR to aid in upgrades is *not*
supposed to be set by the user.
Stop bootstrapping BSD ar(1) on the next __FreeBSD_version bump, as
there are no known bugs in it. Bump __FreeBSD_version to anticipate
this and to flag the switch to BSD ar(1), should it be needed for
something.
Input from: obrien, des, kaiw
|
| |
|
|
|
|
|
|
|
|
|
| |
and usr.bin/truss/ioctl.c. This is the correct way to address the problem
that arises when doing an incremental build after a header used by kdump
has been removed (cf. i4b disconnect a while ago)
Explained by: ru
MFC after: 2 weeks
|
|
|
|
| |
Reviewed by: imp, obrien
|
| |
|
| |
|
|
|
|
| |
to RELENG_7 are not supported.
|
|
|
|
|
|
| |
Reviewed by: imp, kan
Approved by: rwatson (mentor)
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
through scanning its output as ldd(1) returns a non-zero status only
for really abnormal conditions such as an improper file format.
Now cp(1) won't get bogus "not" and "found" arguments if a lib
is missing. [1]
- Don't guess if an element of a complex pipeline is assigned to the main
shell or a sub-shell. Namely use stdio, not vars, to pass lists out from
loops. If using vars, there's the risk that a loop will run in a sub-shell
and the list won't make it to the main shell. It appears that braces and
parens give only limited control over the issue while stdio always works
as intended. Apply this solution to both $progs and $libs for consistency,
although I've failed to go without it only in the $libs part.
Requested by: emaste [1]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I.e., not only copy them to a scratch dir, but also make them use saved
copies of libraries and locale files. That gives us several benefits:
1) ABI breakages should no longer affect installworld over the live system.
2) It becomes safe to run installworld while still running the old kernel.
However, it can be reasonable to save the old /rescue before that to be
able to run the old reboot(8), as the new binaries are rather likely to
fail with the old kernel. Anyhow, it's now possible to upgrade a system
in a single reboot _reliably_.
3) With a bit of hackery around rtld(8), it becomes possible to do destructive
cross-installs, e.g., i386->amd64 over the live system.
The only shared item left between the old and new systems is rtld(8),
which cannot be run from a saved copy easily because its full
pathname is stored in the respective field of each ELF executable.
(In theory, that field could be overridden, e.g., from the environment,
but this can lead to security issues.) That's why a destructive
cross-install isn't possible w/o hackery yet.
Fruitful ideas by: ru
Reviewed by: ru
Tested with: audit(4)
|
|
|
|
| |
message (instead of cp's usage info).
|
|
|
|
|
|
|
| |
treatment of 'LIBKSE' as an "old style" knob.
Submitted by: ru
Approved by: re(kensmith)
|
|
|
|
|
|
| |
This introduces the WITHOUT_LIBKSE nob,
and changes WITHOUT_LIBPTHREADS to mean with neither threading libs.
Approved by: re(kensmith)
|
|
|
|
|
|
|
| |
${WORLDTMP} and ${LIB32TMP}; some of them are no longer
needed, and some were never needed.
Approved by: re (kensmith)
|
|
|
|
|
|
|
|
|
|
|
|
| |
the threading libraries is built. This simplifies the
logic in makefiles that need to check if the pthreads
support is present. It also fixes a bug where we would
build a threading library that we shouldn't have built:
for example, building with WITHOUT_LIBTHR and the default
value of DEFAULT_THREADING_LIB (libthr) would mistakenly
build the libthr library, but not install it.
Approved by: re (kensmith)
|
|
|
|
|
|
| |
buildworld.
Approved by: re (rwatson)
|
|
|
|
| |
(since src/usr.bin/lex/Makefile,v 1.20).
|
|
|
|
| |
ZFS, which doesn't support flags...
|
|
|
|
|
|
| |
their dependency on libc and its versioned symbols. For that to work,
libc needs to be built before any other shared library that might depend
on it. Add necessary glue to make that happen.
|
|
|
|
| |
Noticed by: John E Hein <jhein@timing.com>
|
|
|
|
| |
MFC after: 3 weeks
|
| |
|
|
|
|
|
|
|
| |
logic.
Apply similar modifications to {check,delete}-old-dirs, which I had
overlooked.
|
|
|
|
|
| |
Pointed out by: netchild
MFC after: 3 weeks
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
| |
Warning, after symbol versioning is enabled, going back is not easy
(use WITHOUT_SYMVER at your own risk).
Change the default thread library to libthr.
There most likely still needs to be a version bump for at least the
thread libraries. If necessary, this will happen later.
|
|
|
|
| |
Requested by: ru
|
| |
|
|
|
|
|
| |
Approved by: delphij (mentor)
Tested by: kris on pointyhat (early version), current@
|
|
|
|
|
|
|
| |
a note in UPDATING that tried to work around the build breakage.
Tested by: jhb
OK'ed by: njl
|
|
|
|
|
|
|
|
|
|
| |
lib32 build somewhat. Specifically, instead of spamming
${CC} et al with -I${LIB32TMP}/usr/include which can be
harmful (as has been demonstrated by the ncursesw WIP),
use slightly different approach to achieve the same goal.
This also simplifies things a bit.
Prodded by: rafan
|
|
|
|
|
| |
Discussed with: ru
MFC after: 2 weeks
|
|
|
|
| |
Approved by: delphij
|
|
|
|
|
| |
an upgrade during the build so those who are affected can
build world again.
|
|
|
|
| |
so early.
|
|
|
|
| |
This is required for 'make universe'.
|
|
|
|
|
|
|
| |
not sure why pmap.c is included as it is unchanged
Approved by: rwatson (mentor)
Reviewed by: jmg
|
| |
|
|
|
|
|
|
|
|
|
| |
- Remove libnetgraph from the list of prebuilt libraries as
no other library depends on it (snmp_netgraph.so does not
count as we don't build it in the "libraries" target).
- Restore libssh dependencies when compiling with Kerberos
support.
|
|
|
|
|
|
| |
to work. Some build-tools that are part of cross-tools (cc_tools)
also need to know the proper values of TARGET_ARCH and TARGET, so
tell them.
|
|
|
|
|
|
|
|
| |
I found one bug. Pass our idea of TARGET_ARCH and TARGET down to
XMAKE, the cross-tools make. Previously it worked because usually
TARGET_ARCH was specified on the initial make's command line.
This should also allow us to simplify the "universe" target, which
I'm currently testing.
|
| |
|
|
|
|
|
|
| |
but without changes in behavior.
- Add sanity checking for TARGET_ARCH/TARGET.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
TARGET_ARCH correctly. Now it does, even for pc98. We should suggest
TARGET=foo in preference to TARGET_ARCH because the former is
unambiguous and the latter isn't, so update the docs.
This means that a long standing gripe I've had with this comes to a
close. I can build pc98 w/o specify both things. make TARGET=arm
works (rather than trying to build a arm:amd64 image and dying badly
in the attempt).
If you specify only TARGET_ARCH, then you get the old behavior.
# we can likely simplify the UNIVERSE target now to use this, but I'm not
# up for breaking that tonight :-).
# We should consider adding some kind of sanity check for TARGET_ARCH
# and TARGET.
|
|
|
|
|
| |
helps some cross-architecture building tool installation patches that
I'm developing.
|
| |
|