Revision tags: release/3.0.0, release/2.2.8 |
|
#
13575fc4 |
| 04-Sep-1998 |
Doug Rabson <dfr@FreeBSD.org> |
Add alpha support.
Submitted by: John Birrell <jb@cimlogic.com.au> (with extra hacks by me) Obtained from: Probably NetBSD
|
#
9d5aee94 |
| 17-Aug-1998 |
John Polstra <jdp@FreeBSD.org> |
Add "-C" to INSTALLFLAGS to install atomically. An elf->elf installworld dies at this point otherwise, leaving the system without a dynamic linker.
|
Revision tags: release/2.2.7 |
|
#
2001f720 |
| 30-Apr-1998 |
Doug Rabson <dfr@FreeBSD.org> |
Add GDB support. The method and some of the code came from NetBSD's elf runtime linker.
|
Revision tags: release/2.2.6 |
|
#
3124c3e0 |
| 07-Mar-1998 |
John Polstra <jdp@FreeBSD.org> |
Import the ELF dynamic linker. This is the ElfKit version with quite a few enhancements and bug fixes. There are still some known deficiencies, but it should be adequate to get us started with ELF.
Import the ELF dynamic linker. This is the ElfKit version with quite a few enhancements and bug fixes. There are still some known deficiencies, but it should be adequate to get us started with ELF.
Submitted by: John Polstra <jdp@polstra.com>
show more ...
|
#
9199c09a |
| 06-Jan-2010 |
Warner Losh <imp@FreeBSD.org> |
Merge from head at r201628.
# This hasn't been tested, and there are at least three bad commits # that need to be backed out before the branch will be stable again.
|
#
1100c001 |
| 02-Jan-2010 |
Ed Schouten <ed@FreeBSD.org> |
Make WARNS=6 the default for libexec/.
Just like bin/ and sbin/, I think setting WARNS to the highest value possible will make it more attractive for people to fix warnings.
- The WARNS variable is
Make WARNS=6 the default for libexec/.
Just like bin/ and sbin/, I think setting WARNS to the highest value possible will make it more attractive for people to fix warnings.
- The WARNS variable is set in the Makefile in the directory of the application itself, making it more likely that it will be removed out of curiosity to see what happens. - New applications will most likely build with WARNS=6 out of the box, because the author would more likely fix the warnings during development than lower WARNS.
Unfortunately almost all apps in libexec require a lowered value of WARNS.
show more ...
|
#
11e9b8ba |
| 04-Aug-2009 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
- MFC @196061
|
#
2286fe76 |
| 14-Jul-2009 |
Alexander Kabaev <kan@FreeBSD.org> |
Second attempt at eliminating .text relocations in shared libraries compiled with stack protector.
Use libssp_nonshared library to pull __stack_chk_fail_local symbol into each library that needs it
Second attempt at eliminating .text relocations in shared libraries compiled with stack protector.
Use libssp_nonshared library to pull __stack_chk_fail_local symbol into each library that needs it instead of pulling it from libc. GCC generates local calls to this function which result in absolute relocations put into position-independent code segment, making dynamic loader do extra work every time given shared library is being relocated and making affected text pages non-shareable.
Reviewed by: kib Approved by: re (kib)
show more ...
|
#
d48890cf |
| 29-Jun-2009 |
Alexander Kabaev <kan@FreeBSD.org> |
Back out previous revision until better tested fix is ready.
Approved by: re (impliciti, by approving previos check-in)
|
#
a162c9ae |
| 29-Jun-2009 |
Alexander Kabaev <kan@FreeBSD.org> |
Eliminate .text relocations in shared libraries compiled with stack protector.
Use libssp_nonshared library to pull __stack_chk_fail_local symbol into each library that needs it instead of pulling i
Eliminate .text relocations in shared libraries compiled with stack protector.
Use libssp_nonshared library to pull __stack_chk_fail_local symbol into each library that needs it instead of pulling it from libc. GCC generates local calls to this function which result in absolute relocations put into position-independent code segment, making dynamic loader do extra work everys time given shared library is being relocated and making affected text pages non-shareable.
Reviewed by: kib Approved by: re (kensmith)
show more ...
|
Revision tags: release/7.2.0_cvs, release/7.2.0 |
|
#
1829d5da |
| 12-Mar-2009 |
Warner Losh <imp@FreeBSD.org> |
Update the projects tree to a newer FreeBSD current.
|
#
d9ca85fc |
| 21-Feb-2009 |
Ruslan Ermilov <ru@FreeBSD.org> |
Fix build when WITH_SSP is set explicitly.
Submitted by: Jeremie Le Hen
|
Revision tags: release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0 |
|
#
042df2e2 |
| 25-Jun-2008 |
Ruslan Ermilov <ru@FreeBSD.org> |
Enable GCC stack protection (aka Propolice) for userland: - It is opt-out for now so as to give it maximum testing, but it may be turned opt-in for stable branches depending on the consensus. You
Enable GCC stack protection (aka Propolice) for userland: - It is opt-out for now so as to give it maximum testing, but it may be turned opt-in for stable branches depending on the consensus. You can turn it off with WITHOUT_SSP. - WITHOUT_SSP was previously used to disable the build of GNU libssp. It is harmless to steal the knob as SSP symbols have been provided by libc for a long time, GNU libssp should not have been much used. - SSP is disabled in a few corners such as system bootstrap programs (sys/boot), process bootstrap code (rtld, csu) and SSP symbols themselves. - It should be safe to use -fstack-protector-all to build world, however libc will be automatically downgraded to -fstack-protector because it breaks rtld otherwise. - This option is unavailable on ia64.
Enable GCC stack protection (aka Propolice) for kernel: - It is opt-out for now so as to give it maximum testing. - Do not compile your kernel with -fstack-protector-all, it won't work.
Submitted by: Jeremie Le Hen <jeremie@le-hen.org>
show more ...
|
Revision tags: release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0 |
|
#
cc09c7fb |
| 17-May-2007 |
Marcel Moolenaar <marcel@FreeBSD.org> |
Don't enable symbol versioning on ia64 for now. It causes symbol lookup failures that later result in null-pointer dereferences. This needs looking into, but since we're close to release it's possibl
Don't enable symbol versioning on ia64 for now. It causes symbol lookup failures that later result in null-pointer dereferences. This needs looking into, but since we're close to release it's possible that it's not resolved before that time.
show more ...
|
#
00fb440c |
| 13-May-2007 |
Daniel Eischen <deischen@FreeBSD.org> |
Enable symbol versioning by default. Use WITHOUT_SYMVER to disable it. Warning, after symbol versioning is enabled, going back is not easy (use WITHOUT_SYMVER at your own risk).
Change the default
Enable symbol versioning by default. Use WITHOUT_SYMVER to disable it. 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.
show more ...
|
#
effa5b4e |
| 29-Apr-2007 |
Alexander Kabaev <kan@FreeBSD.org> |
Retire rtld-specific Versions.def. Symbols exported by rtld are supposed to override weak symbols exported by libc, so by definition these two are using the same symbol version names.
Reflect the re
Retire rtld-specific Versions.def. Symbols exported by rtld are supposed to override weak symbols exported by libc, so by definition these two are using the same symbol version names.
Reflect the reality by referring to libc's Versions.def directly.
show more ...
|
#
3c0d0ca7 |
| 10-Apr-2007 |
Alexander Kabaev <kan@FreeBSD.org> |
Bring rtld exports in line with corresponding symbols exported from libc.
Disable SYMVER_DEFAULT n rtld until its implications are understood better.
|
#
7ca8e6a6 |
| 03-Apr-2007 |
Alexander Kabaev <kan@FreeBSD.org> |
Prepare rtld for symbol versioning. Disable it by default for now.
|
Revision tags: release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0 |
|
#
1b1aa7e4 |
| 14-Nov-2004 |
Ruslan Ermilov <ru@FreeBSD.org> |
So do it like we do in usr.bin/tip/tip/Makefile. ;)
|
#
443ceb1c |
| 14-Nov-2004 |
Jens Schweikhardt <schweikh@FreeBSD.org> |
Revert previous commit. As ru explains:
In the old world (as the surrounding comment in makefile says), there was the /usr/libexec/ld-elf.so.1 binary which is now a symlink to /libexec/ld-elf.so.
Revert previous commit. As ru explains:
In the old world (as the surrounding comment in makefile says), there was the /usr/libexec/ld-elf.so.1 binary which is now a symlink to /libexec/ld-elf.so.1. To symlink, we need to make sure that the _target_ (and the target is /usr/libexec/ld-elf.so.1) doesn't have "schg" flag set. A real solution is to protect the chflags call only if target exists, like we do in usr.bin/tip/tip/Makefile.
Requested by: ru
show more ...
|
#
6ccc491b |
| 14-Nov-2004 |
Jens Schweikhardt <schweikh@FreeBSD.org> |
Avoid an (ignored) error by invoking chflags on the link target, not the symlink.
PR: kern/73016 Submitted by: John E. Hein <jhein@timing.com> MFC after: 1 week
|
Revision tags: release/5.3.0_cvs, release/5.3.0 |
|
#
dee651eb |
| 03-Nov-2004 |
Ruslan Ermilov <ru@FreeBSD.org> |
Introduce the PRECIOUSPROG knob in bsd.prog.mk, similar to PRECIOUSLIB from bsd.lib.mk. The side effect of this is making installing the world under jail(8) possible by using another knob, NOFSCHG.
Introduce the PRECIOUSPROG knob in bsd.prog.mk, similar to PRECIOUSLIB from bsd.lib.mk. The side effect of this is making installing the world under jail(8) possible by using another knob, NOFSCHG.
Reviewed by: oliver
show more ...
|
#
a35d8893 |
| 24-Oct-2004 |
Ruslan Ermilov <ru@FreeBSD.org> |
For variables that are only checked with defined(), don't provide any fake value.
|
#
45ab3f53 |
| 17-Jun-2004 |
Olivier Houchard <cognet@FreeBSD.org> |
This comment should have been removed in the previous commit.
Spotted out by: marcus, simon
|
#
f77d42ce |
| 17-Jun-2004 |
Olivier Houchard <cognet@FreeBSD.org> |
Woohoo ! the latest binutils import mades this gross hack useless, so just remove it.
|