quickfix-developers — QuickFIX developers forum

Re: [Quickfix-developers] QuickFix FailOver/Farming Support.

[Oren M. <or...@qu...>]

Ok, I see why the reasoning for the second interface.  Since refresh support 
is being added to quickfix that can probably be consolidated into a single 
interface for future versions.

I don't really see why the no-op results in incorrect runtime behavior.  My 
view of the method is that it sets the state of the session to the persisted 
state.  In the case of the memory store, it is persisted into memory.  I 
could copy the state in memory from one place to another, it just happens 
that a no-op is a more efficient implementation.  I don't really see it any 
different than if I refreshed against a database with store that is already 
in sync with the database.  Nothing has changed (state wise), so it 
essentially acted like a no-op memory store refresh, but the end result is 
correct since the state of the session is correct.

As to the name, I had always seen the settings as sitting in the [SESSION] 
section.  So I never thought that the settings required additional 
clarification any more then methods on the Session class are prefixed with 
Session.  Pretty much every setting is like this.  StartTime, EndTime, 
ConnectionType, ReconnectInterval etc. etc.  None of these settings 
explicitly state they are session settings, but that is implied by the name 
of the section.

--oren

----- Original Message ----- 
From: "Steve Bate" <sb...@sm...>
Cc: <qui...@li...>; 
<qui...@li...>
Sent: Monday, May 29, 2006 12:50 AM
Subject: RE: [Quickfix-developers] QuickFix FailOver/Farming Support.


QuickFIX Documentation: 
http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html

Hi Oren,

I derived an interface because I couldn't add methods to existing
JNI interfaces without breaking API compatibility. If anybody had
implemented custom message stores those would be broken when they
migrated to QuickFIX/J.

I prefer providing user feedback instead of implementing
the operation as a no-op if the user has requested a refresh at
logon time and the message store they are using doesn't support
refresh. If we changed the MessageStore interface we could add
a predicate isRefreshable(), but I'm still a little uncomfortable
with a no-op operation when it results in incorrect runtime
behavior.

For the option name, I prefer more descriptive names.
RefreshOnLogon is a bit vague (refresh what?) but
RefreshSessionOnLogon would be fine and less implementation
oriented. However, I don't have a big issue with the
shorter name.

Steve

> -----Original Message-----
> From: Oren Miller [mailto:or...@qu...]
> Sent: Sunday, May 28, 2006 11:32 AM
> To: Steve Bate
> Cc: qui...@li...;
> qui...@li...
> Subject: Re: [Quickfix-developers] QuickFix FailOver/Farming Support.
>
> Steve,
>
> Can you explain the rational for implementing this as another
> interface.  It seems you are using reflection to determine if the
> interface implements RefreshableMessageStore or MessageStore.  If it
> is, it does a downcast to RefreshableMessageStore and calls refresh,
> if not it says that refresh is not supported.  Why wouldn't refresh
> be on the MessageStore interface, and if the store doesn't require
> any action to refresh (in this case since the state is in memory and
> is therefore always up to date), implement it as a no-op?
>
> --oren
>
> On May 28, 2006, at 2:09 AM, Steve Bate wrote:
>
> > Hi Phil,
> >
> > This feature is in QuickFIX/J. There is a RefreshableMessageStore
> > interface that provides the methods for refreshing the store and
> > marks which stores can be refreshed (MemoryStore can't, for
> > example). The Session can be configured to refresh it's state at
> > logon if a refreshable store is being used (see the
> > "RefreshMessageStoreAtLogon" configuration option). This
> might give
> > you some ideas how to modify the C++ code in a similar way.
> >
> > Regards,
> >
> > Steve
> >
> > From: qui...@li...
> > [mailto:qui...@li...] On Behalf
> > Of pc redev
> > Sent: Friday, May 26, 2006 6:07 PM
> > To: Oren Miller; qui...@li...
> > Subject: Re: [Quickfix-developers] QuickFix
> FailOver/Farming Support.
> >
> > Oren,
> >
> > From looking at the source looks like "revert" would
> propbably just
> > call "populateCache()" on the message store's.  Not sure where
> > abouts in logon is the safest place to call this.
> >
> > What is the possibility of this being available in a future
> > release?  I'd prefer not to change the code for my system as
> > creates issues with Fix Fixengine releases.
> >
> > Also is there a way I can simulate this behaviour without changing
> > the "FixEngineCode".  Is it possible to make the session
> "recreate"
> > on the logon event, which would also have the same effect?
>  In the
> > worst case I could expose the "PopulateCache" as a public method,
> > and call this on the "OnLogon", however I suspect this is too late
> > as you will have already started using the sequence number.   Any
> > ideas on workaround would be appreciated.
> >
> > Thanks
> > Phil.
> >
> > Oren Miller <or...@qu...> wrote:
> > To do this we would need some sort of revert method on the
> > MessageStore interface which would revert to the persisted state.
> > This could then be called by a session when receiving a logon.  It
> > actually might be a useful thing to do in all logon
> situations.  It
> > also gives us the ability to modify sequence numbers and such
> > without having to restart the engine.
> >
> > --oren
> > ----- Original Message -----
> > From: pc redev
> > To: qui...@li...
> > Sent: Thursday, May 25, 2006 2:08 PM
> > Subject: [Quickfix-developers] QuickFix FailOver/Farming Support.
> >
> > Hi,
> >
> > I have a QuickFixEngine connected to a "Clustered" MS SQL Server
> > backend, running fine.  I would like to be-able to provider
> > "FailOver/Farming" support like:
> >
> > Primary Machine:  Fix Engine Running Serving Active Clients
> > Secondary Machine: Fix Engine Running in No client connections.
> >
> > Both Fix Engines are connected to the clustered SQL Server for the
> > message store.
> >
> > If I "pull the plug" on A, clients are disconnected and connect to
> > "secondary", which in theory when they connect we pick up the
> > session from where it left off.
> >
> > The problem is the "Secondary" quick fix engine does not know to
> > "re-read" the clients "Sessions" when they connect, it
> appears that
> > this is performed when the "Fix Engine Starts Up" probably during
> > the create session.
> >
> > My only solution at the moment would be to have the
> "Secondary" fix
> > engine start on failover, i.e cold standby, which is not ideal.
> >
> > In the Fix Engine logic is it possible to "detect" a client socket
> > connect and force a "re-read" of session information from the
> > message store  cleanly with no side effects?   I'd prefer not to
> > change the Fix engine source code.
> >
> > Any info would be appreciated.
> >
> > Regards
> >
> > Phil.
> > Copy addresses and emails from any email account to Yahoo! Mail -
> > quick, easy and free. Do it now...
> >
> >
> > Try the all-new Yahoo! Mail . "The New Version is radically easier
> > to use" - The Wall Street Journal
> >
>
>


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=k&kid7521&bid$8729&dat1642
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

RE: [Quickfix-developers] ThreadedSocketInitiator vs SocketInitiator

[Steve B. <sb...@sm...>]

Hi Sean,

One complication of a thread pool approach is that we must be
sure that the messages for each session are processed in sequence.
We can't just dispatch each received message to a thread in the=20
pool. One solution is to maintain a queue for each session and=20
then dispatch the queues to a thread pool. The worker threads=20
would process one or more messages (could be configurable)=20
each time they take a session queue for processing.

Do you have any other ideas how to implement an thread pool
initiator/acceptor? Do any of the threading experts out there
know of an applicable pattern for this scenario?

Steve

> -----Original Message-----
> From: qui...@li...=20
> [mailto:qui...@li...] On=20
> Behalf Of Sean Kirkpatrick
> Sent: Friday, May 12, 2006 11:00 PM
> To: Oren Miller; Brian Erst; Caleb Epstein; Nick Volpe
> Cc: quickfix-developers
> Subject: RE: [Quickfix-developers] ThreadedSocketInitiator vs=20
> SocketInitiator
>=20
> QuickFIX Documentation:=20
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>=20
> May I suggest that there also be a thread pool option?  If an=20
> acceptor has hundreds of sessions configured, it won't be a=20
> good idea to spawn a thread per session...
>=20
> --Sean
>=20
> -----Original Message-----
> From: qui...@li...
> [mailto:qui...@li...]On=20
> Behalf Of Oren Miller
> Sent: Wednesday, May 10, 2006 12:56 PM
> To: Brian Erst; Caleb Epstein; Nick Volpe
> Cc: quickfix-developers
> Subject: Re: [Quickfix-developers] ThreadedSocketInitiator vs=20
> SocketInitiator
>=20
>=20
> QuickFIX Documentation:=20
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>=20
> There was, however it was overrun by WikiSpam and I never got=20
> around to researching solutions to the problem.
>=20
> --oren
>=20
> > p.s. Speaking of confusion, is there a QuickFIX wiki? While the=20
> > existing documentation is sufficient for getting started,=20
> in order to=20
> > really understand a lot of QF you have to read the mailing list=20
> > archives. If we had a wiki, I'd be tempted to transfer at=20
> least some=20
> > of the mailing list knowledge to the wiki, if only from an=20
> ongoing basis.
>=20
>=20
>=20
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web=20
> services, security?
> Get stuff done quickly with pre-integrated technology to make=20
> your job easier Download IBM WebSphere Application Server=20
> v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&
> dat=3D121642
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>=20
>=20
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web=20
> services, security?
> Get stuff done quickly with pre-integrated technology to make=20
> your job easier Download IBM WebSphere Application Server=20
> v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=120709&bid&3057&dat=121642
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>=20

RE: [Quickfix-developers] QuickFix FailOver/Farming Support.

[Steve B. <sb...@sm...>]

Hi Oren,

I derived an interface because I couldn't add methods to existing=20
JNI interfaces without breaking API compatibility. If anybody had=20
implemented custom message stores those would be broken when they=20
migrated to QuickFIX/J.

I prefer providing user feedback instead of implementing
the operation as a no-op if the user has requested a refresh at=20
logon time and the message store they are using doesn't support=20
refresh. If we changed the MessageStore interface we could add
a predicate isRefreshable(), but I'm still a little uncomfortable
with a no-op operation when it results in incorrect runtime=20
behavior.

For the option name, I prefer more descriptive names.=20
RefreshOnLogon is a bit vague (refresh what?) but=20
RefreshSessionOnLogon would be fine and less implementation
oriented. However, I don't have a big issue with the
shorter name.

Steve

> -----Original Message-----
> From: Oren Miller [mailto:or...@qu...]=20
> Sent: Sunday, May 28, 2006 11:32 AM
> To: Steve Bate
> Cc: qui...@li...;=20
> qui...@li...
> Subject: Re: [Quickfix-developers] QuickFix FailOver/Farming Support.
>=20
> Steve,
>=20
> Can you explain the rational for implementing this as another =20
> interface.  It seems you are using reflection to determine if the =20
> interface implements RefreshableMessageStore or MessageStore.  If it =20
> is, it does a downcast to RefreshableMessageStore and calls refresh, =20
> if not it says that refresh is not supported.  Why wouldn't refresh =20
> be on the MessageStore interface, and if the store doesn't require =20
> any action to refresh (in this case since the state is in memory and =20
> is therefore always up to date), implement it as a no-op?
>=20
> --oren
>=20
> On May 28, 2006, at 2:09 AM, Steve Bate wrote:
>=20
> > Hi Phil,
> >
> > This feature is in QuickFIX/J. There is a RefreshableMessageStore =20
> > interface that provides the methods for refreshing the store and =20
> > marks which stores can be refreshed (MemoryStore can't, for =20
> > example). The Session can be configured to refresh it's state at =20
> > logon if a refreshable store is being used (see the =20
> > "RefreshMessageStoreAtLogon" configuration option). This=20
> might give =20
> > you some ideas how to modify the C++ code in a similar way.
> >
> > Regards,
> >
> > Steve
> >
> > From: qui...@li... =20
> > [mailto:qui...@li...] On Behalf =20
> > Of pc redev
> > Sent: Friday, May 26, 2006 6:07 PM
> > To: Oren Miller; qui...@li...
> > Subject: Re: [Quickfix-developers] QuickFix=20
> FailOver/Farming Support.
> >
> > Oren,
> >
> > From looking at the source looks like "revert" would=20
> propbably just =20
> > call "populateCache()" on the message store's.  Not sure where =20
> > abouts in logon is the safest place to call this.
> >
> > What is the possibility of this being available in a future =20
> > release?  I'd prefer not to change the code for my system as =20
> > creates issues with Fix Fixengine releases.
> >
> > Also is there a way I can simulate this behaviour without changing =20
> > the "FixEngineCode".  Is it possible to make the session=20
> "recreate" =20
> > on the logon event, which would also have the same effect? =20
>  In the =20
> > worst case I could expose the "PopulateCache" as a public method, =20
> > and call this on the "OnLogon", however I suspect this is too late =20
> > as you will have already started using the sequence number.   Any =20
> > ideas on workaround would be appreciated.
> >
> > Thanks
> > Phil.
> >
> > Oren Miller <or...@qu...> wrote:
> > To do this we would need some sort of revert method on the =20
> > MessageStore interface which would revert to the persisted state.  =20
> > This could then be called by a session when receiving a logon.  It =20
> > actually might be a useful thing to do in all logon=20
> situations.  It =20
> > also gives us the ability to modify sequence numbers and such =20
> > without having to restart the engine.
> >
> > --oren
> > ----- Original Message -----
> > From: pc redev
> > To: qui...@li...
> > Sent: Thursday, May 25, 2006 2:08 PM
> > Subject: [Quickfix-developers] QuickFix FailOver/Farming Support.
> >
> > Hi,
> >
> > I have a QuickFixEngine connected to a "Clustered" MS SQL Server =20
> > backend, running fine.  I would like to be-able to provider =20
> > "FailOver/Farming" support like:
> >
> > Primary Machine:  Fix Engine Running Serving Active Clients
> > Secondary Machine: Fix Engine Running in No client connections.
> >
> > Both Fix Engines are connected to the clustered SQL Server for the =20
> > message store.
> >
> > If I "pull the plug" on A, clients are disconnected and connect to =20
> > "secondary", which in theory when they connect we pick up the =20
> > session from where it left off.
> >
> > The problem is the "Secondary" quick fix engine does not know to =20
> > "re-read" the clients "Sessions" when they connect, it=20
> appears that =20
> > this is performed when the "Fix Engine Starts Up" probably during =20
> > the create session.
> >
> > My only solution at the moment would be to have the=20
> "Secondary" fix =20
> > engine start on failover, i.e cold standby, which is not ideal.
> >
> > In the Fix Engine logic is it possible to "detect" a client socket =20
> > connect and force a "re-read" of session information from the =20
> > message store  cleanly with no side effects?   I'd prefer not to =20
> > change the Fix engine source code.
> >
> > Any info would be appreciated.
> >
> > Regards
> >
> > Phil.
> > Copy addresses and emails from any email account to Yahoo! Mail - =20
> > quick, easy and free. Do it now...
> >
> >
> > Try the all-new Yahoo! Mail . "The New Version is radically easier =20
> > to use" - The Wall Street Journal
> >
>=20
>=20

Re: [Quickfix-developers] QuickFix FailOver/Farming Support.

[Oren M. <or...@qu...>]

Hi Steve,

One more comment.  I was thinking that simply RefreshOnLogon would be =20=

a better name for the setting.  It is more consistent with the reset =20
configuration settings already in place "ResetOnLogon, =20
ResetOnLogout...".  I don't think that it is really necessary to put =20
MessageStore in there, as from the application users point of view it =20=

is the session state in the end that is being refreshed.  So I think =20
this creates more consistency as well as being easier to remember.

--oren

On May 28, 2006, at 2:09 AM, Steve Bate wrote:

> Hi Phil,
>
> This feature is in QuickFIX/J. There is a RefreshableMessageStore =20
> interface that provides the methods for refreshing the store and =20
> marks which stores can be refreshed (MemoryStore can't, for =20
> example). The Session can be configured to refresh it's state at =20
> logon if a refreshable store is being used (see the =20
> "RefreshMessageStoreAtLogon" configuration option). This might give =20=

> you some ideas how to modify the C++ code in a similar way.
>
> Regards,
>
> Steve
>
> From: qui...@li... =20
> [mailto:qui...@li...] On Behalf =20
> Of pc redev
> Sent: Friday, May 26, 2006 6:07 PM
> To: Oren Miller; qui...@li...
> Subject: Re: [Quickfix-developers] QuickFix FailOver/Farming Support.
>
> Oren,
>
> =46rom looking at the source looks like "revert" would propbably just =20=

> call "populateCache()" on the message store's.  Not sure where =20
> abouts in logon is the safest place to call this.
>
> What is the possibility of this being available in a future =20
> release?  I'd prefer not to change the code for my system as =20
> creates issues with Fix Fixengine releases.
>
> Also is there a way I can simulate this behaviour without changing =20
> the "FixEngineCode".  Is it possible to make the session "recreate" =20=

> on the logon event, which would also have the same effect?   In the =20=

> worst case I could expose the "PopulateCache" as a public method, =20
> and call this on the "OnLogon", however I suspect this is too late =20
> as you will have already started using the sequence number.   Any =20
> ideas on workaround would be appreciated.
>
> Thanks
> Phil.
>
> Oren Miller <or...@qu...> wrote:
> To do this we would need some sort of revert method on the =20
> MessageStore interface which would revert to the persisted state.  =20
> This could then be called by a session when receiving a logon.  It =20
> actually might be a useful thing to do in all logon situations.  It =20=

> also gives us the ability to modify sequence numbers and such =20
> without having to restart the engine.
>
> --oren
> ----- Original Message -----
> From: pc redev
> To: qui...@li...
> Sent: Thursday, May 25, 2006 2:08 PM
> Subject: [Quickfix-developers] QuickFix FailOver/Farming Support.
>
> Hi,
>
> I have a QuickFixEngine connected to a "Clustered" MS SQL Server =20
> backend, running fine.  I would like to be-able to provider =20
> "FailOver/Farming" support like:
>
> Primary Machine:  Fix Engine Running Serving Active Clients
> Secondary Machine: Fix Engine Running in No client connections.
>
> Both Fix Engines are connected to the clustered SQL Server for the =20
> message store.
>
> If I "pull the plug" on A, clients are disconnected and connect to =20
> "secondary", which in theory when they connect we pick up the =20
> session from where it left off.
>
> The problem is the "Secondary" quick fix engine does not know to =20
> "re-read" the clients "Sessions" when they connect, it appears that =20=

> this is performed when the "Fix Engine Starts Up" probably during =20
> the create session.
>
> My only solution at the moment would be to have the "Secondary" fix =20=

> engine start on failover, i.e cold standby, which is not ideal.
>
> In the Fix Engine logic is it possible to "detect" a client socket =20
> connect and force a "re-read" of session information from the =20
> message store  cleanly with no side effects?   I'd prefer not to =20
> change the Fix engine source code.
>
> Any info would be appreciated.
>
> Regards
>
> Phil.
> Copy addresses and emails from any email account to Yahoo! Mail - =20
> quick, easy and free. Do it now...
>
>
> Try the all-new Yahoo! Mail . "The New Version is radically easier =20
> to use" =96 The Wall Street Journal
>

Re: [Quickfix-developers] QuickFix FailOver/Farming Support.

[Oren M. <or...@qu...>]

Steve,

Can you explain the rational for implementing this as another =20
interface.  It seems you are using reflection to determine if the =20
interface implements RefreshableMessageStore or MessageStore.  If it =20
is, it does a downcast to RefreshableMessageStore and calls refresh, =20
if not it says that refresh is not supported.  Why wouldn't refresh =20
be on the MessageStore interface, and if the store doesn't require =20
any action to refresh (in this case since the state is in memory and =20
is therefore always up to date), implement it as a no-op?

--oren

On May 28, 2006, at 2:09 AM, Steve Bate wrote:

> Hi Phil,
>
> This feature is in QuickFIX/J. There is a RefreshableMessageStore =20
> interface that provides the methods for refreshing the store and =20
> marks which stores can be refreshed (MemoryStore can't, for =20
> example). The Session can be configured to refresh it's state at =20
> logon if a refreshable store is being used (see the =20
> "RefreshMessageStoreAtLogon" configuration option). This might give =20=

> you some ideas how to modify the C++ code in a similar way.
>
> Regards,
>
> Steve
>
> From: qui...@li... =20
> [mailto:qui...@li...] On Behalf =20
> Of pc redev
> Sent: Friday, May 26, 2006 6:07 PM
> To: Oren Miller; qui...@li...
> Subject: Re: [Quickfix-developers] QuickFix FailOver/Farming Support.
>
> Oren,
>
> =46rom looking at the source looks like "revert" would propbably just =20=

> call "populateCache()" on the message store's.  Not sure where =20
> abouts in logon is the safest place to call this.
>
> What is the possibility of this being available in a future =20
> release?  I'd prefer not to change the code for my system as =20
> creates issues with Fix Fixengine releases.
>
> Also is there a way I can simulate this behaviour without changing =20
> the "FixEngineCode".  Is it possible to make the session "recreate" =20=

> on the logon event, which would also have the same effect?   In the =20=

> worst case I could expose the "PopulateCache" as a public method, =20
> and call this on the "OnLogon", however I suspect this is too late =20
> as you will have already started using the sequence number.   Any =20
> ideas on workaround would be appreciated.
>
> Thanks
> Phil.
>
> Oren Miller <or...@qu...> wrote:
> To do this we would need some sort of revert method on the =20
> MessageStore interface which would revert to the persisted state.  =20
> This could then be called by a session when receiving a logon.  It =20
> actually might be a useful thing to do in all logon situations.  It =20=

> also gives us the ability to modify sequence numbers and such =20
> without having to restart the engine.
>
> --oren
> ----- Original Message -----
> From: pc redev
> To: qui...@li...
> Sent: Thursday, May 25, 2006 2:08 PM
> Subject: [Quickfix-developers] QuickFix FailOver/Farming Support.
>
> Hi,
>
> I have a QuickFixEngine connected to a "Clustered" MS SQL Server =20
> backend, running fine.  I would like to be-able to provider =20
> "FailOver/Farming" support like:
>
> Primary Machine:  Fix Engine Running Serving Active Clients
> Secondary Machine: Fix Engine Running in No client connections.
>
> Both Fix Engines are connected to the clustered SQL Server for the =20
> message store.
>
> If I "pull the plug" on A, clients are disconnected and connect to =20
> "secondary", which in theory when they connect we pick up the =20
> session from where it left off.
>
> The problem is the "Secondary" quick fix engine does not know to =20
> "re-read" the clients "Sessions" when they connect, it appears that =20=

> this is performed when the "Fix Engine Starts Up" probably during =20
> the create session.
>
> My only solution at the moment would be to have the "Secondary" fix =20=

> engine start on failover, i.e cold standby, which is not ideal.
>
> In the Fix Engine logic is it possible to "detect" a client socket =20
> connect and force a "re-read" of session information from the =20
> message store  cleanly with no side effects?   I'd prefer not to =20
> change the Fix engine source code.
>
> Any info would be appreciated.
>
> Regards
>
> Phil.
> Copy addresses and emails from any email account to Yahoo! Mail - =20
> quick, easy and free. Do it now...
>
>
> Try the all-new Yahoo! Mail . "The New Version is radically easier =20
> to use" =96 The Wall Street Journal
>

RE: [Quickfix-developers] QuickFix FailOver/Farming Support.

[Steve B. <sb...@sm...>]

Hi Phil,
=20
This feature is in QuickFIX/J. There is a RefreshableMessageStore
interface that provides the methods for refreshing the store and marks
which stores can be refreshed (MemoryStore can't, for example). The
Session can be configured to refresh it's state at logon if a
refreshable store is being used (see the "RefreshMessageStoreAtLogon"
configuration option). This might give you some ideas how to modify the
C++ code in a similar way.
=20
Regards,
=20
Steve


________________________________

	From: qui...@li...
[mailto:qui...@li...] On Behalf Of pc
redev
	Sent: Friday, May 26, 2006 6:07 PM
	To: Oren Miller; qui...@li...
	Subject: Re: [Quickfix-developers] QuickFix FailOver/Farming
Support.
=09
=09
	Oren,
	=20
	From looking at the source looks like "revert" would propbably
just call "populateCache()" on the message store's.  Not sure where
abouts in logon is the safest place to call this.
	=20
	What is the possibility of this being available in a future
release?  I'd prefer not to change the code for my system as creates
issues with Fix Fixengine releases.
	=20
	Also is there a way I can simulate this behaviour without
changing the "FixEngineCode".  Is it possible to make the session
"recreate" on the logon event, which would also have the same effect?
In the worst case I could expose the "PopulateCache" as a public method,
and call this on the "OnLogon", however I suspect this is too late as
you will have already started using the sequence number.   Any ideas on
workaround would be appreciated.
	=20
	Thanks
	Phil.
=09
	Oren Miller <or...@qu...> wrote:

		To do this we would need some sort of revert method on
the MessageStore interface which would revert to the persisted state.
This could then be called by a session when receiving a logon.  It
actually might be a useful thing to do in all logon situations.  It also
gives us the ability to modify sequence numbers and such without having
to restart the engine.
		=20
		--oren

			----- Original Message -----=20
			From: pc redev <mailto:pc....@ta...> =20
			To: qui...@li...=20
			Sent: Thursday, May 25, 2006 2:08 PM
			Subject: [Quickfix-developers] QuickFix
FailOver/Farming Support.

			Hi,=20
			=20
			I have a QuickFixEngine connected to a
"Clustered" MS SQL Server backend, running fine.  I would like to
be-able to provider "FailOver/Farming" support like:
			=20
			Primary Machine:  Fix Engine Running Serving
Active Clients
			Secondary Machine: Fix Engine Running in No
client connections.
			=20
			Both Fix Engines are connected to the clustered
SQL Server for the message store. =20
			=20
			If I "pull the plug" on A, clients are
disconnected and connect to "secondary", which in theory when they
connect we pick up the session from where it left off.
			=20
			The problem is the "Secondary" quick fix engine
does not know to "re-read" the clients "Sessions" when they connect, it
appears that this is performed when the "Fix Engine Starts Up" probably
during the create session.
			=20
			My only solution at the moment would be to have
the "Secondary" fix engine start on failover, i.e cold standby, which is
not ideal.=20
			=20
			In the Fix Engine logic is it possible to
"detect" a client socket connect and force a "re-read" of session
information from the message store  cleanly with no side effects?   I'd
prefer not to change the Fix engine source code. =20
			=20
			Any info would be appreciated.
			=20
			Regards
			=20
			Phil.
________________________________

			Copy addresses and emails from any email account
to Yahoo! Mail - quick, easy and free. Do it now...
<http://us.rd.yahoo.com/mail/uk/taglines/default/trueswitch/*http://uk.d
ocs.yahoo.com/trueswitch2.html>=20


=09
________________________________

	Try the all-new Yahoo! Mail
<http://us.rd.yahoo.com/mail/uk/taglines/default/nowyoucan/wall_st_2/*ht
tp://us.rd.yahoo.com/evt=3D40565/*http://uk.docs.yahoo.com/nowyoucan.html=
>
. "The New Version is radically easier to use" - The Wall Street Journal

Re: [Quickfix-developers] QuickFix FailOver/Farming Support.

[pc r. <pc....@ta...>]

Oren,
   
  From looking at the source looks like "revert" would propbably just call "populateCache()" on the message store's.  Not sure where abouts in logon is the safest place to call this.
   
  What is the possibility of this being available in a future release?  I'd prefer not to change the code for my system as creates issues with Fix Fixengine releases.
   
  Also is there a way I can simulate this behaviour without changing the "FixEngineCode".  Is it possible to make the session "recreate" on the logon event, which would also have the same effect?   In the worst case I could expose the "PopulateCache" as a public method, and call this on the "OnLogon", however I suspect this is too late as you will have already started using the sequence number.   Any ideas on workaround would be appreciated.
   
  Thanks
  Phil.

Oren Miller <or...@qu...> wrote:
          To do this we would need some sort of revert method on the MessageStore interface which would revert to the persisted state.  This could then be called by a session when receiving a logon.  It actually might be a useful thing to do in all logon situations.  It also gives us the ability to modify sequence numbers and such without having to restart the engine.
   
  --oren
    ----- Original Message ----- 
  From: pc redev 
  To: qui...@li... 
  Sent: Thursday, May 25, 2006 2:08 PM
  Subject: [Quickfix-developers] QuickFix FailOver/Farming Support.
  

  Hi, 
   
  I have a QuickFixEngine connected to a "Clustered" MS SQL Server backend, running fine.  I would like to be-able to provider "FailOver/Farming" support like:
   
  Primary Machine:  Fix Engine Running Serving Active Clients
  Secondary Machine: Fix Engine Running in No client connections.
   
  Both Fix Engines are connected to the clustered SQL Server for the message store.  
   
  If I "pull the plug" on A, clients are disconnected and connect to "secondary", which in theory when they connect we pick up the session from where it left off.
   
  The problem is the "Secondary" quick fix engine does not know to "re-read" the clients "Sessions" when they connect, it appears that this is performed when the "Fix Engine Starts Up" probably during the create session.
   
  My only solution at the moment would be to have the "Secondary" fix engine start on failover, i.e cold standby, which is not ideal. 
   
  In the Fix Engine logic is it possible to "detect" a client socket connect and force a "re-read" of session information from the message store  cleanly with no side effects?   I'd prefer not to change the Fix engine source code.  
   
  Any info would be appreciated.
   
  Regards
   
  Phil.
    
---------------------------------
  Copy addresses and emails from any email account to Yahoo! Mail - quick, easy and free. Do it now...

		
---------------------------------
 Try the all-new Yahoo! Mail . "The New Version is radically easier to use" – The Wall Street Journal

RE: [Quickfix-developers] QFJ: Session EndTime and Logout

[Steve B. <sb...@sm...>]

Toby,
=20
This might be related to a bug that was fixed this morning in
Subversion. The logon and logout timeout defaults were zero. They should
have been 10 seconds for the logon timeout and 2 seconds for the logout
timeout. These are configurable, so the workaround for now is to set the
timeouts explicitly in the configuration file.
=20
Steve


________________________________

	From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Shepheard, Toby (London)
	Sent: Friday, May 26, 2006 2:00 PM
	To: qui...@li...
	Subject: [Quickfix-developers] QFJ: Session EndTime and Logout
=09
=09

	Hiya,=20

	A quick question on the Session EndTime. I'd assumed that when
running as an Initiator, QFJ would send a Logout message (and await a
Logout response for LogoutTimeout seconds) when the EndTime is reached,
but when I tested it, it just does a TCP FIN (disconnect). Is this
expected behaviour or a bug?

	I'm running with a ThreadedSocketInitiator, QFJ 1.0.0.=20

	[2006-05-26 12:24:23,126][INFO ][QFJ Timer
reuters.protocol.ReutersQFApplication]:   Sending FIX heartbeat message
FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1

	[2006-05-26 12:24:23,126][INFO ][QFJ Timer
quickfixj.msg.outgoing]:
8=3DFIX.4.4=019=3D68=0135=3D0=0134=3D15=0149=3DML_RTFI_DEV1=0152=3D200605=
26-11:24:23.126=0156=3DRE
UTFIXTEST1=0110=3D062=01

	[2006-05-26 12:24:44,083][INFO ][AnonymousIoService-1-2
quickfixj.msg.incoming]:
8=3DFIX.4.4=019=3D68=0135=3D0=0134=3D17=0149=3DREUTFIXTEST1=0152=3D200605=
26-11:24:06.324=0156=3DML
_RTFI_DEV1=0110=3D065=01

	[2006-05-26 12:24:44,083][DEBUG][QF/J Session dispatcher:
FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1
reuters.protocol.ReutersQFApplication]:   QuickFIX session
FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1: fromAdmin()

	[2006-05-26 12:24:44,083][INFO ][QF/J Session dispatcher:
FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1
reuters.protocol.ReutersQFApplication]:   Received FIX heartbeat message
FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1

	[2006-05-26 12:24:53,146][INFO ][QFJ Timer
reuters.protocol.ReutersQFApplication]:   Sending FIX heartbeat message
FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1

	[2006-05-26 12:24:53,146][INFO ][QFJ Timer
quickfixj.msg.outgoing]:
8=3DFIX.4.4=019=3D68=0135=3D0=0134=3D16=0149=3DML_RTFI_DEV1=0152=3D200605=
26-11:24:53.146=0156=3DRE
UTFIXTEST1=0110=3D068=01

	[2006-05-26 12:25:02,830][INFO ][QFJ Timer quickfixj.event]:
Disconnecting=20
	[2006-05-26 12:25:02,830][INFO ][QFJ Timer
reuters.protocol.ReutersQFApplication]:   Logged out from the FIX engine
for session FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1

	[2006-05-26 12:25:02,830][INFO ][QFJ Timer
protocol.session.ReutersSession]:   Logged out from FIX session, setting
AQ Session status to DISCONNECTED

	Regards,=20
	Toby=20

________________________________

	If you are not an intended recipient of this e-mail, please
notify the sender, delete it and do not read, act upon, print, disclose,
copy, retain or redistribute it. Click here
<http://www.ml.com/email_terms/> for important additional terms relating
to this e-mail.     http://www.ml.com/email_terms/
________________________________

[Quickfix-developers] QFJ: Session EndTime and Logout

[Shepheard, T. \(London\) <Tob...@ml...>]

Hiya,

A quick question on the Session EndTime. I'd assumed that when running
as an Initiator, QFJ would send a Logout message (and await a Logout
response for LogoutTimeout seconds) when the EndTime is reached, but
when I tested it, it just does a TCP FIN (disconnect). Is this expected
behaviour or a bug?

I'm running with a ThreadedSocketInitiator, QFJ 1.0.0.

[2006-05-26 12:24:23,126][INFO ][QFJ Timer
reuters.protocol.ReutersQFApplication]:   Sending FIX heartbeat message
FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1
[2006-05-26 12:24:23,126][INFO ][QFJ Timer quickfixj.msg.outgoing]:
8=3DFIX.4.4=019=3D68=0135=3D0=0134=3D15=0149=3DML_RTFI_DEV1=0152=3D200605=
26-11:24:23.126=0156=3DRE
UTFIXTEST1=0110=3D062=01
[2006-05-26 12:24:44,083][INFO ][AnonymousIoService-1-2
quickfixj.msg.incoming]:
8=3DFIX.4.4=019=3D68=0135=3D0=0134=3D17=0149=3DREUTFIXTEST1=0152=3D200605=
26-11:24:06.324=0156=3DML
_RTFI_DEV1=0110=3D065=01
[2006-05-26 12:24:44,083][DEBUG][QF/J Session dispatcher:
FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1
reuters.protocol.ReutersQFApplication]:   QuickFIX session
FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1: fromAdmin()
[2006-05-26 12:24:44,083][INFO ][QF/J Session dispatcher:
FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1
reuters.protocol.ReutersQFApplication]:   Received FIX heartbeat message
FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1
[2006-05-26 12:24:53,146][INFO ][QFJ Timer
reuters.protocol.ReutersQFApplication]:   Sending FIX heartbeat message
FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1
[2006-05-26 12:24:53,146][INFO ][QFJ Timer quickfixj.msg.outgoing]:
8=3DFIX.4.4=019=3D68=0135=3D0=0134=3D16=0149=3DML_RTFI_DEV1=0152=3D200605=
26-11:24:53.146=0156=3DRE
UTFIXTEST1=0110=3D068=01
[2006-05-26 12:25:02,830][INFO ][QFJ Timer quickfixj.event]:
Disconnecting
[2006-05-26 12:25:02,830][INFO ][QFJ Timer
reuters.protocol.ReutersQFApplication]:   Logged out from the FIX engine
for session FIX.4.4:ML_RTFI_DEV1->REUTFIXTEST1
[2006-05-26 12:25:02,830][INFO ][QFJ Timer
protocol.session.ReutersSession]:   Logged out from FIX session, setting
AQ Session status to DISCONNECTED

Regards,
Toby
--------------------------------------------------------

If you are not an intended recipient of this e-mail, please notify the =
sender, delete it and do not read, act upon, print, disclose, copy, =
retain or redistribute it. Click here for important additional terms =
relating to this e-mail.     http://www.ml.com/email_terms/
--------------------------------------------------------

Re: [Quickfix-developers] QuickFix FailOver/Farming Support.

[Oren M. <or...@qu...>]

To do this we would need some sort of revert method on the MessageStore =
interface which would revert to the persisted state.  This could then be =
called by a session when receiving a logon.  It actually might be a =
useful thing to do in all logon situations.  It also gives us the =
ability to modify sequence numbers and such without having to restart =
the engine.

--oren
  ----- Original Message -----=20
  From: pc redev=20
  To: qui...@li...=20
  Sent: Thursday, May 25, 2006 2:08 PM
  Subject: [Quickfix-developers] QuickFix FailOver/Farming Support.


  Hi,=20

  I have a QuickFixEngine connected to a "Clustered" MS SQL Server =
backend, running fine.  I would like to be-able to provider =
"FailOver/Farming" support like:

  Primary Machine:  Fix Engine Running Serving Active Clients
  Secondary Machine: Fix Engine Running in No client connections.

  Both Fix Engines are connected to the clustered SQL Server for the =
message store. =20

  If I "pull the plug" on A, clients are disconnected and connect to =
"secondary", which in theory when they connect we pick up the session =
from where it left off.

  The problem is the "Secondary" quick fix engine does not know to =
"re-read" the clients "Sessions" when they connect, it appears that this =
is performed when the "Fix Engine Starts Up" probably during the create =
session.

  My only solution at the moment would be to have the "Secondary" fix =
engine start on failover, i.e cold standby, which is not ideal.=20

  In the Fix Engine logic is it possible to "detect" a client socket =
connect and force a "re-read" of session information from the message =
store  cleanly with no side effects?   I'd prefer not to change the Fix =
engine source code. =20

  Any info would be appreciated.

  Regards

  Phil.


-------------------------------------------------------------------------=
-----
  Copy addresses and emails from any email account to Yahoo! Mail - =
quick, easy and free. Do it now...

[Quickfix-developers] QuickFix FailOver/Farming Support.

[pc r. <pc....@ta...>]

Hi, 
   
  I have a QuickFixEngine connected to a "Clustered" MS SQL Server backend, running fine.  I would like to be-able to provider "FailOver/Farming" support like:
   
  Primary Machine:  Fix Engine Running Serving Active Clients
  Secondary Machine: Fix Engine Running in No client connections.
   
  Both Fix Engines are connected to the clustered SQL Server for the message store.  
   
  If I "pull the plug" on A, clients are disconnected and connect to "secondary", which in theory when they connect we pick up the session from where it left off.
   
  The problem is the "Secondary" quick fix engine does not know to "re-read" the clients "Sessions" when they connect, it appears that this is performed when the "Fix Engine Starts Up" probably during the create session.
   
  My only solution at the moment would be to have the "Secondary" fix engine start on failover, i.e cold standby, which is not ideal. 
   
  In the Fix Engine logic is it possible to "detect" a client socket connect and force a "re-read" of session information from the message store  cleanly with no side effects?   I'd prefer not to change the Fix engine source code.  
   
  Any info would be appreciated.
   
  Regards
   
  Phil.

		
---------------------------------
 Copy addresses and emails from any email account to Yahoo! Mail - quick, easy and free. Do it now...

[Quickfix-developers] Subversion Repository

[Oren M. <or...@qu...>]

The QuickFIX source has migrated from CVS to a Subversion repository.  The 
conversion was done with cvs2svn, so all the history has been transfered. 
Directions on accessing the repository are on the developer page: 
http://www.quickfixengine.org/developers.html

Unlike with CVS, everybody hits the same repository, so there are no delays 
between commiter checkins and public checkouts.

--oren 

Re: [Quickfix-developers] linux compilation

[Caleb E. <cal...@gm...>]

On 5/25/06, Igor Seleznev <se...@ma...> wrote:

> The "LIBXML_DOMAttributes::" in front of toMap() is not necessary and
> becomes an error with gcc 4.1.

Yes I know.  This was fixed in CVS yesterday about 5 minutes after
your initial report.

--=20
Caleb Epstein
caleb dot epstein at gmail dot com

Re: [Quickfix-developers] linux compilation

[Igor S. <se...@ma...>]

Hi,

Correct :)
This code snapshot was taken from one of many pages found via google, I 
didn't notice that it is erroneous because I was focused on the actual 
problem.
The idea is that gcc 4.1 doesn't ignore extra qualification anymore. And 
quickfix does have such. I mention it once again, please ignore all this if 
it has been fixed in CVS already.

quickfix/src/C++/LIBXML_DOMDocument.h:
...
  class LIBXML_DOMAttributes : public DOMAttributes
  {
    bool get( const std::string&, std::string& );
    DOMAttributes::map LIBXML_DOMAttributes::toMap();
  };
...

The "LIBXML_DOMAttributes::" in front of toMap() is not necessary and 
becomes an error with gcc 4.1.

Kind regards,
Igor

----- Original Message ----- 
From: "Caleb Epstein" <cal...@gm...>
To: "Igor Seleznev" <se...@ma...>
Cc: "Alexey Zubko" <ale...@gm...>; 
<qui...@li...>
Sent: Wednesday, May 24, 2006 11:26 PM
Subject: Re: [Quickfix-developers] linux compilation


On 5/24/06, Igor Seleznev <se...@ma...> wrote:
> For quickfix developers: the problem is that instead of
>
> class Foo
> {
>  int Foo::Foo(void);
> }
>
> it is better to write: class Foo
> {
>   int Foo(void);
> }

Its not that the latter is better.  The former is just plain wrong.
The code only compiled because the compiler (e.g. older versions of
gcc) wasn't strict enough.

A constructor can't return a value anyway, so both forms are wrong :)

-- 
Caleb Epstein
caleb dot epstein at gmail dot com

Re: [Quickfix-developers] linux compilation

[Caleb E. <cal...@gm...>]

On 5/24/06, Igor Seleznev <se...@ma...> wrote:
> For quickfix developers: the problem is that instead of
>
> class Foo
> {
>  int Foo::Foo(void);
> }
>
> it is better to write: class Foo
> {
>   int Foo(void);
> }

Its not that the latter is better.  The former is just plain wrong.
The code only compiled because the compiler (e.g. older versions of
gcc) wasn't strict enough.

A constructor can't return a value anyway, so both forms are wrong :)

--=20
Caleb Epstein
caleb dot epstein at gmail dot com

Re: [Quickfix-developers] linux compilation

[Caleb E. <cal...@gm...>]

On 5/24/06, Alexey Zubko <ale...@gm...> wrote:
>
>  Hi Igor,
>
>  Thanks a lot.
>  I deleted that directory and bootstrap and configure passed Ok.
>  Now I crash during the compilation:
>
>   g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I. -I.. -I../.. -g -O2
> -I/usr/include/libxml2 -MT DataDictionary.lo -MD -MP -MF .deps/D
>                  ataDictionary.Tpo -c DataDictionary.cpp
> -fPIC -DPIC -o .libs/DataDictionary.o
>  LIBXML_DOMDocument.h:45: error: extra qualification
> 'FIX::LIBXML_DOMAttributes::' on member 'toMap'

Fixed in CVS.

--=20
Caleb Epstein
caleb dot epstein at gmail dot com

Re: [Quickfix-developers] linux compilation

[Alexey Z. <ale...@gm...>]

Hi,

I removed this "extra qualification" and QuickFix continued and created 
lib/libquickfix.so.
So, it looks like everything is fine.
Thank you for your help.

What kind of development environment do you use? Eclipse, KDevelop, 
Emacs, Vim?
I was always interested in Linux but never had chance to write a big 
project.
Could you suggest me anything?
Thanks.

Regards,
		Alexey Zubko



Igor Seleznev wrote:
> Hi,
>  
> I am using:
> Red Hat Enterprise Linux ES release 4 (Nahant Update 3)
> gcc version 3.4.5 20051201 (Red Hat 3.4.5-2)
> Perhaps your problem because of the gcc 4.1 -- I "googled" and see 
> such complains about this warning exactly because of gcc 4.1.
> Please, try to use 3.x.
>
> For quickfix developers: the problem is that instead of
> class Foo
> {
>
>     int Foo::Foo(void);
>
> }
>
> it is better to write: 
>
> class Foo
> {
>
>     int Foo(void);
>
> }
> Kind regards,
> Igor
>
>     ----- Original Message -----
>     *From:* Alexey Zubko <mailto:ale...@gm...>
>     *To:* Igor Seleznev <mailto:se...@ma...>
>     *Cc:* qui...@li...
>     <mailto:qui...@li...>
>     *Sent:* Wednesday, May 24, 2006 8:24 PM
>     *Subject:* Re: [Quickfix-developers] linux compilation
>
>     Hi Igor,
>
>     Thanks a lot.
>     I deleted that directory and bootstrap and configure passed Ok.
>     Now I crash during the compilation:
>
>      g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I. -I.. -I../.. -g -O2
>     -I/usr/include/libxml2 -MT DataDictionary.lo -MD -MP -MF
>     ..deps/D                              ataDictionary.Tpo -c
>     DataDictionary.cpp  -fPIC -DPIC -o .libs/DataDictionary.o
>     LIBXML_DOMDocument.h:45: error: extra qualification
>     'FIX::LIBXML_DOMAttributes::' on member 'toMap'
>     make[4]: *** [DataDictionary.lo] Error 1
>     make[4]: Leaving directory `/home/alexey/workspace/quickfix/src/C++'
>     make[3]: *** [all-recursive] Error 1
>     make[3]: Leaving directory `/home/alexey/workspace/quickfix/src/C++'
>     make[2]: *** [all-recursive] Error 1
>     make[2]: Leaving directory `/home/alexey/workspace/quickfix/src'
>     make[1]: *** [all-recursive] Error 1
>     make[1]: Leaving directory `/home/alexey/workspace/quickfix'
>     make: *** [all] Error 2
>
>
>     Does it mean I need to use another gcc version?
>     BTW, what environment do you use for your projects?
>
>     Thank you.
>
>     Regards,
>     		Alexey Zubko
>         
>
>
>
>     Igor Seleznev wrote:
>>     Hi,
>>
>>     I have experienced some of your problems too.
>>
>>     To fix the first one with 'bootstrap', please delete
>>     "quickfix/autom4te.cache". I noticed that one of quickfix
>>     tarballs contains it. I will file a bug about this issue.
>>
>>     As for second one with 'missing' script, you can ignore it.
>>     Moreover, there was a case about it and it claimed to be fixed in
>>     HEAD.
>>     See:
>>     http://www.quickfixengine.org/bugtracker/bug.php?op=show&bugid=183&pos=0
>>
>>
>>     Most likely the last problem will be fixed when you fix the first
>>     two. From your logs it looks like that 'automake' cached into
>>     wrong location.
>>     If it doesn't help, perhaps it makes sense to run configure in
>>     debug mode (sh -x ./configure) and see what's wrong.
>>
>>     Kind regards,
>>     Igor
>>
>>     ----- Original Message ----- From: "Alexey Zubko"
>>     <ale...@gm...>
>>     To: <qui...@li...>
>>     Sent: Wednesday, May 24, 2006 7:34 PM
>>     Subject: [Quickfix-developers] linux compilation
>>
>>
>>>     QuickFIX Documentation:
>>>     http://www.quickfixengine.org/quickfix/doc/html/index.html
>>>     QuickFIX Support: http://www.quickfixengine.org/services.html
>>>
>>>     Hello guys,
>>>
>>>     I want to compile quickfix in Linux, but unfortunately don't
>>>     have such experience now.
>>>     I know I need to learn a lot, but as a start could anyone help
>>>     me, please?
>>>     Does anyone use Eclipse CDT?
>>>     Thank you in advance.
>>>
>>>     So, I have Gentoo Linux with gcc 4.1.0 and quickfix 1.11.1
>>>
>>>     # ./bootstrap
>>>     aclocal...
>>>     autoheader...
>>>     Can't locate object method "path" via package "Request" at
>>>     /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
>>>     autoheader-2.59: /usr/bin/autom4te-2.59 failed with exit status: 1
>>>     libtoolize...
>>>     automake...
>>>     Can't locate object method "path" via package "Request" at
>>>     /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
>>>     configure.in: no proper invocation of AM_INIT_AUTOMAKE was found.
>>>     configure.in: You should verify that configure.in invokes
>>>     AM_INIT_AUTOMAKE,
>>>     configure.in: that aclocal.m4 is present in the top-level
>>>     directory,
>>>     configure.in: and that aclocal.m4 was recently regenerated
>>>     (using aclocal).
>>>     automake-1.7: no `Makefile.am' found or specified
>>>     autoconf...
>>>     Can't locate object method "path" via package "Request" at
>>>     /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
>>>     Now run configure with any arguments necessary
>>>
>>>     After that:
>>>     # ./configure
>>>     checking for a BSD-compatible install... /usr/bin/install -c
>>>     checking whether build environment is sane... yes
>>>     /home/alexey/workspace/quickfix/missing: Unknown `--run' option
>>>     Try `/home/alexey/workspace/quickfix/missing --help' for more
>>>     information
>>>     configure: WARNING: `missing' script is too old or missing
>>>     checking for gawk... gawk
>>>     checking whether make sets $(MAKE)... yes
>>>     checking for g++... g++
>>>     checking for C++ compiler default output... a.out
>>>     checking whether the C++ compiler works... yes
>>>     checking whether we are cross compiling... no
>>>     checking for suffix of executables...
>>>     checking for suffix of object files... o
>>>     checking whether we are using the GNU C++ compiler... yes
>>>     checking whether g++ accepts -g... yes
>>>     checking for style of include used by make... GNU
>>>     checking dependency style of g++... gcc3
>>>     checking for gcc... gcc
>>>     checking whether we are using the GNU C compiler... yes
>>>     checking whether gcc accepts -g... yes
>>>     checking for gcc option to accept ANSI C... none needed
>>>     checking dependency style of gcc... gcc3
>>>     checking build system type... i686-pc-linux-gnu
>>>     checking host system type... i686-pc-linux-gnu
>>>     checking for a sed that does not truncate output... /usr/bin/sed
>>>     checking for egrep... grep -E
>>>     checking for ld used by gcc... /usr/i686-pc-linux-gnu/bin/ld
>>>     checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU
>>>     ld... yes
>>>     checking for /usr/i686-pc-linux-gnu/bin/ld option to reload
>>>     object files... -r
>>>     checking for BSD-compatible nm... /usr/bin/nm -B
>>>     checking whether ln -s works... yes
>>>     checking how to recognise dependent libraries... pass_all
>>>     checking how to run the C preprocessor... gcc -E
>>>     checking for ANSI C header files... yes
>>>     checking for sys/types.h... yes
>>>     checking for sys/stat.h... yes
>>>     checking for stdlib.h... yes
>>>     checking for string.h... yes
>>>     checking for memory.h... yes
>>>     checking for strings.h... yes
>>>     checking for inttypes.h... yes
>>>     checking for stdint.h... yes
>>>     checking for unistd.h... yes
>>>     checking dlfcn.h usability... yes
>>>     checking dlfcn.h presence... yes
>>>     checking for dlfcn.h... yes
>>>     checking how to run the C++ preprocessor... g++ -E
>>>     checking for g77... no
>>>     checking for f77... no
>>>     checking for xlf... no
>>>     checking for frt... no
>>>     checking for pgf77... no
>>>     checking for fl32... no
>>>     checking for af77... no
>>>     checking for fort77... no
>>>     checking for f90... no
>>>     checking for xlf90... no
>>>     checking for pgf90... no
>>>     checking for epcf90... no
>>>     checking for f95... no
>>>     checking for fort... no
>>>     checking for xlf95... no
>>>     checking for lf95... no
>>>     checking for g95... no
>>>     checking whether we are using the GNU Fortran 77 compiler... no
>>>     checking whether  accepts -g... no
>>>     checking the maximum length of command line arguments... 32768
>>>     checking command to parse /usr/bin/nm -B output from gcc
>>>     object... ok
>>>     checking for objdir... .libs
>>>     checking for ar... ar
>>>     checking for ranlib... ranlib
>>>     checking for strip... strip
>>>     checking if gcc static flag  works... yes
>>>     checking if gcc supports -fno-rtti -fno-exceptions... no
>>>     checking for gcc option to produce PIC... -fPIC
>>>     checking if gcc PIC flag -fPIC works... yes
>>>     checking if gcc supports -c -o file.o... yes
>>>     checking whether the gcc linker (/usr/i686-pc-linux-gnu/bin/ld)
>>>     supports shared libraries... yes
>>>     checking whether -lc should be explicitly linked in... no
>>>     checking dynamic linker characteristics... GNU/Linux ld.so
>>>     checking how to hardcode library paths into programs... immediate
>>>     checking whether stripping libraries is possible... yes
>>>     checking if libtool supports shared libraries... yes
>>>     checking whether to build shared libraries... yes
>>>     checking whether to build static libraries... no
>>>     configure: creating libtool
>>>     appending configuration tag "CXX" to libtool
>>>     checking for ld used by g++... /usr/i686-pc-linux-gnu/bin/ld
>>>     checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU
>>>     ld... yes
>>>     checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld)
>>>     supports shared libraries... yes
>>>     checking for g++ option to produce PIC... -fPIC
>>>     checking if g++ PIC flag -fPIC works... yes
>>>     checking if g++ supports -c -o file.o... yes
>>>     checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld)
>>>     supports shared libraries... yes
>>>     checking dynamic linker characteristics... GNU/Linux ld.so
>>>     checking how to hardcode library paths into programs... immediate
>>>     checking whether stripping libraries is possible... yes
>>>     appending configuration tag "F77" to libtool
>>>     checking for flex... flex
>>>     checking for yywrap in -lfl... yes
>>>     checking lex output file root... lex.yy
>>>     checking whether yytext is a pointer... yes
>>>     .../configure: line 19059: ruby: command not found
>>>     checking for xml2-config... /usr/bin/xml2-config
>>>     checking for libxml - version >= 2.0.0... yes (version 2.6.23)
>>>     checking for shutdown in -lc... yes
>>>     checking for inet_addr in -lc... yes
>>>     checking for nanosleep in -lc... yes
>>>     checking for ftime in -lcompat... no
>>>     checking which threading environment to use... -lpthread
>>>     checking for pthread_create in -lpthread... yes
>>>     checking stdio.h usability... yes
>>>     checking stdio.h presence... yes
>>>     checking for stdio.h... yes
>>>     checking for STREAMS ioctl... no
>>>     checking for socklen_t... yes
>>>     checking for ftime... yes
>>>     checking for set_terminate in the global namespace... no
>>>     checking for set_terminate in the std namespace... yes
>>>     checking for typeinfo in the global namespace... no
>>>     checking for typeinfo in the std namespace... yes
>>>     checking for gethostbyname_r with input result... yes
>>>     checking for gethostbyname_r with return result... no
>>>     checking for cplus_demangle in -liberty... yes
>>>     checking if select modifies timeval parameter... yes
>>>     configure: creating ./config.status
>>>     config.status: creating quickfix.pc
>>>     config.status: creating Makefile
>>>     config.status: creating src/Makefile
>>>     config.status: creating src/C++/Makefile
>>>     config.status: creating src/C++/test/Makefile
>>>     config.status: creating src/java/Makefile
>>>     config.status: creating src/java/cfg/Makefile
>>>     config.status: creating src/java/src/Makefile
>>>     config.status: creating src/java/src/quickfix/Makefile
>>>     config.status: creating src/java/src/quickfix/field/Makefile
>>>     config.status: creating src/java/src/quickfix/fix40/Makefile
>>>     config.status: creating src/java/src/quickfix/fix41/Makefile
>>>     config.status: creating src/java/src/quickfix/fix42/Makefile
>>>     config.status: creating src/java/src/quickfix/fix43/Makefile
>>>     config.status: creating src/java/src/quickfix/fix44/Makefile
>>>     config.status: creating src/python/Makefile
>>>     config.status: creating bin/Makefile
>>>     config.status: creating bin/cfg/Makefile
>>>     config.status: creating spec/Makefile
>>>     config.status: creating test/Makefile
>>>     config.status: creating test/atrun/Makefile
>>>     config.status: creating test/cfg/Makefile
>>>     config.status: creating test/definitions/Makefile
>>>     config.status: creating test/definitions/server/Makefile
>>>     config.status: creating test/definitions/server/future/Makefile
>>>     config.status: creating examples/Makefile
>>>     config.status: creating examples/executor/Makefile
>>>     config.status: creating examples/executor/C++/Makefile
>>>     config.status: creating examples/executor/java/Makefile
>>>     config.status: creating examples/executor/java/src/Makefile
>>>     config.status: creating examples/ordermatch/Makefile
>>>     config.status: creating examples/ordermatch/test/Makefile
>>>     config.status: creating examples/tradeclient/Makefile
>>>     config.status: creating examples/tradeclientgui/Makefile
>>>     config.status: creating examples/tradeclientgui/banzai/Makefile
>>>     config.status: creating
>>>     examples/tradeclientgui/banzai/test/Makefile
>>>     config.status: creating examples/tradeclientgui/banzai/src/Makefile
>>>     config.status: creating
>>>     examples/tradeclientgui/banzai/src/quickfix/Makefile
>>>     config.status: creating
>>>     examples/tradeclientgui/banzai/src/quickfix/banzai/Makefile
>>>     config.status: creating
>>>     examples/tradeclientgui/banzai/src/quickfix/banzai/ui/Makefile
>>>     config.status: creating doc/Makefile
>>>     config.status: creating doc/html/Makefile
>>>     config.status: creating CPPTest/Makefile
>>>     config.status: creating config.h
>>>     config.status: config.h is unchanged
>>>     config.status: executing depfiles commands
>>>
>>>     # make
>>>     cd . && \
>>>       --foreign  Makefile
>>>     /bin/sh: --foreign: command not found
>>>     make: *** [Makefile.in] Error 127
>>>
>>>
>>>
>>>     -- 
>>>     Regards,
>>>     Alexey Zubko
>>>
>>>
>>>
>>>     -------------------------------------------------------
>>>     All the advantages of Linux Managed Hosting--Without the Cost
>>>     and Risk!
>>>     Fully trained technicians. The highest number of Red Hat
>>>     certifications in
>>>     the hosting industry. Fanatical Support. Click to learn more
>>>     http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
>>>
>>>     _______________________________________________
>>>     Quickfix-developers mailing list
>>>     Qui...@li...
>>>     https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>>>
>>
>>

Re: [Quickfix-developers] linux compilation

[Igor S. <se...@ma...>]

Hi,

I am using:
Red Hat Enterprise Linux ES release 4 (Nahant Update 3)
gcc version 3.4.5 20051201 (Red Hat 3.4.5-2)

Perhaps your problem because of the gcc 4.1 -- I "googled" and see such =
complains about this warning exactly because of gcc 4.1.
Please, try to use 3.x.

For quickfix developers: the problem is that instead of
class Foo
{

    int Foo::Foo(void);

}
it is better to write:=20

class Foo
{

    int Foo(void);

}
Kind regards,
Igor
  ----- Original Message -----=20
  From: Alexey Zubko=20
  To: Igor Seleznev=20
  Cc: qui...@li...=20
  Sent: Wednesday, May 24, 2006 8:24 PM
  Subject: Re: [Quickfix-developers] linux compilation


  Hi Igor,

  Thanks a lot.
  I deleted that directory and bootstrap and configure passed Ok.
  Now I crash during the compilation:

   g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I. -I.. -I../.. -g -O2 =
-I/usr/include/libxml2 -MT DataDictionary.lo -MD -MP -MF ..deps/D        =
                      ataDictionary.Tpo -c DataDictionary.cpp  -fPIC =
-DPIC -o .libs/DataDictionary.o
  LIBXML_DOMDocument.h:45: error: extra qualification =
'FIX::LIBXML_DOMAttributes::' on member 'toMap'
  make[4]: *** [DataDictionary.lo] Error 1
  make[4]: Leaving directory `/home/alexey/workspace/quickfix/src/C++'
  make[3]: *** [all-recursive] Error 1
  make[3]: Leaving directory `/home/alexey/workspace/quickfix/src/C++'
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory `/home/alexey/workspace/quickfix/src'
  make[1]: *** [all-recursive] Error 1
  make[1]: Leaving directory `/home/alexey/workspace/quickfix'
  make: *** [all] Error 2


  Does it mean I need to use another gcc version?
  BTW, what environment do you use for your projects?

  Thank you.


Regards,
		Alexey Zubko


  Igor Seleznev wrote:=20
    Hi,=20

    I have experienced some of your problems too.=20

    To fix the first one with 'bootstrap', please delete =
"quickfix/autom4te.cache". I noticed that one of quickfix tarballs =
contains it. I will file a bug about this issue.=20

    As for second one with 'missing' script, you can ignore it. =
Moreover, there was a case about it and it claimed to be fixed in HEAD.=20
    See:=20
    =
http://www.quickfixengine.org/bugtracker/bug.php?op=3Dshow&bugid=3D183&po=
s=3D0=20

    Most likely the last problem will be fixed when you fix the first =
two. From your logs it looks like that 'automake' cached into wrong =
location.=20
    If it doesn't help, perhaps it makes sense to run configure in debug =
mode (sh -x ./configure) and see what's wrong.=20

    Kind regards,=20
    Igor=20

    ----- Original Message ----- From: "Alexey Zubko" =
<ale...@gm...>=20
    To: <qui...@li...>=20
    Sent: Wednesday, May 24, 2006 7:34 PM=20
    Subject: [Quickfix-developers] linux compilation=20



      QuickFIX Documentation: =
http://www.quickfixengine.org/quickfix/doc/html/index.html=20
      QuickFIX Support: http://www.quickfixengine.org/services.html=20

      Hello guys,=20

      I want to compile quickfix in Linux, but unfortunately don't have =
such experience now.=20
      I know I need to learn a lot, but as a start could anyone help me, =
please?=20
      Does anyone use Eclipse CDT?=20
      Thank you in advance.=20

      So, I have Gentoo Linux with gcc 4.1.0 and quickfix 1.11.1=20

      # ./bootstrap=20
      aclocal...=20
      autoheader...=20
      Can't locate object method "path" via package "Request" at =
/usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.=20
      autoheader-2.59: /usr/bin/autom4te-2.59 failed with exit status: 1 =

      libtoolize...=20
      automake...=20
      Can't locate object method "path" via package "Request" at =
/usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.=20
      configure.in: no proper invocation of AM_INIT_AUTOMAKE was found.=20
      configure.in: You should verify that configure.in invokes =
AM_INIT_AUTOMAKE,=20
      configure.in: that aclocal.m4 is present in the top-level =
directory,=20
      configure.in: and that aclocal.m4 was recently regenerated (using =
aclocal).=20
      automake-1.7: no `Makefile.am' found or specified=20
      autoconf...=20
      Can't locate object method "path" via package "Request" at =
/usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.=20
      Now run configure with any arguments necessary=20

      After that:=20
      # ./configure=20
      checking for a BSD-compatible install... /usr/bin/install -c=20
      checking whether build environment is sane... yes=20
      /home/alexey/workspace/quickfix/missing: Unknown `--run' option=20
      Try `/home/alexey/workspace/quickfix/missing --help' for more =
information=20
      configure: WARNING: `missing' script is too old or missing=20
      checking for gawk... gawk=20
      checking whether make sets $(MAKE)... yes=20
      checking for g++... g++=20
      checking for C++ compiler default output... a.out=20
      checking whether the C++ compiler works... yes=20
      checking whether we are cross compiling... no=20
      checking for suffix of executables...=20
      checking for suffix of object files... o=20
      checking whether we are using the GNU C++ compiler... yes=20
      checking whether g++ accepts -g... yes=20
      checking for style of include used by make... GNU=20
      checking dependency style of g++... gcc3=20
      checking for gcc... gcc=20
      checking whether we are using the GNU C compiler... yes=20
      checking whether gcc accepts -g... yes=20
      checking for gcc option to accept ANSI C... none needed=20
      checking dependency style of gcc... gcc3=20
      checking build system type... i686-pc-linux-gnu=20
      checking host system type... i686-pc-linux-gnu=20
      checking for a sed that does not truncate output... /usr/bin/sed=20
      checking for egrep... grep -E=20
      checking for ld used by gcc... /usr/i686-pc-linux-gnu/bin/ld=20
      checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU =
ld... yes=20
      checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object =
files... -r=20
      checking for BSD-compatible nm... /usr/bin/nm -B=20
      checking whether ln -s works... yes=20
      checking how to recognise dependent libraries... pass_all=20
      checking how to run the C preprocessor... gcc -E=20
      checking for ANSI C header files... yes=20
      checking for sys/types.h... yes=20
      checking for sys/stat.h... yes=20
      checking for stdlib.h... yes=20
      checking for string.h... yes=20
      checking for memory.h... yes=20
      checking for strings.h... yes=20
      checking for inttypes.h... yes=20
      checking for stdint.h... yes=20
      checking for unistd.h... yes=20
      checking dlfcn.h usability... yes=20
      checking dlfcn.h presence... yes=20
      checking for dlfcn.h... yes=20
      checking how to run the C++ preprocessor... g++ -E=20
      checking for g77... no=20
      checking for f77... no=20
      checking for xlf... no=20
      checking for frt... no=20
      checking for pgf77... no=20
      checking for fl32... no=20
      checking for af77... no=20
      checking for fort77... no=20
      checking for f90... no=20
      checking for xlf90... no=20
      checking for pgf90... no=20
      checking for epcf90... no=20
      checking for f95... no=20
      checking for fort... no=20
      checking for xlf95... no=20
      checking for lf95... no=20
      checking for g95... no=20
      checking whether we are using the GNU Fortran 77 compiler... no=20
      checking whether  accepts -g... no=20
      checking the maximum length of command line arguments... 32768=20
      checking command to parse /usr/bin/nm -B output from gcc object... =
ok=20
      checking for objdir... .libs=20
      checking for ar... ar=20
      checking for ranlib... ranlib=20
      checking for strip... strip=20
      checking if gcc static flag  works... yes=20
      checking if gcc supports -fno-rtti -fno-exceptions... no=20
      checking for gcc option to produce PIC... -fPIC=20
      checking if gcc PIC flag -fPIC works... yes=20
      checking if gcc supports -c -o file.o... yes=20
      checking whether the gcc linker (/usr/i686-pc-linux-gnu/bin/ld) =
supports shared libraries... yes=20
      checking whether -lc should be explicitly linked in... no=20
      checking dynamic linker characteristics... GNU/Linux ld.so=20
      checking how to hardcode library paths into programs... immediate=20
      checking whether stripping libraries is possible... yes=20
      checking if libtool supports shared libraries... yes=20
      checking whether to build shared libraries... yes=20
      checking whether to build static libraries... no=20
      configure: creating libtool=20
      appending configuration tag "CXX" to libtool=20
      checking for ld used by g++... /usr/i686-pc-linux-gnu/bin/ld=20
      checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU =
ld... yes=20
      checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) =
supports shared libraries... yes=20
      checking for g++ option to produce PIC... -fPIC=20
      checking if g++ PIC flag -fPIC works... yes=20
      checking if g++ supports -c -o file.o... yes=20
      checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) =
supports shared libraries... yes=20
      checking dynamic linker characteristics... GNU/Linux ld.so=20
      checking how to hardcode library paths into programs... immediate=20
      checking whether stripping libraries is possible... yes=20
      appending configuration tag "F77" to libtool=20
      checking for flex... flex=20
      checking for yywrap in -lfl... yes=20
      checking lex output file root... lex.yy=20
      checking whether yytext is a pointer... yes=20
      .../configure: line 19059: ruby: command not found=20
      checking for xml2-config... /usr/bin/xml2-config=20
      checking for libxml - version >=3D 2.0.0... yes (version 2.6.23)=20
      checking for shutdown in -lc... yes=20
      checking for inet_addr in -lc... yes=20
      checking for nanosleep in -lc... yes=20
      checking for ftime in -lcompat... no=20
      checking which threading environment to use... -lpthread=20
      checking for pthread_create in -lpthread... yes=20
      checking stdio.h usability... yes=20
      checking stdio.h presence... yes=20
      checking for stdio.h... yes=20
      checking for STREAMS ioctl... no=20
      checking for socklen_t... yes=20
      checking for ftime... yes=20
      checking for set_terminate in the global namespace... no=20
      checking for set_terminate in the std namespace... yes=20
      checking for typeinfo in the global namespace... no=20
      checking for typeinfo in the std namespace... yes=20
      checking for gethostbyname_r with input result... yes=20
      checking for gethostbyname_r with return result... no=20
      checking for cplus_demangle in -liberty... yes=20
      checking if select modifies timeval parameter... yes=20
      configure: creating ./config.status=20
      config.status: creating quickfix.pc=20
      config.status: creating Makefile=20
      config.status: creating src/Makefile=20
      config.status: creating src/C++/Makefile=20
      config.status: creating src/C++/test/Makefile=20
      config.status: creating src/java/Makefile=20
      config.status: creating src/java/cfg/Makefile=20
      config.status: creating src/java/src/Makefile=20
      config.status: creating src/java/src/quickfix/Makefile=20
      config.status: creating src/java/src/quickfix/field/Makefile=20
      config.status: creating src/java/src/quickfix/fix40/Makefile=20
      config.status: creating src/java/src/quickfix/fix41/Makefile=20
      config.status: creating src/java/src/quickfix/fix42/Makefile=20
      config.status: creating src/java/src/quickfix/fix43/Makefile=20
      config.status: creating src/java/src/quickfix/fix44/Makefile=20
      config.status: creating src/python/Makefile=20
      config.status: creating bin/Makefile=20
      config.status: creating bin/cfg/Makefile=20
      config.status: creating spec/Makefile=20
      config.status: creating test/Makefile=20
      config.status: creating test/atrun/Makefile=20
      config.status: creating test/cfg/Makefile=20
      config.status: creating test/definitions/Makefile=20
      config.status: creating test/definitions/server/Makefile=20
      config.status: creating test/definitions/server/future/Makefile=20
      config.status: creating examples/Makefile=20
      config.status: creating examples/executor/Makefile=20
      config.status: creating examples/executor/C++/Makefile=20
      config.status: creating examples/executor/java/Makefile=20
      config.status: creating examples/executor/java/src/Makefile=20
      config.status: creating examples/ordermatch/Makefile=20
      config.status: creating examples/ordermatch/test/Makefile=20
      config.status: creating examples/tradeclient/Makefile=20
      config.status: creating examples/tradeclientgui/Makefile=20
      config.status: creating examples/tradeclientgui/banzai/Makefile=20
      config.status: creating =
examples/tradeclientgui/banzai/test/Makefile=20
      config.status: creating =
examples/tradeclientgui/banzai/src/Makefile=20
      config.status: creating =
examples/tradeclientgui/banzai/src/quickfix/Makefile=20
      config.status: creating =
examples/tradeclientgui/banzai/src/quickfix/banzai/Makefile=20
      config.status: creating =
examples/tradeclientgui/banzai/src/quickfix/banzai/ui/Makefile=20
      config.status: creating doc/Makefile=20
      config.status: creating doc/html/Makefile=20
      config.status: creating CPPTest/Makefile=20
      config.status: creating config.h=20
      config.status: config.h is unchanged=20
      config.status: executing depfiles commands=20

      # make=20
      cd . && \=20
        --foreign  Makefile=20
      /bin/sh: --foreign: command not found=20
      make: *** [Makefile.in] Error 127=20



      --=20
      Regards,=20
      Alexey Zubko=20



      -------------------------------------------------------=20
      All the advantages of Linux Managed Hosting--Without the Cost and =
Risk!=20
      Fully trained technicians. The highest number of Red Hat =
certifications in=20
      the hosting industry. Fanatical Support. Click to learn more=20
      =
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D107521&bid=3D248729&dat=3D=
121642=20
      _______________________________________________=20
      Quickfix-developers mailing list=20
      Qui...@li...=20
      https://lists.sourceforge.net/lists/listinfo/quickfix-developers=20

Re: [Quickfix-developers] linux compilation

[Alexey Z. <ale...@gm...>]

Hi Igor,

Thanks a lot.
I deleted that directory and bootstrap and configure passed Ok.
Now I crash during the compilation:

 g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I. -I.. -I../.. -g -O2 
-I/usr/include/libxml2 -MT DataDictionary.lo -MD -MP -MF 
.deps/D                              ataDictionary.Tpo -c 
DataDictionary.cpp  -fPIC -DPIC -o .libs/DataDictionary.o
LIBXML_DOMDocument.h:45: error: extra qualification 
'FIX::LIBXML_DOMAttributes::' on member 'toMap'
make[4]: *** [DataDictionary.lo] Error 1
make[4]: Leaving directory `/home/alexey/workspace/quickfix/src/C++'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/alexey/workspace/quickfix/src/C++'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/alexey/workspace/quickfix/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/alexey/workspace/quickfix'
make: *** [all] Error 2


Does it mean I need to use another gcc version?
BTW, what environment do you use for your projects?

Thank you.

Regards,
		Alexey Zubko



Igor Seleznev wrote:
> Hi,
>
> I have experienced some of your problems too.
>
> To fix the first one with 'bootstrap', please delete 
> "quickfix/autom4te.cache". I noticed that one of quickfix tarballs 
> contains it. I will file a bug about this issue.
>
> As for second one with 'missing' script, you can ignore it. Moreover, 
> there was a case about it and it claimed to be fixed in HEAD.
> See:
> http://www.quickfixengine.org/bugtracker/bug.php?op=show&bugid=183&pos=0
>
> Most likely the last problem will be fixed when you fix the first two. 
> From your logs it looks like that 'automake' cached into wrong location.
> If it doesn't help, perhaps it makes sense to run configure in debug 
> mode (sh -x ./configure) and see what's wrong.
>
> Kind regards,
> Igor
>
> ----- Original Message ----- From: "Alexey Zubko" 
> <ale...@gm...>
> To: <qui...@li...>
> Sent: Wednesday, May 24, 2006 7:34 PM
> Subject: [Quickfix-developers] linux compilation
>
>
>> QuickFIX Documentation: 
>> http://www.quickfixengine.org/quickfix/doc/html/index.html
>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>
>> Hello guys,
>>
>> I want to compile quickfix in Linux, but unfortunately don't have 
>> such experience now.
>> I know I need to learn a lot, but as a start could anyone help me, 
>> please?
>> Does anyone use Eclipse CDT?
>> Thank you in advance.
>>
>> So, I have Gentoo Linux with gcc 4.1.0 and quickfix 1.11.1
>>
>> # ./bootstrap
>> aclocal...
>> autoheader...
>> Can't locate object method "path" via package "Request" at 
>> /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
>> autoheader-2.59: /usr/bin/autom4te-2.59 failed with exit status: 1
>> libtoolize...
>> automake...
>> Can't locate object method "path" via package "Request" at 
>> /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
>> configure.in: no proper invocation of AM_INIT_AUTOMAKE was found.
>> configure.in: You should verify that configure.in invokes 
>> AM_INIT_AUTOMAKE,
>> configure.in: that aclocal.m4 is present in the top-level directory,
>> configure.in: and that aclocal.m4 was recently regenerated (using 
>> aclocal).
>> automake-1.7: no `Makefile.am' found or specified
>> autoconf...
>> Can't locate object method "path" via package "Request" at 
>> /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
>> Now run configure with any arguments necessary
>>
>> After that:
>> # ./configure
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> /home/alexey/workspace/quickfix/missing: Unknown `--run' option
>> Try `/home/alexey/workspace/quickfix/missing --help' for more 
>> information
>> configure: WARNING: `missing' script is too old or missing
>> checking for gawk... gawk
>> checking whether make sets $(MAKE)... yes
>> checking for g++... g++
>> checking for C++ compiler default output... a.out
>> checking whether the C++ compiler works... yes
>> checking whether we are cross compiling... no
>> checking for suffix of executables...
>> checking for suffix of object files... o
>> checking whether we are using the GNU C++ compiler... yes
>> checking whether g++ accepts -g... yes
>> checking for style of include used by make... GNU
>> checking dependency style of g++... gcc3
>> checking for gcc... gcc
>> checking whether we are using the GNU C compiler... yes
>> checking whether gcc accepts -g... yes
>> checking for gcc option to accept ANSI C... none needed
>> checking dependency style of gcc... gcc3
>> checking build system type... i686-pc-linux-gnu
>> checking host system type... i686-pc-linux-gnu
>> checking for a sed that does not truncate output... /usr/bin/sed
>> checking for egrep... grep -E
>> checking for ld used by gcc... /usr/i686-pc-linux-gnu/bin/ld
>> checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
>> checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object 
>> files... -r
>> checking for BSD-compatible nm... /usr/bin/nm -B
>> checking whether ln -s works... yes
>> checking how to recognise dependent libraries... pass_all
>> checking how to run the C preprocessor... gcc -E
>> checking for ANSI C header files... yes
>> checking for sys/types.h... yes
>> checking for sys/stat.h... yes
>> checking for stdlib.h... yes
>> checking for string.h... yes
>> checking for memory.h... yes
>> checking for strings.h... yes
>> checking for inttypes.h... yes
>> checking for stdint.h... yes
>> checking for unistd.h... yes
>> checking dlfcn.h usability... yes
>> checking dlfcn.h presence... yes
>> checking for dlfcn.h... yes
>> checking how to run the C++ preprocessor... g++ -E
>> checking for g77... no
>> checking for f77... no
>> checking for xlf... no
>> checking for frt... no
>> checking for pgf77... no
>> checking for fl32... no
>> checking for af77... no
>> checking for fort77... no
>> checking for f90... no
>> checking for xlf90... no
>> checking for pgf90... no
>> checking for epcf90... no
>> checking for f95... no
>> checking for fort... no
>> checking for xlf95... no
>> checking for lf95... no
>> checking for g95... no
>> checking whether we are using the GNU Fortran 77 compiler... no
>> checking whether  accepts -g... no
>> checking the maximum length of command line arguments... 32768
>> checking command to parse /usr/bin/nm -B output from gcc object... ok
>> checking for objdir... .libs
>> checking for ar... ar
>> checking for ranlib... ranlib
>> checking for strip... strip
>> checking if gcc static flag  works... yes
>> checking if gcc supports -fno-rtti -fno-exceptions... no
>> checking for gcc option to produce PIC... -fPIC
>> checking if gcc PIC flag -fPIC works... yes
>> checking if gcc supports -c -o file.o... yes
>> checking whether the gcc linker (/usr/i686-pc-linux-gnu/bin/ld) 
>> supports shared libraries... yes
>> checking whether -lc should be explicitly linked in... no
>> checking dynamic linker characteristics... GNU/Linux ld.so
>> checking how to hardcode library paths into programs... immediate
>> checking whether stripping libraries is possible... yes
>> checking if libtool supports shared libraries... yes
>> checking whether to build shared libraries... yes
>> checking whether to build static libraries... no
>> configure: creating libtool
>> appending configuration tag "CXX" to libtool
>> checking for ld used by g++... /usr/i686-pc-linux-gnu/bin/ld
>> checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
>> checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) 
>> supports shared libraries... yes
>> checking for g++ option to produce PIC... -fPIC
>> checking if g++ PIC flag -fPIC works... yes
>> checking if g++ supports -c -o file.o... yes
>> checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) 
>> supports shared libraries... yes
>> checking dynamic linker characteristics... GNU/Linux ld.so
>> checking how to hardcode library paths into programs... immediate
>> checking whether stripping libraries is possible... yes
>> appending configuration tag "F77" to libtool
>> checking for flex... flex
>> checking for yywrap in -lfl... yes
>> checking lex output file root... lex.yy
>> checking whether yytext is a pointer... yes
>> ../configure: line 19059: ruby: command not found
>> checking for xml2-config... /usr/bin/xml2-config
>> checking for libxml - version >= 2.0.0... yes (version 2.6.23)
>> checking for shutdown in -lc... yes
>> checking for inet_addr in -lc... yes
>> checking for nanosleep in -lc... yes
>> checking for ftime in -lcompat... no
>> checking which threading environment to use... -lpthread
>> checking for pthread_create in -lpthread... yes
>> checking stdio.h usability... yes
>> checking stdio.h presence... yes
>> checking for stdio.h... yes
>> checking for STREAMS ioctl... no
>> checking for socklen_t... yes
>> checking for ftime... yes
>> checking for set_terminate in the global namespace... no
>> checking for set_terminate in the std namespace... yes
>> checking for typeinfo in the global namespace... no
>> checking for typeinfo in the std namespace... yes
>> checking for gethostbyname_r with input result... yes
>> checking for gethostbyname_r with return result... no
>> checking for cplus_demangle in -liberty... yes
>> checking if select modifies timeval parameter... yes
>> configure: creating ./config.status
>> config.status: creating quickfix.pc
>> config.status: creating Makefile
>> config.status: creating src/Makefile
>> config.status: creating src/C++/Makefile
>> config.status: creating src/C++/test/Makefile
>> config.status: creating src/java/Makefile
>> config.status: creating src/java/cfg/Makefile
>> config.status: creating src/java/src/Makefile
>> config.status: creating src/java/src/quickfix/Makefile
>> config.status: creating src/java/src/quickfix/field/Makefile
>> config.status: creating src/java/src/quickfix/fix40/Makefile
>> config.status: creating src/java/src/quickfix/fix41/Makefile
>> config.status: creating src/java/src/quickfix/fix42/Makefile
>> config.status: creating src/java/src/quickfix/fix43/Makefile
>> config.status: creating src/java/src/quickfix/fix44/Makefile
>> config.status: creating src/python/Makefile
>> config.status: creating bin/Makefile
>> config.status: creating bin/cfg/Makefile
>> config.status: creating spec/Makefile
>> config.status: creating test/Makefile
>> config.status: creating test/atrun/Makefile
>> config.status: creating test/cfg/Makefile
>> config.status: creating test/definitions/Makefile
>> config.status: creating test/definitions/server/Makefile
>> config.status: creating test/definitions/server/future/Makefile
>> config.status: creating examples/Makefile
>> config.status: creating examples/executor/Makefile
>> config.status: creating examples/executor/C++/Makefile
>> config.status: creating examples/executor/java/Makefile
>> config.status: creating examples/executor/java/src/Makefile
>> config.status: creating examples/ordermatch/Makefile
>> config.status: creating examples/ordermatch/test/Makefile
>> config.status: creating examples/tradeclient/Makefile
>> config.status: creating examples/tradeclientgui/Makefile
>> config.status: creating examples/tradeclientgui/banzai/Makefile
>> config.status: creating examples/tradeclientgui/banzai/test/Makefile
>> config.status: creating examples/tradeclientgui/banzai/src/Makefile
>> config.status: creating 
>> examples/tradeclientgui/banzai/src/quickfix/Makefile
>> config.status: creating 
>> examples/tradeclientgui/banzai/src/quickfix/banzai/Makefile
>> config.status: creating 
>> examples/tradeclientgui/banzai/src/quickfix/banzai/ui/Makefile
>> config.status: creating doc/Makefile
>> config.status: creating doc/html/Makefile
>> config.status: creating CPPTest/Makefile
>> config.status: creating config.h
>> config.status: config.h is unchanged
>> config.status: executing depfiles commands
>>
>> # make
>> cd . && \
>>   --foreign  Makefile
>> /bin/sh: --foreign: command not found
>> make: *** [Makefile.in] Error 127
>>
>>
>>
>> -- 
>> Regards,
>> Alexey Zubko
>>
>>
>>
>> -------------------------------------------------------
>> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
>> Fully trained technicians. The highest number of Red Hat 
>> certifications in
>> the hosting industry. Fanatical Support. Click to learn more
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
>> _______________________________________________
>> Quickfix-developers mailing list
>> Qui...@li...
>> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>>
>
>

Re: [Quickfix-developers] linux compilation

[Igor S. <se...@ma...>]

Sorry, mistyped.
Should be "quickfix/aclocal.m4".

----- Original Message ----- 
From: "Igor Seleznev" <se...@ma...>
To: "Alexey Zubko" <ale...@gm...>; 
<qui...@li...>
Sent: Wednesday, May 24, 2006 8:02 PM
Subject: Re: [Quickfix-developers] linux compilation


> Hi,
>
> I have experienced some of your problems too.
>
> To fix the first one with 'bootstrap', please delete 
> "quickfix/autom4te.cache". I noticed that one of quickfix tarballs 
> contains it. I will file a bug about this issue.
>
> As for second one with 'missing' script, you can ignore it. Moreover, 
> there was a case about it and it claimed to be fixed in HEAD.
> See:
> http://www.quickfixengine.org/bugtracker/bug.php?op=show&bugid=183&pos=0
>
> Most likely the last problem will be fixed when you fix the first two. 
> From your logs it looks like that 'automake' cached into wrong location.
> If it doesn't help, perhaps it makes sense to run configure in debug mode 
> (sh -x ./configure) and see what's wrong.
>
> Kind regards,
> Igor
>
> ----- Original Message ----- 
> From: "Alexey Zubko" <ale...@gm...>
> To: <qui...@li...>
> Sent: Wednesday, May 24, 2006 7:34 PM
> Subject: [Quickfix-developers] linux compilation
>
>
>> QuickFIX Documentation: 
>> http://www.quickfixengine.org/quickfix/doc/html/index.html
>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>
>> Hello guys,
>>
>> I want to compile quickfix in Linux, but unfortunately don't have such 
>> experience now.
>> I know I need to learn a lot, but as a start could anyone help me, 
>> please?
>> Does anyone use Eclipse CDT?
>> Thank you in advance.
>>
>> So, I have Gentoo Linux with gcc 4.1.0 and quickfix 1.11.1
>>
>> # ./bootstrap
>> aclocal...
>> autoheader...
>> Can't locate object method "path" via package "Request" at 
>> /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
>> autoheader-2.59: /usr/bin/autom4te-2.59 failed with exit status: 1
>> libtoolize...
>> automake...
>> Can't locate object method "path" via package "Request" at 
>> /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
>> configure.in: no proper invocation of AM_INIT_AUTOMAKE was found.
>> configure.in: You should verify that configure.in invokes 
>> AM_INIT_AUTOMAKE,
>> configure.in: that aclocal.m4 is present in the top-level directory,
>> configure.in: and that aclocal.m4 was recently regenerated (using 
>> aclocal).
>> automake-1.7: no `Makefile.am' found or specified
>> autoconf...
>> Can't locate object method "path" via package "Request" at 
>> /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
>> Now run configure with any arguments necessary
>>
>> After that:
>> # ./configure
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> /home/alexey/workspace/quickfix/missing: Unknown `--run' option
>> Try `/home/alexey/workspace/quickfix/missing --help' for more information
>> configure: WARNING: `missing' script is too old or missing
>> checking for gawk... gawk
>> checking whether make sets $(MAKE)... yes
>> checking for g++... g++
>> checking for C++ compiler default output... a.out
>> checking whether the C++ compiler works... yes
>> checking whether we are cross compiling... no
>> checking for suffix of executables...
>> checking for suffix of object files... o
>> checking whether we are using the GNU C++ compiler... yes
>> checking whether g++ accepts -g... yes
>> checking for style of include used by make... GNU
>> checking dependency style of g++... gcc3
>> checking for gcc... gcc
>> checking whether we are using the GNU C compiler... yes
>> checking whether gcc accepts -g... yes
>> checking for gcc option to accept ANSI C... none needed
>> checking dependency style of gcc... gcc3
>> checking build system type... i686-pc-linux-gnu
>> checking host system type... i686-pc-linux-gnu
>> checking for a sed that does not truncate output... /usr/bin/sed
>> checking for egrep... grep -E
>> checking for ld used by gcc... /usr/i686-pc-linux-gnu/bin/ld
>> checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
>> checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object 
>> files... -r
>> checking for BSD-compatible nm... /usr/bin/nm -B
>> checking whether ln -s works... yes
>> checking how to recognise dependent libraries... pass_all
>> checking how to run the C preprocessor... gcc -E
>> checking for ANSI C header files... yes
>> checking for sys/types.h... yes
>> checking for sys/stat.h... yes
>> checking for stdlib.h... yes
>> checking for string.h... yes
>> checking for memory.h... yes
>> checking for strings.h... yes
>> checking for inttypes.h... yes
>> checking for stdint.h... yes
>> checking for unistd.h... yes
>> checking dlfcn.h usability... yes
>> checking dlfcn.h presence... yes
>> checking for dlfcn.h... yes
>> checking how to run the C++ preprocessor... g++ -E
>> checking for g77... no
>> checking for f77... no
>> checking for xlf... no
>> checking for frt... no
>> checking for pgf77... no
>> checking for fl32... no
>> checking for af77... no
>> checking for fort77... no
>> checking for f90... no
>> checking for xlf90... no
>> checking for pgf90... no
>> checking for epcf90... no
>> checking for f95... no
>> checking for fort... no
>> checking for xlf95... no
>> checking for lf95... no
>> checking for g95... no
>> checking whether we are using the GNU Fortran 77 compiler... no
>> checking whether  accepts -g... no
>> checking the maximum length of command line arguments... 32768
>> checking command to parse /usr/bin/nm -B output from gcc object... ok
>> checking for objdir... .libs
>> checking for ar... ar
>> checking for ranlib... ranlib
>> checking for strip... strip
>> checking if gcc static flag  works... yes
>> checking if gcc supports -fno-rtti -fno-exceptions... no
>> checking for gcc option to produce PIC... -fPIC
>> checking if gcc PIC flag -fPIC works... yes
>> checking if gcc supports -c -o file.o... yes
>> checking whether the gcc linker (/usr/i686-pc-linux-gnu/bin/ld) supports 
>> shared libraries... yes
>> checking whether -lc should be explicitly linked in... no
>> checking dynamic linker characteristics... GNU/Linux ld.so
>> checking how to hardcode library paths into programs... immediate
>> checking whether stripping libraries is possible... yes
>> checking if libtool supports shared libraries... yes
>> checking whether to build shared libraries... yes
>> checking whether to build static libraries... no
>> configure: creating libtool
>> appending configuration tag "CXX" to libtool
>> checking for ld used by g++... /usr/i686-pc-linux-gnu/bin/ld
>> checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
>> checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports 
>> shared libraries... yes
>> checking for g++ option to produce PIC... -fPIC
>> checking if g++ PIC flag -fPIC works... yes
>> checking if g++ supports -c -o file.o... yes
>> checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports 
>> shared libraries... yes
>> checking dynamic linker characteristics... GNU/Linux ld.so
>> checking how to hardcode library paths into programs... immediate
>> checking whether stripping libraries is possible... yes
>> appending configuration tag "F77" to libtool
>> checking for flex... flex
>> checking for yywrap in -lfl... yes
>> checking lex output file root... lex.yy
>> checking whether yytext is a pointer... yes
>> ../configure: line 19059: ruby: command not found
>> checking for xml2-config... /usr/bin/xml2-config
>> checking for libxml - version >= 2.0.0... yes (version 2.6.23)
>> checking for shutdown in -lc... yes
>> checking for inet_addr in -lc... yes
>> checking for nanosleep in -lc... yes
>> checking for ftime in -lcompat... no
>> checking which threading environment to use... -lpthread
>> checking for pthread_create in -lpthread... yes
>> checking stdio.h usability... yes
>> checking stdio.h presence... yes
>> checking for stdio.h... yes
>> checking for STREAMS ioctl... no
>> checking for socklen_t... yes
>> checking for ftime... yes
>> checking for set_terminate in the global namespace... no
>> checking for set_terminate in the std namespace... yes
>> checking for typeinfo in the global namespace... no
>> checking for typeinfo in the std namespace... yes
>> checking for gethostbyname_r with input result... yes
>> checking for gethostbyname_r with return result... no
>> checking for cplus_demangle in -liberty... yes
>> checking if select modifies timeval parameter... yes
>> configure: creating ./config.status
>> config.status: creating quickfix.pc
>> config.status: creating Makefile
>> config.status: creating src/Makefile
>> config.status: creating src/C++/Makefile
>> config.status: creating src/C++/test/Makefile
>> config.status: creating src/java/Makefile
>> config.status: creating src/java/cfg/Makefile
>> config.status: creating src/java/src/Makefile
>> config.status: creating src/java/src/quickfix/Makefile
>> config.status: creating src/java/src/quickfix/field/Makefile
>> config.status: creating src/java/src/quickfix/fix40/Makefile
>> config.status: creating src/java/src/quickfix/fix41/Makefile
>> config.status: creating src/java/src/quickfix/fix42/Makefile
>> config.status: creating src/java/src/quickfix/fix43/Makefile
>> config.status: creating src/java/src/quickfix/fix44/Makefile
>> config.status: creating src/python/Makefile
>> config.status: creating bin/Makefile
>> config.status: creating bin/cfg/Makefile
>> config.status: creating spec/Makefile
>> config.status: creating test/Makefile
>> config.status: creating test/atrun/Makefile
>> config.status: creating test/cfg/Makefile
>> config.status: creating test/definitions/Makefile
>> config.status: creating test/definitions/server/Makefile
>> config.status: creating test/definitions/server/future/Makefile
>> config.status: creating examples/Makefile
>> config.status: creating examples/executor/Makefile
>> config.status: creating examples/executor/C++/Makefile
>> config.status: creating examples/executor/java/Makefile
>> config.status: creating examples/executor/java/src/Makefile
>> config.status: creating examples/ordermatch/Makefile
>> config.status: creating examples/ordermatch/test/Makefile
>> config.status: creating examples/tradeclient/Makefile
>> config.status: creating examples/tradeclientgui/Makefile
>> config.status: creating examples/tradeclientgui/banzai/Makefile
>> config.status: creating examples/tradeclientgui/banzai/test/Makefile
>> config.status: creating examples/tradeclientgui/banzai/src/Makefile
>> config.status: creating 
>> examples/tradeclientgui/banzai/src/quickfix/Makefile
>> config.status: creating 
>> examples/tradeclientgui/banzai/src/quickfix/banzai/Makefile
>> config.status: creating 
>> examples/tradeclientgui/banzai/src/quickfix/banzai/ui/Makefile
>> config.status: creating doc/Makefile
>> config.status: creating doc/html/Makefile
>> config.status: creating CPPTest/Makefile
>> config.status: creating config.h
>> config.status: config.h is unchanged
>> config.status: executing depfiles commands
>>
>> # make
>> cd . && \
>>   --foreign  Makefile
>> /bin/sh: --foreign: command not found
>> make: *** [Makefile.in] Error 127
>>
>>
>>
>> -- 
>> Regards,
>> Alexey Zubko
>>
>>
>>
>> -------------------------------------------------------
>> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
>> Fully trained technicians. The highest number of Red Hat certifications 
>> in
>> the hosting industry. Fanatical Support. Click to learn more
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
>> _______________________________________________
>> Quickfix-developers mailing list
>> Qui...@li...
>> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>>
> 

Re: [Quickfix-developers] linux compilation

[Igor S. <se...@ma...>]

Hi,

I have experienced some of your problems too.

To fix the first one with 'bootstrap', please delete 
"quickfix/autom4te.cache". I noticed that one of quickfix tarballs contains 
it. I will file a bug about this issue.

As for second one with 'missing' script, you can ignore it. Moreover, there 
was a case about it and it claimed to be fixed in HEAD.
See:
http://www.quickfixengine.org/bugtracker/bug.php?op=show&bugid=183&pos=0

Most likely the last problem will be fixed when you fix the first two. From 
your logs it looks like that 'automake' cached into wrong location.
If it doesn't help, perhaps it makes sense to run configure in debug mode 
(sh -x ./configure) and see what's wrong.

Kind regards,
Igor

----- Original Message ----- 
From: "Alexey Zubko" <ale...@gm...>
To: <qui...@li...>
Sent: Wednesday, May 24, 2006 7:34 PM
Subject: [Quickfix-developers] linux compilation


> QuickFIX Documentation: 
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hello guys,
>
> I want to compile quickfix in Linux, but unfortunately don't have such 
> experience now.
> I know I need to learn a lot, but as a start could anyone help me, please?
> Does anyone use Eclipse CDT?
> Thank you in advance.
>
> So, I have Gentoo Linux with gcc 4.1.0 and quickfix 1.11.1
>
> # ./bootstrap
> aclocal...
> autoheader...
> Can't locate object method "path" via package "Request" at 
> /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
> autoheader-2.59: /usr/bin/autom4te-2.59 failed with exit status: 1
> libtoolize...
> automake...
> Can't locate object method "path" via package "Request" at 
> /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
> configure.in: no proper invocation of AM_INIT_AUTOMAKE was found.
> configure.in: You should verify that configure.in invokes 
> AM_INIT_AUTOMAKE,
> configure.in: that aclocal.m4 is present in the top-level directory,
> configure.in: and that aclocal.m4 was recently regenerated (using 
> aclocal).
> automake-1.7: no `Makefile.am' found or specified
> autoconf...
> Can't locate object method "path" via package "Request" at 
> /usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
> Now run configure with any arguments necessary
>
> After that:
> # ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> /home/alexey/workspace/quickfix/missing: Unknown `--run' option
> Try `/home/alexey/workspace/quickfix/missing --help' for more information
> configure: WARNING: `missing' script is too old or missing
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for g++... g++
> checking for C++ compiler default output... a.out
> checking whether the C++ compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking for style of include used by make... GNU
> checking dependency style of g++... gcc3
> checking for gcc... gcc
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking dependency style of gcc... gcc3
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for egrep... grep -E
> checking for ld used by gcc... /usr/i686-pc-linux-gnu/bin/ld
> checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
> checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object 
> files... -r
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking how to run the C++ preprocessor... g++ -E
> checking for g77... no
> checking for f77... no
> checking for xlf... no
> checking for frt... no
> checking for pgf77... no
> checking for fl32... no
> checking for af77... no
> checking for fort77... no
> checking for f90... no
> checking for xlf90... no
> checking for pgf90... no
> checking for epcf90... no
> checking for f95... no
> checking for fort... no
> checking for xlf95... no
> checking for lf95... no
> checking for g95... no
> checking whether we are using the GNU Fortran 77 compiler... no
> checking whether  accepts -g... no
> checking the maximum length of command line arguments... 32768
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for objdir... .libs
> checking for ar... ar
> checking for ranlib... ranlib
> checking for strip... strip
> checking if gcc static flag  works... yes
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC
> checking if gcc PIC flag -fPIC works... yes
> checking if gcc supports -c -o file.o... yes
> checking whether the gcc linker (/usr/i686-pc-linux-gnu/bin/ld) supports 
> shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by g++... /usr/i686-pc-linux-gnu/bin/ld
> checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
> checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports 
> shared libraries... yes
> checking for g++ option to produce PIC... -fPIC
> checking if g++ PIC flag -fPIC works... yes
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports 
> shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> appending configuration tag "F77" to libtool
> checking for flex... flex
> checking for yywrap in -lfl... yes
> checking lex output file root... lex.yy
> checking whether yytext is a pointer... yes
> ../configure: line 19059: ruby: command not found
> checking for xml2-config... /usr/bin/xml2-config
> checking for libxml - version >= 2.0.0... yes (version 2.6.23)
> checking for shutdown in -lc... yes
> checking for inet_addr in -lc... yes
> checking for nanosleep in -lc... yes
> checking for ftime in -lcompat... no
> checking which threading environment to use... -lpthread
> checking for pthread_create in -lpthread... yes
> checking stdio.h usability... yes
> checking stdio.h presence... yes
> checking for stdio.h... yes
> checking for STREAMS ioctl... no
> checking for socklen_t... yes
> checking for ftime... yes
> checking for set_terminate in the global namespace... no
> checking for set_terminate in the std namespace... yes
> checking for typeinfo in the global namespace... no
> checking for typeinfo in the std namespace... yes
> checking for gethostbyname_r with input result... yes
> checking for gethostbyname_r with return result... no
> checking for cplus_demangle in -liberty... yes
> checking if select modifies timeval parameter... yes
> configure: creating ./config.status
> config.status: creating quickfix.pc
> config.status: creating Makefile
> config.status: creating src/Makefile
> config.status: creating src/C++/Makefile
> config.status: creating src/C++/test/Makefile
> config.status: creating src/java/Makefile
> config.status: creating src/java/cfg/Makefile
> config.status: creating src/java/src/Makefile
> config.status: creating src/java/src/quickfix/Makefile
> config.status: creating src/java/src/quickfix/field/Makefile
> config.status: creating src/java/src/quickfix/fix40/Makefile
> config.status: creating src/java/src/quickfix/fix41/Makefile
> config.status: creating src/java/src/quickfix/fix42/Makefile
> config.status: creating src/java/src/quickfix/fix43/Makefile
> config.status: creating src/java/src/quickfix/fix44/Makefile
> config.status: creating src/python/Makefile
> config.status: creating bin/Makefile
> config.status: creating bin/cfg/Makefile
> config.status: creating spec/Makefile
> config.status: creating test/Makefile
> config.status: creating test/atrun/Makefile
> config.status: creating test/cfg/Makefile
> config.status: creating test/definitions/Makefile
> config.status: creating test/definitions/server/Makefile
> config.status: creating test/definitions/server/future/Makefile
> config.status: creating examples/Makefile
> config.status: creating examples/executor/Makefile
> config.status: creating examples/executor/C++/Makefile
> config.status: creating examples/executor/java/Makefile
> config.status: creating examples/executor/java/src/Makefile
> config.status: creating examples/ordermatch/Makefile
> config.status: creating examples/ordermatch/test/Makefile
> config.status: creating examples/tradeclient/Makefile
> config.status: creating examples/tradeclientgui/Makefile
> config.status: creating examples/tradeclientgui/banzai/Makefile
> config.status: creating examples/tradeclientgui/banzai/test/Makefile
> config.status: creating examples/tradeclientgui/banzai/src/Makefile
> config.status: creating 
> examples/tradeclientgui/banzai/src/quickfix/Makefile
> config.status: creating 
> examples/tradeclientgui/banzai/src/quickfix/banzai/Makefile
> config.status: creating 
> examples/tradeclientgui/banzai/src/quickfix/banzai/ui/Makefile
> config.status: creating doc/Makefile
> config.status: creating doc/html/Makefile
> config.status: creating CPPTest/Makefile
> config.status: creating config.h
> config.status: config.h is unchanged
> config.status: executing depfiles commands
>
> # make
> cd . && \
>   --foreign  Makefile
> /bin/sh: --foreign: command not found
> make: *** [Makefile.in] Error 127
>
>
>
> -- 
> Regards,
> Alexey Zubko
>
>
>
> -------------------------------------------------------
> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> Fully trained technicians. The highest number of Red Hat certifications in
> the hosting industry. Fanatical Support. Click to learn more
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 

[Quickfix-developers] linux compilation

[Alexey Z. <ale...@gm...>]

Hello guys,

I want to compile quickfix in Linux, but unfortunately don't have such 
experience now.
I know I need to learn a lot, but as a start could anyone help me, please?
Does anyone use Eclipse CDT?
Thank you in advance.

So, I have Gentoo Linux with gcc 4.1.0 and quickfix 1.11.1

# ./bootstrap
aclocal...
autoheader...
Can't locate object method "path" via package "Request" at 
/usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
autoheader-2.59: /usr/bin/autom4te-2.59 failed with exit status: 1
libtoolize...
automake...
Can't locate object method "path" via package "Request" at 
/usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
configure.in: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE,
configure.in: that aclocal.m4 is present in the top-level directory,
configure.in: and that aclocal.m4 was recently regenerated (using aclocal).
automake-1.7: no `Makefile.am' found or specified
autoconf...
Can't locate object method "path" via package "Request" at 
/usr/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 111.
Now run configure with any arguments necessary

After that:
# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/home/alexey/workspace/quickfix/missing: Unknown `--run' option
Try `/home/alexey/workspace/quickfix/missing --help' for more information
configure: WARNING: `missing' script is too old or missing
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for g++... g++
checking for C++ compiler default output... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /usr/bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object 
files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fl32... no
checking for af77... no
checking for fort77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for lf95... no
checking for g95... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag  works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/i686-pc-linux-gnu/bin/ld) supports 
shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports 
shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports 
shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking for flex... flex
checking for yywrap in -lfl... yes
checking lex output file root... lex.yy
checking whether yytext is a pointer... yes
./configure: line 19059: ruby: command not found
checking for xml2-config... /usr/bin/xml2-config
checking for libxml - version >= 2.0.0... yes (version 2.6.23)
checking for shutdown in -lc... yes
checking for inet_addr in -lc... yes
checking for nanosleep in -lc... yes
checking for ftime in -lcompat... no
checking which threading environment to use... -lpthread
checking for pthread_create in -lpthread... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for STREAMS ioctl... no
checking for socklen_t... yes
checking for ftime... yes
checking for set_terminate in the global namespace... no
checking for set_terminate in the std namespace... yes
checking for typeinfo in the global namespace... no
checking for typeinfo in the std namespace... yes
checking for gethostbyname_r with input result... yes
checking for gethostbyname_r with return result... no
checking for cplus_demangle in -liberty... yes
checking if select modifies timeval parameter... yes
configure: creating ./config.status
config.status: creating quickfix.pc
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/C++/Makefile
config.status: creating src/C++/test/Makefile
config.status: creating src/java/Makefile
config.status: creating src/java/cfg/Makefile
config.status: creating src/java/src/Makefile
config.status: creating src/java/src/quickfix/Makefile
config.status: creating src/java/src/quickfix/field/Makefile
config.status: creating src/java/src/quickfix/fix40/Makefile
config.status: creating src/java/src/quickfix/fix41/Makefile
config.status: creating src/java/src/quickfix/fix42/Makefile
config.status: creating src/java/src/quickfix/fix43/Makefile
config.status: creating src/java/src/quickfix/fix44/Makefile
config.status: creating src/python/Makefile
config.status: creating bin/Makefile
config.status: creating bin/cfg/Makefile
config.status: creating spec/Makefile
config.status: creating test/Makefile
config.status: creating test/atrun/Makefile
config.status: creating test/cfg/Makefile
config.status: creating test/definitions/Makefile
config.status: creating test/definitions/server/Makefile
config.status: creating test/definitions/server/future/Makefile
config.status: creating examples/Makefile
config.status: creating examples/executor/Makefile
config.status: creating examples/executor/C++/Makefile
config.status: creating examples/executor/java/Makefile
config.status: creating examples/executor/java/src/Makefile
config.status: creating examples/ordermatch/Makefile
config.status: creating examples/ordermatch/test/Makefile
config.status: creating examples/tradeclient/Makefile
config.status: creating examples/tradeclientgui/Makefile
config.status: creating examples/tradeclientgui/banzai/Makefile
config.status: creating examples/tradeclientgui/banzai/test/Makefile
config.status: creating examples/tradeclientgui/banzai/src/Makefile
config.status: creating examples/tradeclientgui/banzai/src/quickfix/Makefile
config.status: creating 
examples/tradeclientgui/banzai/src/quickfix/banzai/Makefile
config.status: creating 
examples/tradeclientgui/banzai/src/quickfix/banzai/ui/Makefile
config.status: creating doc/Makefile
config.status: creating doc/html/Makefile
config.status: creating CPPTest/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands

# make
cd . && \
   --foreign  Makefile
/bin/sh: --foreign: command not found
make: *** [Makefile.in] Error 127



-- 
Regards,
		Alexey Zubko

[Quickfix-developers] [ANN] QuickFIX/J Project Announcement

[Steve B. <sb...@sm...>]

QuickFIX/J has moved to a new project home: www.quickfixj.org.=20
The project will still work closely with the QuickFIX team but=20
will be run independently. Some of the changes associated with=20
the move include:

* New home page (http://www.quickfixj.org) on a dedicated server
  sponsored by Smart Trade Technologies. This server will also
  support CruiseControl, Jira (issue tracking) and Confluence=20
  (wiki) servers.

* Subversion source code management - Hosted at SourceForge=20

    The quickfixj module of the QuickFIX CVS repository will no=20
    longer be used. The SourceForge project containing the
    Subversion repository is called 'quickfixj'.

* Issue/bug tracking and release management using Jira

    Bugs and feature requests should be submitted here instead of
    the PHPBugTracker application. You can access Jira from
    the QFJ home page. You can browse issues anonymously but
    will need to create an account to submit them. Creating an
    account will also allow to monitor the status of issues with
    email notifications.

* A community wiki using Confluence.=20

    I have placed some initial information on the wiki already=20
    but I'm looking for community involvement here. To add
    information to the wiki, you will need to create an account
    (to minimize spam on the site). However, you can browse
    the information anonymously.

* A quickfixj-users mailing list.=20

    I've decided to start with one mailing list for both user=20
    and development-related discussions. If the traffic or
    content becomes a problem, we can split the lists later.
    I'll also continue to monitor the quickfix-users and
    quickfix-developers list but QFJ-specific discussions
    should be directed on the QFJ list. See the support section
    of the web site (or go to the SourceForge project page) to
    sign up for the new list.

Regards,

Steve Bate
Smart Trade Technologies
http://www.smart-trade.net/

=20

[Quickfix-developers] [ANN] QuickFIX/J 1.0.0 final released

[Steve B. <sb...@sm...>]

I'm happy to announce the release of QuickFIX/J 1.0.0. It can be
downloaded from the new quickfixj SourceForge project site.

The following link will take you to the 1.0.0 downloads
at SourceForge.

Downloads: http://tinyurl.com/raoav

New Features and Improvements:
  * Compatability updates for QuickFIX JNI 1.11.1
  * Upgrade to MINA 0.9.
  * Feature #171 Allow variables in session settings
  * Performance improvements in the FileStore
  * New FileLog options for timestamps on messages (with optional=20
        milliseconds)
 =20
Bug Fixes:

  * Bug #170 DataDictionary field in Message not initialized
  * Bug #172 The message.clone() doesn't preserve group ordering
  * Bug #173 SessionSchedule improvements
  * Bug #179 Time-only presentation based on 1970. Patch by John
Hensley.
  * Bug #184 Added missing fields to ExecutionReport.
  * Fix for creation time storage in FileStore
  * Fixed session start/create time retrieval in JDBCStore

Any new bugs or features requests should be entered into the
QuickFIX/J issue tracker at http://www.quickfixj.org/jira. You
can create an account for yourself.

Steve Bate
Smart Trade Technologies
http://www.smart-trade.net/

[Quickfix-developers] How to know quickfix version

[Abel M. <am...@bo...>]

Hi,

Is there any function that returns a string with the library version, in =

order to show it on the beginning of the application? I was looking for=20
some version.h or similar, but i didn't find it. For us it would be very =

helpful, so with every application we could inmediatly know which=20
version of quickfix is using.

Regards,
Abel.



****************************** AVISO LEGAL =
******************************
La informaci=F3n contenida en este mensaje es para uso exclusivo de su =
destinatario. No debe copiarse, transmitirse a terceros ni guardarse por =
estos =FAltimos, salvo autorizaci=F3n del remitente.
Puede contener informaci=F3n confidencial o legalmente protegida cuyo =
r=E9gimen legal de utilizaci=F3n no se ve afectado por el hecho de que =
haya sido enviada por correo electr=F3nico.
Su env=EDo por error a una persona distinta de su destinatario real no =
implica que se haya modificado tal destinatario ni supone renuncia a su =
eventual car=E1cter confidencial o al r=E9gimen legal que rija su =
utilizaci=F3n.
Cualquier opini=F3n expresada en este mensaje vincular=E1 exclusivamente =
a la persona que lo haya remitido, excepto cuando el mensaje establezca =
lo contrario y el remitente est=E9 autorizado para establecer que dichas =
opiniones vincular=E1n a esta entidad.
En el supuesto de que este correo se recibiera por error, rogamos =
procedan a borrarlo, sin reenviarlo a terceros ni conservarlo en =
cualquier soporte y nos informen inmediatamente llamando al tel=E9fono =
34 91 5892123 o a la direcci=F3n de correo electr=F3nico remitente. =
Gracias.
****************************** DISCLAIMER ******************************
The information contained in this message is for the exclusive use of =
the named person. It can not be copied, transmitted to third parties or =
stored by the latter, except if authorised by the sender.
It may contain confidential or legally privileged information whose =
legal regime is not affected by the fact that this information has been =
sent by e-mail.=20
Its erroneous transmission to a person other than the real named person =
neither implies any modification of this named person nor a renunciation =
of the eventual confidentiality or legal regime affecting the use of =
concerned message.
Any views expressed in this message are binding exclusively upon the =
individual sender, except where the message states otherwise and the =
sender is authorised to bind this entity.=20
If you receive this message in error, please delete it without =
transmitting it to any third party or keeping it in any form and notify =
us immediately either by phone (34 91 5892123) or using the e- mail =
address of the sender. Thank You.