summaryrefslogtreecommitdiffstats
path: root/gnu/usr.bin
Commit message (Collapse)AuthorAgeFilesLines
* GDB has moved up one level.obrien2004-06-251-8/+0
|
* Hook gdb into the build. Exclude gdb on arm and powerpc as supportmarcel2004-06-251-1/+8
| | | | does not exist yet. The NO_GDB knob is respected.
* Remove building gdb info files. The gdb info files are built as partmarcel2004-06-251-31/+3
| | | | | of building gdb itself, which has been decoupled from binutils for as much as is reasonable.
* Add bmake glue for gdb 6.1.1. Supports alpha, amd64, i386, ia64marcel2004-06-2522-0/+4513
| | | | | | | and sparc64. Note that the debugger doesn't support threading, nor kernel debugging yet.
* Turn back on the building of GDB info files.obrien2004-06-231-4/+0
|
* This should be the right set of docs sources.obrien2004-06-211-3/+5
|
* Disable building of GDB info files until the gdb6 upgrade is finished.obrien2004-06-212-2/+8
|
* With tmm's latest change to the sparc64 dynamic loader, we can remove thisobrien2004-06-202-19/+1
| | | | hack to binutils and use the stock sparc64 sources.
* Our 'TOOLS_PREFIX' and not 'DESTDIR' matches what the stock GNU buildobrien2004-06-201-2/+2
| | | | framework wants.
* Update to binutils 2.15.marcel2004-06-191-15/+20
|
* Seperately add regex.c and splay-tree.c to SRCS. They are both neededmarcel2004-06-191-6/+9
| | | | by gdb(1). While here, sort SRCS.
* Add the necessary branding of ELF files. This is relatively easy tomarcel2004-06-191-3/+2
| | | | | | | | | | 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...
* Add bfdwin.c to SRCS. The file contains support for mmap(2) windowsmarcel2004-06-191-1/+1
| | | | | into a BFD. It's included in stock BFD on the platforms I checked (i386 and ia64).
* Move the elf32-target.h and elf64-target.h targets from the MDmarcel2004-06-197-20/+6
| | | | | | makefiles to the centralized makefile. This not only reduces duplication, it also makes the MD quirks stand out better and thus improves maintenance.
* Update to binutils 2.15:marcel2004-06-191-3/+3
| | | | | | | | | 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.
* Update to binutils 2.15:marcel2004-06-191-5/+26
| | | | | 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.
* Update to binutils 2.15.marcel2004-06-191-891/+1251
|
* Commit a crude hack so we get sparc64 snapshots working again with aobrien2004-06-172-1/+19
| | | | | | 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.
* Updated Bmake framework for Binutils 2.15.obrien2004-06-1642-3846/+5536
|
* Disable gdb from the build due to the impending binutils 2.15 import.obrien2004-06-161-1/+1
| | | | GDB 5.12 cannot consume the 2.15 bfd and libiberty.
* Sperate out the MD parts of kvm-fbsd to get rid of the #ifdef maze.obrien2004-06-115-275/+317
| | | | Also quiet some warnings by tweaking the included headers.
* Revise previous commit - I managed to mess up a 1-line change and brokepeter2004-06-111-1/+1
| | | | amd64 world. The csu code evalues this Makefile with a different origin.
* The gcc/config/i386/freebsd64.h file neglects to override the defaultpeter2004-06-102-0/+10
| | | | | | | | | | | | | (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.
* Turn cvs back on after import; that was less painful than I expected.peter2004-06-101-1/+1
|
* Turn off cvs while import/merging.peter2004-06-101-1/+1
|
* Have /usr/bin/tar be a symlink to /usr/bin/gtar ratherkientzle2004-06-041-1/+1
| | | | | than a hardlink. This will make it easier for people to tell which system tar they're currently using.
* Remove componenst which are not part of GCC 3.3 and which are not likelykan2004-05-294-115/+0
| | | | to get used again in the future.
* Use pcbp->pcb_ufp for UltraSparc vs. ->pcb_fp.obrien2004-05-101-2/+2
|
* Restore vendor Id.obrien2004-05-031-1/+3
|
* Tweak to rev 1.8 to match the offical http://www.gzip.org/gzip-1.2.4b.patchobrien2004-05-031-2/+3
|
* Gzip assumes 'unsigned long' is 32-bits wide and depends on this.obrien2004-05-021-3/+6
| | | | | | | | | | | | | | 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
* Apply patch from gzip web page to correctly decompress files larger thantjr2004-05-021-10/+14
| | | | 4GB on architectures with 64-bit long integers.
* Revert rev 1.21 which configured with --enable-64-bit-bfd.obrien2004-04-181-1/+1
| | | | | 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.
* Removed local bits that are now part of the standard mdoc(7) package.ru2004-04-161-8/+1
|
* Whitespace nit in previous revision.ru2004-04-151-1/+1
|
* Update bmake glue for cvs-1.11.15, with apologies to Jacques for messingpeter2004-04-154-69/+7
| | | | up his day. The *.patch files are still fine for MFC'ing.
* Turn off cvs build for a few hours while importing.peter2004-04-151-3/+3
|
* Patch vulnerabilities in the CVS client and server:nectar2004-04-143-2/+65
| | | | | | | | | | | 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.)
* Added FreeBSD 5.2.1, just in case.ru2004-04-131-0/+1
|
* Added upcoming 4.10 and 5.3 releases.ru2004-04-131-0/+2
| | | | Reminded by: marcel
* Add a new threads category.ceri2004-04-051-0/+1
| | | | | | | PR: gnu/65209 Submitted by: Craig Rodrigues <rodrigc@crodrigues.org> Discussed with: julian,deischen MFC after: 1 day
* Get rid of a spurious "the".dannyboy2004-03-181-1/+1
| | | | | | PR: 64081 Submitted by: Chris Pepper <pepper@reppep.com> MFC after: 1 day
* Configure as --enable-64-bit-bfd.obrien2004-03-182-2/+2
|
* I accidently spammed rev. 1.18, back out rev 1.19.obrien2004-03-171-1/+1
|
* Avoid the whole -I${DESTDIR}/usr/include/gnu issue by includingobrien2004-03-172-6/+5
| | | | <gnu/regex.h> vs. just <regex.h>.
* gasp(1) isn't linked with -lgnuregex, and it doesn't need <gnu/regex.h>ru2004-03-151-1/+0
| | | | | | either. Reviewed by: obrien
* Back out attempt to bypass contrib's getopt.h on the way,ache2004-03-053-8/+2
| | | | | it makes cross-build fail. Prefer invisible incorrect -current build to visible failure.
* Move -I${DESTDIR}/usr/include/gnu up, beforeache2004-03-052-2/+6
| | | | -I${DESTDIR}/usr/include to pick correct regex.h
* Add -I${DESTDIR}/usr/include before -I${SRCDIR}/include to pick rightache2004-03-041-0/+2
| | | | getopt.h (as workaround until it will be removed from contrib)
* Fixed "make clean".ru2004-03-031-0/+1
|
OpenPOWER on IntegriCloud