| Age | Commit message (Collapse) | Author |
|---|
|
command line option to disable it. The new default improves the
formatting of Perl manuals using UTF-8 characters (for example
perlunicook(1)) with man(1) and mandoc(1) no matter which locale
the user has set.
Issue discovered by and fix OK by afresh1@.
Trying to push this change upstream would make no sense. It's the
right thing to do only because we decided to not support any other
locales except ASCII and UTF-8. A system trying to provide arbitrary
locales simply cannot handle manuals containing UTF-8 characters
at build time, so the change would produce wrong results.
|
|
|
|
From Miod Vallat
I trust miod deraadt@
|
|
correctly - logically complete that now by removing MLINKS from base;
authors need only to ensure there is an entry in NAME for any function/
util being added. MLINKS will still work, and remain for perl to ease
upgrades;
ok nicm (curses) bcook (ssl)
ok schwarze, who provided a lot of feedback and assistance
ok tb natano jung
|
|
aren't recognized by the in-tree gdb because it's built with the bfd code
from 2.15.
From miod@.
|
|
ok otto@
|
|
|
|
arm9e (armv5te w/o xscale extensions). We no longer support anything
less than armv5te and this allows some additional instructions.
-mthumb-interwork remains off by default.
ok patrick@
|
|
|
|
could in principle be called at any point during runtime.
Instead of adding "dpath" to the relevant pledges, disable the
code path itself. Now instead of hitting a brutal abort(3), you
will just get an error message.
autoconf handholding + ok jca@
|
|
into a register. Fixes an ICE when building Mesa with __sync builtins.
From Roger Sayle in gcc svn rev 121779 in Feb 2007 before the license
change.
Tested by miod and matthieu.
|
|
from Ricardo Signes
ok deraadt@
|
|
this can happen due to the frame layout change introduced in order to
support the stack protector. Fix from miod.
Bug originally observed by jca and condensed to a 3-liner by myself,
basically local [] arrays being initialized with shorter strings.
|
|
cases from dcoppa@ where incorrect behaviour was trigged when using
std::ifstream and linking libpthread. Further investigation and patch
from miod. ok deraadt@
|
|
|
|
from Jan Schreiber, ok deraadt@
|
|
https://rt.perl.org/Ticket/Display.html?id=126862
|
|
|
|
ok deraadt@
|
|
|
|
Similar to changes made in FreeBSD.
ok kettenis@
|
|
Help with testing and ok kettenis@
|
|
emit a "sync" instruction.
ok visa@
|
|
|
|
Required for building gcc 4.9
ok jsg@
|
|
In some cases GCC would generate a cmpxchg8b instruction with a memory
reference that used %ebx. This is wrong (and will almost certainly result
in SIGSEGV). This fix uses a new memory constraint "W" to prevent the use
of %ebx in this case. This differs from the approach taken by upstream so
there are no GPLv3 issues here.
Fixes the Mesa i965 dri module on i386.
ok jsg@
|
|
okay espie@ "we should be wary" deraadt@
|
|
doesn't grok DT_RUNPATH yet.
|
|
Inspired by https://sourceware.org/ml/binutils/2010-08/msg00333.html, but
expressed differently so there are no GPLv3 issues.
|
|
requested by and OK jmc@
|
|
architectures when yy_size_t becomes size_t instead of unsigned int.
ok millert@, tedu@
|
|
|
|
ok sthen@ semarie@
|
|
Just delete the tcflow(3) calls, the use case for tcflow(3) here is
a bit far-fetched.
looks good to deraadt@, ok espie@
|
|
|
|
The initial pledge(2) call is broad, we can refine later when we know
whether we run in server, pserver client mode or regular client mode.
pserver server mode is likely broken, it will either be fixed or
removed.
With and ok semarie@, "let's proceed." deraadt@
|
|
But don't restore ownership/setuid/etc bits. ok deraadt@
|
|
But don't try to chown or set special bits. This fixes several ports.
ok deraadt@
|
|
- only the binutils package (no gdb here)
- don't import libiberty and texinfo, they are elsewhere
- remove all .info* generated files
|
|
ar/ranlib and objcopy/strip can pledge "stdio rpath wpath cpath fattr"
ok guenther
|
|
of files. In two cases however they were not being masked. These are build
tools -- therefore they should not encourage further propogation of such
unsafe bits.
ok guenther
|
|
setuid-preserving code in the so-called smart_rename() function. I
don't want my tools (ar, ranlib, objcopy, strip) going through the
effort to preserve setuid bits on ``build-directory'' files when they
sense a symbolic link, thank you very much. The modern way is to build
code, then set such modes at install-time.
Our kernel goes through the effort to clear setuid flags, and this was
neutering that attempt. Also has atrocious error handling.
(Identified as an issue of concern while doing the audit for pledge)
ok guenther
|
|
infokey - stdio rpath wpath cpath tty
makeinfo - stdio rpath wpath cpath getpw
install-info - stdio rpath wpath cpath proc exec
texindex - stdio rpath wpath cpath tmppath
ok schwarze
|
|
the ports build cycle to find out for sure.
|
|
NOTE: cc1 uses brk/sbrk, which was only enabled in pledge a few hours
ago. So this requires a fairly new kernel if compiling monster c++
programs..
|
|
features that new FSF programs will need (e.g., gcc snapshots).
looked at by fgs@, thanks.
|
|
(cc1 "toplev.c" uses brk/sbrk, so it is on hold to figure out the right
direction...)
ok semarie pascal
|
|
ok semarie
|
|
ok kettenis@
|
|
kettenis ok'd me poking around in here; ingo ok'd the diff
|
