| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Desired by: ru
|
| |
|
|
|
|
| |
We can't use straight "c99" due to the lack of alloca.S for non-i386 platforms.
|
| |
|
| |
|
| |
|
|
|
|
| |
*sigh* Just can't get a brake when trying to react too quickly and fix the build.
|
|
|
|
| |
I swore this made it thru a 'make world', but I don't know what happened.
|
|
|
|
| |
Also allow for "CSTD=" in a Makefile.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
known to produce broken code with -march=pentium4. Add a note explaining this.
This should be removed when we update to gcc 3.3 or the bug is otherwise fixed.
Approved by: re
|
|
|
|
|
|
| |
PR: misc/52486
Submitted by: "Simon L. Nielsen" <simon@nitro.dk>
Approved by: re (jhb)
|
|
|
|
|
| |
Noticed by: ru
Approved by: re (amd64-specific low risk stuff)
|
|
|
|
|
|
| |
PR: 35652
Submitted by: "Simon L. Nielsen" <simon@nitro.dk> (original version)
Approved by: re (bmah)
|
| |
|
| |
|
|
|
|
|
| |
cleanups were necessary in release/Makefile, and the tinderbox code
was syntax checked, not run checked.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in which the source code is written. This is controlled by the CSTD
variable, which can have one of the following values:
- "k&r" => -traditional
- "c89" or "c90" => -std=iso9899:1990
- "c94" or "c95" => -std=iso9899:199409
- "c99" => -std=iso9899:1999
The corresponding option is added to CFLAGS regardless of WARNS level.
This also removes -ansi from WARNS level 6, but adds -Wno-long-long to
work around a weird gcc bug (-ansi, which is supposedly equivalent to
-std=iso9899:1990, seems to turn long long warnings off instead of on)
If CSTD is undefined, CFLAGS are unchanged except for the -ansi /
-Wno-long-long change mentioned above for WARNS level 6.
|
|
|
|
| |
If one is using NOSHARED, why build the libs.
|
|
|
|
| |
Reviewed by: bde
|
|
|
|
|
| |
PR: 50801
Submitted by: Glenn Johnson <glennpj@charter.net>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
-Wuninitialized does not work without -O.
This fixes the ${WARNS} > 4 compilations with -O0.
Spotted by: marcel
|
|
|
|
|
|
| |
glibc which is externally maintained, so GCC ships with these
warnings turned off by default. This is also consistent with
the src/contrib/gcc/c-lex.c,v 1.2 change.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
for installkernel to wipe them out later. So install them under
/boot/modules if that is the case.
|
|
|
|
|
|
| |
get rid of bsd.kern.mk completely.
OK'ed by: bde
|
|
|
|
|
|
|
|
|
| |
Always use sys/conf/kern.mk when building kernel/modules.
<bsd.kern.mk> is only preserved for sys/boot/pc98/boot2
for now, but this will be fixed. If there are other
users of <bsd.kern.mk>, please let me know.
Reminded by: bde
|
|
|
|
|
| |
- Moved special compiler flags to bsd.kern.mk so they get used for modules
too.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
for the -static flag instead when constructing LIBPAM.
(This fixes false warnings from ``make checkdpadd -DNOSHARED'' in
lib/libpam/modules/.)
Submitted by: bde, ru
Approved by: re
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't gratuitously pipe thru a cat(1) if NODOCCOMPRESS.
Only create _stamp.extra when necessary.
Get rid of SOELIMPP and OBJS.
Use Groff version of soelim(1); we need its -I option
for the following to work.
Don't needlessly chdir to SRCDIR. Only a few documents
need CD_HACK, and those that need it either use refer(1)
or .PSPIC macro which internally uses the .psbb call.
|
|
|
|
| |
in /usr/share/tmac/troffrc pending the issue resolution on -arch.
|
|
|
|
|
|
|
|
| |
to creating the tags file using ctags(1). Defaults to "gtags".
Made GTAGSFLAGS and HTAGSFLAGS overrideable, added CTAGSFLAGS.
Folded bsd.prog.mk version of `tags' into bsd.dep.mk.
PR: bin/42852
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix the "@gprel relocation against dynamic symbol xxx" linker error.
Variables defined in the link unit and small enough to be put in the
short data section will have a gp-relative access sequence (using the
@gprel relocation). It is invalid to have @gprel relocations in shared
libraries, because they are to be resolved by the static linker and
not the dynamic linker. The -fpic option will cause @ltoff relocations
for @gprel relocations, but the side-effects are untested (if any).
Instead, disable/eliminate the short data section to achieve the same.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In "nroff" mode, italic font renders as an underlined text, which
makes it indistinguishable from the bold text on color monitors
(cons25 terminal type), yet it requires the less(1)'s -R option.
(Refer to the new grotty(1) manpage for details.)
So turn off the color support for now (when generating catpages),
until we figure out what do we do with this new feature. I have
a patch for grotty(1) that tells it to use the "reverse video"
attribute to render the italic font. Once this is accepted, we
can turn color support back on (if there won't be any objections
from the community).
|
| |
|