summaryrefslogtreecommitdiffstats
path: root/gnu
Commit message (Collapse)AuthorAgeFilesLines
* bfd_elf32_i386_freebsd_vec is the only 32-bit vector we really need.obrien2003-07-011-1/+1
| | | | ar and nm aren't very smart when faced with multiple applicable vectors.
* Add elf_i386_fbsd emulation.obrien2003-07-011-0/+14
| | | | Obtained from: p4
* Fixed build.ru2003-07-011-0/+1
| | | | Noticed by: bde
* Don't build separate annotate.info, it's already part of gdb.info.ru2003-07-011-2/+1
|
* Catch up with bsd.lib.mk,v 1.143.ru2003-06-302-19/+0
|
* Add missing quote after cut/paste error in last commit. :-(peter2003-06-261-1/+1
|
* Update the target.obrien2003-06-265-15/+15
|
* Configure gcc in biarch mode for amd64 so that the -m32 flag is enabledpeter2003-06-261-2/+1
| | | | | | for things like boot blocks etc. Reviewed by: kan
* Oops, remove hack to stop libstdc++.so being built now that gcc usespeter2003-06-261-5/+0
| | | | -lgcc_pic by default on -fpic stuff. I forgot about this here.
* Add an amd64 category now that amd64 has its own mailing list and all.des2003-06-202-0/+4
|
* Remove MAINTAINER lines.obrien2003-06-141-4/+0
|
* Do not bogusly set CSTD to the empty string.des2003-06-142-2/+0
|
* When building a shared library, link it against libgcc_pic.a instead of thepeter2003-06-131-1/+2
| | | | | | | | | | | non-PIC libgcc.a. Linking non-pic code into a shared library is not a good thing. It happens to break amd64 at compile time, and the ppc folks want it too. The problem is mainly with C++ code, unwind-dw2.c in particular. Most of the other functions in libgcc.a are self contained so most of the time it isn't a problem. The dwarf2 unwinder is not safe though since it does make global variable references. Reviewed by: kan
* Build/install the PIC version of libgcc (libcc_pic.a) for use by sharedpeter2003-06-131-0/+3
| | | | libraries that do exception unwinding.
* Teach mdoc(7) about the upcoming 5.2-RELEASE.ru2003-06-091-0/+1
| | | | Suggested by: juli
* The .Fn functioncharnier2003-06-081-30/+60
|
* Usekuriyama2003-06-062-2/+2
| | | | | | | | | cat ${.ALLSRC} > ${.TARGET} rather than ln -sf ${.ALLSRC} ${.TARGET} not to depends on absolute-path of symbolic links. Commented by: marcel, obrien, bde
* Make the footer display "FreeBSD 5.1".ru2003-06-051-1/+1
|
* We have at least one consumer of the upcoming FreeBSD 4.9.ru2003-06-021-0/+1
|
* Something funky is going on here... disabling CSTD makes it go away...obrien2003-06-021-0/+1
|
* Don't set a C standard level for ObjC code.obrien2003-06-021-0/+1
|
* Use ?= before someone brings it up.obrien2003-06-021-1/+1
|
* crtstuff needs isn't compilable with C99 on Sparc64, so set CSTD to gnu89.obrien2003-06-011-0/+1
|
* Add a temporary indirect patch for gcc when targeting amd64. This is topeter2003-05-242-2/+67
| | | | | | | | | | | | | | | | | | | | | | give the cvs tree a surviving a 'make world'. One of the two diff chunks is already in gcc-3.3, the other has been committed to gcc's HEAD and is in the pipeline for gcc-3.3.1 (but has not been committed yet). The first chunk simplifies an excessively complex assembler statement when generating switch jump tables. The use of '.' causes as(1) to choke on big files. Use a simpler form instead. This is only an issue for TARGET_64BIT mode. The second chunk fixes an internal compiler error when compiling libc/stdio/vfprinf.c. While this is supposedly only an issue for 64 bit mode, it does touch the 32 bit i386 code paths, so this patch is only applied for TARGET_ARCH == amd64 to keep the risks down. Breaking gcc at the 11th hour would suck. This will be removed when it is time to import gcc-3.3. Discussed with: kan Approved by: re (jhb)
* libstdc++.so breaks on amd64 due to bogons in our build, so prevent thepeter2003-05-241-0/+5
| | | | | | | | | | | | | | shared library being built for amd64. The problem is that libstdc++.so is produced with 'cc -shared'. This has an internal -lgcc, which is not PIC. libstdc++.so uses exceptions and the dwarf2 unwinder, which are in libgcc.a. As a result, non-PIC code gets pulled into libstdc++.so. This is fatal on amd64 when certain relocation types cannot be used in PIC mode. The official FSF solution to this is to have libgcc.so with internal ELF symbol versioning to solve the ABI problem, but I dont want to fight that battle yet. I tried making libgcc_pic.a (which worked fine), but thats not something for the 11th hour before a release. Approved by: re (amd64 "safe" stuff)
* Set the binutils arch for as/nm correctly on the amd64 platform.peter2003-05-081-1/+6
| | | | | | | As far as binutils is concerned, the amd64 platform is still called "x86-64"/"x86_64". Setting things from ${MACHINE_ARCH} breaks that. Approved by: re (scottl)
* Enable GSSAPI/Kerberos 5 support (aka `gserver').nectar2003-05-051-9/+6
| | | | MFC after: 1 month
* Use __FBSDID over rcsid[].obrien2003-05-0332-80/+86
|
* This is WARNS=2 clean.obrien2003-05-031-0/+1
|
* Fix build on 4.x.ru2003-05-021-0/+4
|
* Re-enable building of Groff documentation; texinfo has just beenru2003-05-021-1/+0
| | | | upgraded to version 4.5.
* Update for texinfo 4.5.ru2003-05-021-1/+1
|
* catman(1) sources now live elsewhere.ru2003-05-013-579/+0
|
* Lock GCC w/o -m32 into 64-bit mode.obrien2003-05-011-0/+4
|
* Upgrade to Groff 1.19.ru2003-05-0131-86/+155
|
* Replace beforeinstall: with plain FILES.ru2003-04-301-7/+2
|
* Enable wchar_t support in libstdc++.kan2003-04-292-2/+2
|
* Wrap gperf in NO_CXX as it needs the C++ to compile.obrien2003-04-271-4/+3
|
* We're changing the platform name from x86[_-]86 to amd64.obrien2003-04-264-7/+7
|
* The AMD64 Hammer bits.obrien2003-04-269-1/+4430
|
* Remove first attempt at x86-64 bits. We're going to call it "amd64" now.obrien2003-04-267-4250/+0
| | | | Sponsored by: Microsoft
* Enable ISO-C99 compatibility -- among other things, this tells libstdc++obrien2003-04-252-9/+9
| | | | | | | not to blindly undef isnan() and other functions that became macros in C99. Enable use of newly grown C99 functions: strtof(), strtold(), wcstof() Submitted by: das
* Removed invasion into these makefiles by the "legacy" stuff;ru2003-04-1212-48/+36
| | | | I have a better fix in the works.
* libbinutils.a needs basename(3); when the latter is providedru2003-04-1112-36/+48
| | | | by -legacy, liblegacy.a should come last in the LDADD list.
* Migrate to a new way of dealing with building from old revisions ofimp2003-04-052-14/+1
| | | | | | | | | | | | | | | | | FreeBSD. This method attempts to centralize all the necessary hacks or work arounds in one of two places in the tree (src/Makefile.inc1 and src/tools/build). We build a small compatibility library (libbuild.a) as well as selectively installing necessary include files. We then include this directory when building host binaries. This removes all the past release compatibilty hacks from various places in the tree. We still build on tip of stable and current. I will work with those that want to support more, although I anticipate it will just work. Many thanks to ru@, obrien@ and jhb@ for providing valuable input at various stage of implementation, as well as for working together to positively effect a change for the better.
* Mark bits that do not require an object directory as such.ru2003-04-011-0/+2
|
* Document the MAIL_AGENT environment var.keramida2003-03-261-0/+13
| | | | | PR: 48277 Submitted by: Stefan Walter <sw@gegenunendlich.de>
* Attempt to automatically read in kernel module symbols when a liveiedowse2003-03-214-2/+330
| | | | | | | | | | | | | | | | | | | | | | | | or dead kernel core is loaded into gdb. This extends gdb's existing shared library support, so the "info sharedlibrary", "sharedlibrary" and "nosharedlibrary" commands can be used to view and change the list of loaded symbol files. The current implementation is more than a kludge however, and it will not always manage to find the .ko.debug file corresponding to the loaded module. In particular, for modules whose build directory cannot be easily guessed from the module name such as all the netgraph modules, the debug version of the .ko will not be found automatically. The logic for finding the module file first attempts to guess at the module build directory by parsing the version[] string. Then using that directory ($DIR), it tries the following paths in turn: ./<module>.ko.debug ./<module>.ko $DIR/<module>.ko.debug $DIR/<module>.ko /boot/kernel/<module>.ko.debug /boot/kernel/<module>.ko Approved by: obrien, mp
* Shorten the URL to the problem-reports article.des2003-03-181-1/+1
|
* Forced non-forced commit by adding a comment mentioning what themarcel2003-03-171-0/+1
| | | | | previous commit log should have mentioned: PR: ia64/49081
OpenPOWER on IntegriCloud