Note : the compile is fine without -funroll-loops
multi% gcc -v --save-temps -O -pipe -march=pentiumpro -Wall
-funroll-loops -fschedule-insns2 -DLIBC_RCS -DSYSLIBC_RCS
-I/files3/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6
-DPOSIX_MISTAKE -I/files3/src/lib/libc/../libc/locale
thanks for the responses!
"make" and "make install" worked fine with the newest port changes, but when
making the handbook jade dumped core at last. Memory consumption raised
to over 30 MByte before the core dump.
I made a mistake in the former posting as i tried to compile
jade-1.2.2.tar.gz
-On [19991201 23:30], Nik Clayton ([EMAIL PROTECTED]) wrote:
On Sun, Nov 28, 1999 at 05:38:57PM +0100, F. Heinrichmeyer wrote:
i tried to make me a new handbook, so i needed jade.
But the newest C++ fashion (g++ under current) has changed to fast for
this very old 1998 heavily template based
[ I've cc'd FreeBSD-doc on this, in case there's someone there who's solved
the problem you're having ]
On Sun, Nov 28, 1999 at 05:38:57PM +0100, F. Heinrichmeyer wrote:
i tried to make me a new handbook, so i needed jade.
But the newest C++ fashion (g++ under current) has changed to fast
I have just noticed that the new gcc breaks imake because
/usr/libexec/cpp doesn't define __FreeBSD__. What is the plan to
fix everything in this area? The 2 options I can see is to revert
the behaviour of cpp, or find everything that uses cpp and change
them to use cc -E.
My current "fix"
In article [EMAIL PROTECTED]
Brian Fundakowski Feldman [EMAIL PROTECTED] said:
1. /usr/libexec/cpp now has no predefined symbols like __FreeBSD__,
which makes imake unable to detect OS type automatically.
I'm certain XFree86 should build using gcc -E and not the C preprocessor
I'll be pulling the switch to use GCC 2.95.2 as the base compiler in
-CURRENT on Sunday evening (Freefall time).
It seems that currently after introduction of 2.95.2 world could not be
compiled with -jN option (complains about not being able to locate genrtl.h).
This patch make "
On Wed, 17 Nov 1999, Sheldon Hearn wrote:
XFree86 makes it through the ports ``build'' target just fine. It
breaks in ``install''. That's why I told Manfred I wasn't seeing the
problem.
I'd imagine the confusion is caused by the install target (improperly)
building things. Yet another
On Mon, 15 Nov 1999 13:22:23 PST, Manfred Antar wrote:
I did the same and everything works.
But XFree86 from the ports collection will not build.
That's not a very useful description of the problem. :-)
Did you answer "YES" or "NO" to the following question?
Do you want to compile
On Mon, 15 Nov 1999 13:22:23 PST, Manfred Antar wrote:
I did the same and everything works.
But XFree86 from the ports collection will not build.
By the way, I just tested the build using gcc-2.95.2 both with and
without the threads support. So you really are going to need to provide
more
On Tue, 16 Nov 1999 06:46:12 PST, Manfred Antar wrote:
Did it build for you ?
Yes.
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
At 04:50 PM 11/16/99 +0200, Sheldon Hearn wrote:
On Tue, 16 Nov 1999 06:46:12 PST, Manfred Antar wrote:
Did it build for you ?
Yes.
Ciao,
Sheldon.
Ok Sheldon here are some of the Errors I get when building XFee86 with the
new compiler
A few of these :
cc -c -O -I../..
At 05:14 PM 11/16/99 -0800, Manfred Antar wrote:
At 04:50 PM 11/16/99 +0200, Sheldon Hearn wrote:
On Tue, 16 Nov 1999 06:46:12 PST, Manfred Antar wrote:
Did it build for you ?
Yes.
Ciao,
Sheldon.
Ok Sheldon here are some of the Errors I get when building XFee86 with the
new compiler
A
On Tue, 16 Nov 1999, Manfred Antar wrote:
-DDEFAULT_CONFIG=\"/usr/
X11R6/lib/X11/rstart/config\" -DNOPUTENV server.c
server.c: In function `putenv':
server.c:790: argument `s' doesn't match prototype
/usr/include/stdlib.h:117: prototype declaration
*** Error code 1 (continuing)
There are
At 09:35 PM 11/16/99 -0500, Bill Fumerola wrote:
On Tue, 16 Nov 1999, Manfred Antar wrote:
-DDEFAULT_CONFIG=\"/usr/
X11R6/lib/X11/rstart/config\" -DNOPUTENV server.c
server.c: In function `putenv':
server.c:790: argument `s' doesn't match prototype
/usr/include/stdlib.h:117: prototype
On Tue, 16 Nov 1999, Manfred Antar wrote:
I think this is all related to the compiler update as I did a good
build Friday or
Saturday before the change.
If it is, then some thing wierd is going on.
--
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800)
At 09:50 PM 11/16/99 -0500, Bill Fumerola wrote:
On Tue, 16 Nov 1999, Manfred Antar wrote:
I think this is all related to the compiler update as I did a good
build Friday or
Saturday before the change.
If it is, then some thing wierd is going on.
Maybe it's something else, there might
On Tue, 16 Nov 1999, Manfred Antar wrote:
I think this is all related to the compiler update as I did a good
build Friday or
Saturday before the change.
If it is, then some thing wierd is going on.
Something weird is going on... I can confirm Manfred's claim, I also just
build
On Tue, 16 Nov 1999 20:15:17 PST, "Rodney W. Grimes" wrote:
Something weird is going on... I can confirm Manfred's claim, I also
just build XFree86 just before the compiler change. I'm certainly not
going to cvs update right now... :-)
Gentlemen, would you please use the right terminology
David O'Brien wrote:
I'll be pulling the switch to use GCC 2.95.2 as the base compiler in
-CURRENT on Sunday evening (Freefall time).
Those not-quite-so daring might want to hold off on your next make world.
*** NOTE *** that I have NOT changed the shared lib version for
libstc++.so
I just successfully compiled the world and the kernel (defaut
optimizations on everything) with gcc 2.95.2, and so far all is well :-)
=
| Kenneth Culver | FreeBSD: The best OS around.|
| Unix Systems
Same here, no problems.
_F
At 03:36 PM 11/15/99 -0500, Kenneth Wayne Culver wrote:
I just successfully compiled the world and the kernel (defaut
optimizations on everything) with gcc 2.95.2, and so far all is well :-)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fr
At 04:10 PM 11/15/99 -0500, Forrest Aldrich wrote:
Same here, no problems.
_F
At 03:36 PM 11/15/99 -0500, Kenneth Wayne Culver wrote:
I just successfully compiled the world and the kernel (defaut
optimizations on everything) with gcc 2.95.2, and so far all is well :-)
I did the same
Alright, it seems I have my first problem with gcc 2.95.2, (well, I'm not
really sure that it's a gcc problem). The problem is that now, after
having upgraded the compiler, fxtv will only display every other scanline
instead of all of them
# gcc --version
egcs-2.91.66
What is the relationship?
That is EGCS 1.1.2.
see http://egcs.cygnus.com/timeline.html
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I'll be pulling the switch to use GCC 2.95.2 as the base compiler in
-CURRENT on Sunday evening (Freefall time).
Those not-quite-so daring might want to hold off on your next make world.
*** NOTE *** that I have NOT changed the shared lib version for
libstc++.so (the rules disallow
This is just a "heads up" message, that the switch from EGCS 1.1.2 to
GCC 2.95.2 will probably occur this weekend. I can now `make world' and
build a GENERIC kernel fine with GCC 2.95.2.
All I have left to do is clean up some stuff and arrange some stuff.
--
-- David([EMAIL
I missed something, I think.
# gcc --version
egcs-2.91.66
What is the relationship?
tomdean
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 1999-Nov-09 05:01:43 +1100, Luoqi Chen wrote:
+ "=D" (addr), "=c" (count) :
+ "r" (bsh + offset), "0" (addr), "1" (count) :
+ "%eax", "memory");
You may use "+D" and "+c" for the in-out operands,
"+D"
"David O'Brien" writes:
On Sat, Nov 06, 1999 at 10:34:18AM +0100, Gary Jennejohn wrote:
Here's a patch to bus.h which works for both EGCS and GCC 2.95.2. I have
Here is the patch I've been working on (before I 1st got BDE's reply).
The changes are mostly from OpenBSD + style changes f
"Daniel C. Sobral" writes:
Gary Jennejohn wrote:
Any idea why GCC 2.95.2 produces so much more code ?
Mmmm... O'Brien, could you make sure the space-critical code in
sys/boot compiles ok?
I still have GCC 2.95.2 installed. This is what I get in /sys/boot:
=== i386/boot2
(cd /u
Gary Jennejohn wrote:
Mmmm... O'Brien, could you make sure the space-critical code in
sys/boot compiles ok?
I still have GCC 2.95.2 installed. This is what I get in /sys/boot:
=== i386/boot2
(cd /usr/src/sys/boot/i386/boot2; m4 -DFLAGS=0 boot1.m4 boot1.s) | as -o boot1.o
ld
On Sat, Nov 06, 1999 at 10:34:18AM +0100, Gary Jennejohn wrote:
Here's a patch to bus.h which works for both EGCS and GCC 2.95.2. I have
Here is the patch I've been working on (before I 1st got BDE's reply).
The changes are mostly from OpenBSD + style changes for the way we do
things. Can you
4
+#define RawCppCmd /usr/libexec/cpp /* -undef */
+#endif
+
#define HasTk YES
#define XF86SetupUsesStaticTk NO
With these two patches, I can successfully build/install XFree86 with
gcc-2.95.2.
Hope it helps,
--
さねを URL:mailto:[EMAIL PROTECTED]
To Unsubscribe
On Sat, 20 Nov 1999, SANETO Takanori wrote:
After some investigation, I found that following reasons (both cpp
related) caused the failure of build/installing XFree86:
1. /usr/libexec/cpp now has no predefined symbols like __FreeBSD__,
which makes imake unable to detect OS type
Bruce Evans writes:
On Fri, 5 Nov 1999, David O'Brien wrote:
The current show stopper for switching over to GCC 2.95.2 is a problem
compiling the `ahc' driver:
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
Hi all,
I've got GCC 2.95.2 working as the base compiler. It is still a little
rough, but I wanted to put it in more hands for testing.
My Alpha is booting from a GENERIC kernel and world built from gcc
2.95.2. This is one compiler bug in building libreadline, but I have a
hack around
David O'Brien wrote:
I've got GCC 2.95.2 working as the base compiler. It is still a little
rough, but I wanted to put it in more hands for testing.
If it doesn't interfere with my current work, then I'll get to it ASAP.
I already have some fixes for the current binutils and egcs WRT
The current show stopper for switching over to GCC 2.95.2 is a problem
compiling the `ahc' driver:
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I
On Friday, 5 November 1999 at 14:04:15 -0800, David O'Brien wrote:
The current show stopper for switching over to GCC 2.95.2 is a problem
compiling the `ahc' driver:
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
40 matches
Mail list logo
