Well, I was able to build it on -CURRENT, along with binutils
and other fine software from -STABLE tree. The reason was that
in several cases GCC 3.2.1 proved to be significantly slower
than 2.95.4 (I mean regular integer\floating-point operations,
MMX\SSE\3DNow! is a whole different story). I repl
FreeBSD is a free software. You have no right to make any claims
or force developers to do something to fit your needs (did you
read BSD license?). If it's used to work fine but currently broken,
it will be fixed. Also you're always welcome to fix it yourself.
By installing -CURRENT, you agree that
Hello gentlemen,
the question is, why param.h (v1.65) that comes with 5.0
doesn't define OBJFORMAT_NAMES and OBJFORMAT_DEFAULT, but
v1.54 does? These are required by GCC 2.95.4 at compile-time
(pulled from -STABLE). It may look like someone had decided
that GCC2 is of no use in -CURRENT...
---
Re
Bruce Cran wrote:
> I'm afraid you're wrong - the V2SI datatype and MMX functions
> automatically become available after -march=pentium2, while
> with other processor types you've got to explicitly add -mmmx.
> -msse is presumed with -march=pentium3 and up.
I'm afraid I'm not; I was talking strictl
Nuno Teixeira wrote:
>
> Hi,
>
> Just a little question:
>
> Does -march=k6-2 implies -m3dnow? Or -march=pentiumpro implies -mmmx?
Pentium Pro doesn't support MMX; -march=pentiumpro (aka -march=i686) enables
compiling with main i686 instruction set, no MMX\SSE or whatever.
>
> I always thought
"Paul A. Howes" wrote:
>
> All;
>
> These two kernel options seem to have solved the problem. Builds now
> run smoothly and error-free. I read the comments in NOTES about these
> options and something clicked: I recall that most Pentium processors
> will only deal with 4 kB pages. Aren't 4 MB
Scott Long wrote:
>
> Rhett Monteg Hollander wrote:
>
> > Hello gentlemen,
> >
> > several days ago I've installed 5.0-RELEASE onto
one
> > of my machines, which already carried 4.7-RC1. To
> > avoid possible compatibility problems, I did a
clean
&g
Hello gentlemen,
several days ago I've installed 5.0-RELEASE onto one
of my machines, which already carried 4.7-RC1. To
avoid possible compatibility problems, I did a clean
install onto another hard drive, and later recompiled
everything. Here I have a couple of annoying issues.
Shell refuses to
