Need one global object constructed ahead of others

Question

We are working on porting an application from a Lynx
environment to Solaris using the Forte 6 development
tools. We're having a problem when a constructor for
one object tries to use a global object created in a
library file. The application uses an SLogFile class
to write warning messages to a particular destination.
This is specified in a source file called config.cpp like
so:
SLogFile _slog(fileno(stderr), SLogFile::warn);
SLogFile &slog = _slog;
config.cpp is compiled into config.o, which is then
stored in libclass.a.
In program testprog.cpp, we define a new class
whose constructor wants to use slog to write
output. I think the following simplification explains
what the application is trying to do.
extern SLogFile &slog;
class test {
public:
test(int val);
~test();
private:
int prival;
test::test(int val)
prival=val;
slog << "Initial value set to " << prival << "\n";
test testcritter;
int main(int argc, char** argv)
slog << "Count of arguments to main = " << argc << "\n";
return 0;
Through dbx, I can stop the program when it enters
test::test. slog points to slog, but slog is not
initialized. According to the documentation, this
can be resolved in g++ by the use of the load command
to get config.o loaded first (apparently getting _slog
constructed). Is there anyway to get this to happen
in the Solaris/Forte C++ environment?
Any help would be appreciated...

Answer 1

We are working on porting an application from a Lynx
environment to Solaris using the Forte 6 development
tools. We're having a problem when a constructor for
one object tries to use a global object created in a
library file. The application uses an SLogFile class
to write warning messages to a particular destination.
This is specified in a source file called config.cpp like
so:
SLogFile _slog(fileno(stderr), SLogFile::warn);
SLogFile &slog = _slog;
config.cpp is compiled into config.o, which is then
stored in libclass.a.
In program testprog.cpp, we define a new class
whose constructor wants to use slog to write
output. I think the following simplification explains
what the application is trying to do.
extern SLogFile &slog;
class test {
public:
test(int val);
~test();
private:
int prival;
test::test(int val)
prival=val;
slog << "Initial value set to " << prival << "\n";
test testcritter;
int main(int argc, char** argv)
slog << "Count of arguments to main = " << argc << "\n";
return 0;
Through dbx, I can stop the program when it enters
test::test. slog points to slog, but slog is not
initialized. According to the documentation, this
can be resolved in g++ by the use of the load command
to get config.o loaded first (apparently getting _slog
constructed). Is there anyway to get this to happen
in the Solaris/Forte C++ environment?
Any help would be appreciated...