Maelstrom

SDL Development
1

Sam, what version of gcc did you compile the Maelstrom binaries with?
I tried to compile with gcc 2.95.2 and it hits a bug in gcc. While
you’re at it what version of glib are you using cuz mine is kinda old.
I’m pretty sure it’s a problem on my end, so I just want to see what
I need to update.

Phoenix Kokido
members.xoom.com/kokido
@Wes_Poole

2

SDL and Maelsrom are great!! I’m not sure how I missed all of this
happening until now.

I compiled Malestrom and SDL with 2.95.1 and both work fine. glib is
real current (the recent redhat errata).

Phoenix Kokido wrote:>

Sam, what version of gcc did you compile the Maelstrom binaries with?
I tried to compile with gcc 2.95.2 and it hits a bug in gcc. While
you’re at it what version of glib are you using cuz mine is kinda old.
I’m pretty sure it’s a problem on my end, so I just want to see what
I need to update.

Phoenix Kokido
members.xoom.com/kokido
kokido at postmark.net

3

Well when I try to compile it with GCC 2.95.2 and glibc 2.0.7 I get:

*snip out stuff that worked *

make.cpp: In function ‘void MakeMultiplier()’:
make.cpp:93: Internal compiler error.
make.cpp:93: Please submit a full bug report to
’egcs-bugs at cygnus.com’.
make[1]: *** [make.o] Error 1
make: *** [all-recursive] Error 1

This is the only thing I’ve ever had problems with gcc compiling.

Phoenix Kokido
members.xoom.com/kokido
@Wes_Poole

Philip Long wrote:> SDL and Maelsrom are great!! I’m not sure how I missed all of this

happening until now.

I compiled Malestrom and SDL with 2.95.1 and both work fine. glib is
real current (the recent redhat errata).

Phoenix Kokido wrote:

Sam, what version of gcc did you compile the Maelstrom binaries with?
I tried to compile with gcc 2.95.2 and it hits a bug in gcc. While
you’re at it what version of glib are you using cuz mine is kinda old.
I’m pretty sure it’s a problem on my end, so I just want to see what
I need to update.

Phoenix Kokido
members.xoom.com/kokido
@Wes_Poole

4

Internal compiler errors are always a compiler bug. Please submit
enough source so that the compiler guys can reproduce the bug and squash
it.

Phoenix Kokido wrote:>

Well when I try to compile it with GCC 2.95.2 and glibc 2.0.7 I get:

*snip out stuff that worked *

make.cpp: In function ‘void MakeMultiplier()’:
make.cpp:93: Internal compiler error.
make.cpp:93: Please submit a full bug report to
’egcs-bugs at cygnus.com’.
make[1]: *** [make.o] Error 1
make: *** [all-recursive] Error 1

This is the only thing I’ve ever had problems with gcc compiling.

5

I knew it was a compiler bug, I just wanted to know if Sam had
successfully compiled it with 2.95.2 because I was running so low on
disk space when I built mine that it may have caused my build to go
sour.

Phoenix Kokido
members.xoom.com/kokido
@Wes_Poole

Philip Long wrote:> Internal compiler errors are always a compiler bug. Please submit

enough source so that the compiler guys can reproduce the bug and squash
it.

Phoenix Kokido wrote:

Well when I try to compile it with GCC 2.95.2 and glibc 2.0.7 I get:

*snip out stuff that worked *

make.cpp: In function ‘void MakeMultiplier()’:
make.cpp:93: Internal compiler error.
make.cpp:93: Please submit a full bug report to
’egcs-bugs at cygnus.com’.
make[1]: *** [make.o] Error 1
make: *** [all-recursive] Error 1

This is the only thing I’ve ever had problems with gcc compiling.

6

I’ve seen internal compiler errors be caused by hardware problems as well.
For example, overclocking a computer, bad memory, or a CPU fan going out
can all cause gcc to produce such an error.

Given, it wouldn’t just happen when compiling Maelstrom.–
Brian

On Wed, 8 Dec 1999, Philip Long wrote:

Internal compiler errors are always a compiler bug. Please submit
enough source so that the compiler guys can reproduce the bug and squash
it.

Phoenix Kokido wrote:

Well when I try to compile it with GCC 2.95.2 and glibc 2.0.7 I get:

*snip out stuff that worked *

make.cpp: In function ‘void MakeMultiplier()’:
make.cpp:93: Internal compiler error.
make.cpp:93: Please submit a full bug report to
’egcs-bugs at cygnus.com’.
make[1]: *** [make.o] Error 1
make: *** [all-recursive] Error 1

This is the only thing I’ve ever had problems with gcc compiling.

7

I’ve seen internal compiler errors be caused by hardware problems as well.
For example, overclocking a computer, bad memory, or a CPU fan going out
can all cause gcc to produce such an error.

This particular problem is a bug in some versions of egcs.

-Sam Lantinga				(slouken at devolution.com)

Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec