| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
hack to binutils and use the stock sparc64 sources.
|
|
|
|
| |
framework wants.
|
| |
|
|
|
|
| |
by gdb(1). While here, sort SRCS.
|
|
|
|
|
|
|
|
|
|
| |
achieve on ia64, because we need to generate the ELF64/ia64 code and
simply tag elf-fbsd-brand.c at the end of it.
This hasn't actually been tested beyond trivial compilation testing.
A buildworld has been started and it's time I wait for my changes to
loop back to my local repo anyway. I'll get back to this in a couple
of hours...
|
|
|
|
|
| |
into a BFD. It's included in stock BFD on the platforms I checked
(i386 and ia64).
|
|
|
|
|
|
| |
makefiles to the centralized makefile. This not only reduces
duplication, it also makes the MD quirks stand out better and
thus improves maintenance.
|
|
|
|
|
|
|
|
|
| |
o BFD_VERSION_DATE now reflects the release date of 2.15,
o BFD_VERSION now has the correct version number.
Previous values reflected 2.14.92 from a week prior to release.
While here, fix a whitespace (tab) nit.
|
|
|
|
|
| |
o HAVE_SEEKO and HAVE_TELLO are defined now. These are used in bfdio.c.
o HAVE_STRTOULL is defined now. This is used in bfd.c.
|
| |
|
|
|
|
|
|
| |
stable ld.so. We need to revisit the rtld-elf/sparc64/rtld_start.S
rev. 1.5 and rtld-elf/sparc64/rtld_machdep.h rev. 1.5, which was
suppose to allow stock Binutils 2.13 (and later) to be used.
|
| |
|
|
|
|
| |
GDB 5.12 cannot consume the 2.15 bfd and libiberty.
|
|
|
|
| |
Also quiet some warnings by tweaking the included headers.
|
|
|
|
| |
amd64 world. The csu code evalues this Makefile with a different origin.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(bogus, application name space) mcount function name on amd64. Override
it here instead.
I've done it this way to avoid touching gcc source while 3.4 is in
progress, and this is the smallest, lowest impact I could come up with.
Adding a patch touches about 10-14 lines of Makefile, this touches only 1.
This will likely go away with the 3.4 import.
I spoke with Alexander about this a few days ago, but waited until after
sorting out some of the other bugs in the userland profiling.
|
| |
|
| |
|
|
|
|
|
| |
than a hardlink. This will make it easier for people
to tell which system tar they're currently using.
|
|
|
|
| |
to get used again in the future.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
One thing Gzip does is implicitly by store the size of a file into an
'unsigned long' rather than explicitly compute the remainder modulo 2^32
(see RFC 1952 section 2.3.1 "ISIZE"). Thus an extracted file size is
does not equal the original size (mod 2^32) for files larger than 4GB.
This manifests itself in errors such as:
zcat: bigfile.gz: invalid compressed data--length error
PR: 66008, 66009
Submitted by: Peter Losher <Peter_Losher@isc.org>
Patch by: tjr
|
|
|
|
| |
4GB on architectures with 64-bit long integers.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The GCC developers separated out the configure header between libU77 and
libI77 and FreeBSD didn't keep up with the change. So now this header needs
to be a superset of both sublib's configuration specification.
Notably this commit causes ftruncate(), fseeko(), and ftello() to be used.
PR: 22635
|
| |
|
| |
|
|
|
|
|
| |
GDB 5.2 can't handle a 64-bit BFD on a 32-bit host.
We can revisit configuring with --enable-64-bit-bfd when we get a modern GDB.
|
| |
|
| |
|
|
|
|
| |
up his day. The *.patch files are still fine for MFC'ing.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
A malicious CVS server could cause your CVS client to overwrite
arbitrary files (CAN-2004-0180).
When a CVS client uses the `-p' checkout option, the server could be
fooled into checking out files from outside the given $CVSROOT.
(This patch is applied in an unorthodox manner so as not to complicate
a later vendor import of CVS.)
|
| |
|
|
|
|
| |
Reminded by: marcel
|
|
|
|
|
|
|
| |
PR: gnu/65209
Submitted by: Craig Rodrigues <rodrigc@crodrigues.org>
Discussed with: julian,deischen
MFC after: 1 day
|
|
|
|
|
|
| |
PR: 64081
Submitted by: Chris Pepper <pepper@reppep.com>
MFC after: 1 day
|
| |
|
| |
|
|
|
|
| |
<gnu/regex.h> vs. just <regex.h>.
|
|
|
|
|
|
| |
either.
Reviewed by: obrien
|
|
|
|
| |
the entire command.
|
|
|
|
|
| |
it makes cross-build fail.
Prefer invisible incorrect -current build to visible failure.
|
|
|
|
| |
-I${DESTDIR}/usr/include to pick correct regex.h
|
|
|
|
| |
getopt.h (as workaround until it will be removed from contrib)
|