Re: [Quickfix-developers] Linux Compile Problems - QF1.8.0
Brought to you by:
orenmnero
From: James W. <wi...@wi...> - 2004-08-23 00:49:28
|
Hello Joerg, Many thanks for the reply! On Sun, 2004-08-22 at 17:03, Joerg Thoennes wrote: > QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/i= ndex.html > QuickFIX FAQ: http://www.quickfixengine.org/wikifix/index.php?QuickFixFAQ > QuickFIX Support: http://www.quickfixengine.org/services.html >=20 > Hi James, >=20 > > I am attempting to build QuickFIX 1.8.0 on a Linux box, Debian > > Stable, fully up-to-date. I have installed the latest stable version > > of STLPort. I get compiler errors when compiling with either gcc 2.95 > > or gcc 3.04, the only two stock compilers available for Debian stable. > > I am willing to upgrade the machine to Debian Sarge, which will be the > > new stable within a few months, but do *not* want to go down that road > > if it won't solve the problem. I am testing a build on one of our > > workstations, which run Debian unstable (i.e. SID). The compile has > > not completed yet, but if it does, I'll at least know that gcc 3.3.4 > > will work. > >=20 > > So, the question: what versions of GCC have been used successfully > > to build 1.8.0 on a Linux machine? The errors I've been getting are > > actual internal compiler errors, complete with a request to send a bug > > report to GNU, not library or linking errors. Neither are they out of > > memory errors; there's plenty of RAM on the box. >=20 > I did compile 1.8.0 both on Debian stable (woody) and testing (sarge)=20 > without any problems. Which kind of problems do you have? >=20 > Cheers, J=F6rg I eventually gave up and upgraded one of our servers to Debian Sarge; I was able to get it to compile on my Sid workstation, which is running gcc/g++ 3.3.4-7, and Sarge installs with 3.3.4-3, so I figured it was worth a try. After a few attempts, I was finally able to get it to compile with the STLPorts 4.6 package that comes with Sarge and the MySQL library we have installed. It fails two unit tests, however. It passes all acceptance tests. I did not save out the compiler errors I got. They weren't seg faults or out-of-memory errors. One as I recall, came back as a floating point exception (?!). I'm trying to compile it again on one of our other Woody boxes to see if I can get the error for you again. So far, it's 39 minutes(!) into the compile of Session.cpp, using 384 MB of RAM. Unbelievable. Whenever the build dies, I'll send along the error messages. On a related note, how seriously is Linux *really* supported by the core QuickFIX group? Having to install a whole new version of the operating system just to get QF to compile doesn't instill a lot of confidence. I've got a *very* basic application I'm trying to get running with it, and I can't even get a SocketInitiator to instantiate properly. The code segfaults when I try to do it. I'm drafting a note on that problem separately. Am I unique in having so much trouble with QF? Most of the mailing list messages seem to be from Solaris or Windows developers coding in Java or .NET or VB. How many people are you aware of who are successfully using QF on Linux, coding in C/C++? thanks, Jim Wiggs |