PDA

View Full Version : Error compiling SEQ 5



Onimusha
12-08-2003, 10:41 AM
SuSE Linux 8.2
autoconf (GNU Autoconf) 2.57
linux:~/showeq # gcc -v
Reading specs from /usr/lib/gcc-lib/i486-suse-linux/3.3/specs
Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --enable-languages=c,c++,f77,objc,java,ada --disable-checking --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i486-suse-linux
Thread model: posix
gcc version 3.3 20030226 (prerelease) (SuSE Linux)



if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/lib/qt3/include -I/usr/X11R6/include -DPKGDATADIR=\"/usr/local/share/showeq/\" -I/usr/include/pcap -D_REENTRANT -O2 -Wall -g -ggdb -DDEBUG -finline-functions -DQT_THREAD_SUPPORT=1 -DDISPLAY_ICONS=false -DICON_DIR=\"/eq-icons/\" -MT interface.o -MD -MP -MF ".deps/interface.Tpo" \
-c -o interface.o `test -f 'interface.cpp' || echo './'`interface.cpp; \
then mv ".deps/interface.Tpo" ".deps/interface.Po"; \
else rm -f ".deps/interface.Tpo"; exit 1; \
fi
interface.cpp: In member function `void EQInterface::enableAllTypeFilters()':
interface.cpp:4650: error: integer constant is too large for "long" type
make[3]: *** [interface.o] Error 1
make[3]: Leaving directory `/root/showeq/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/root/showeq/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/showeq'
make: *** [all] Error 2

Talorn
12-12-2003, 08:26 PM
just wanted to confirm that I had this same problem. It comes up with about 4 or 5 other files in src/. I just changed

0xFFFFFFFFFFFFFFFF
to
0xFFFFFFFF

works for now.

-talorn

Zaphod
12-12-2003, 09:31 PM
Originally posted by Talorn
just wanted to confirm that I had this same problem. It comes up with about 4 or 5 other files in src/. I just changed

0xFFFFFFFFFFFFFFFF
to
0xFFFFFFFF

works for now.

-talorn

I don't normally do this, but... Iif you or Onimusha used http://seq.sourceforge.net/forums/images/top_search.gif (http://seq.sourceforge.net/forums/search.php?s=) you would have found that the correct solution to work around the bug in gcc 3.3.x is to change:

0xFFFFFFFFFFFFFFFF
to
0xFFFFFFFFFFFFFFFFULL

Mistakenly setting it to the incorrect value of 0xFFFFFFFF
will lead to incorrect behaviour.

This was discussed and solved not 8 posts away from this one.

Enjoy,
Zaphod (dohpaZ)

Onimusha
12-15-2003, 11:54 PM
Originally posted by Zaphod
I don't normally do this, but... Iif you or Onimusha used http://seq.sourceforge.net/forums/images/top_search.gif (http://seq.sourceforge.net/forums/search.php?s=) you would have found that the correct solution to work around the bug in gcc 3.3.x is to change:

0xFFFFFFFFFFFFFFFF
to
0xFFFFFFFFFFFFFFFFULL

Mistakenly setting it to the incorrect value of 0xFFFFFFFF
will lead to incorrect behaviour.

This was discussed and solved not 8 posts away from this one.

Enjoy,
Zaphod (dohpaZ)

I posted this a day before that fix was posted on another thread. Also note that I posted the bug 6 hours before K_S_R posted the same bug. I posted this in a different thread because it was a different error than ieatacid was having. Nothing against you Zaphod, you do great work for no glory or compensation. Just dont like being burned when I havent done anything to be burned about :). In all my years of using this software (going as farback as when it was on hackersquest.org) this was the first time I have had a problem getting it compiled.

S_B_R
12-16-2003, 08:44 AM
In Zaphod's defense I'm pretty sure he was responding to the post by Talorn. Since Zaphod quotes Talorn's post, I don't think he was directing his comments toward you.;)