When you compile m5 as a static library, e.g.
scons build/ALPHA_SE/libm5_prof.a
it doesn't compile gzstream into the library, nor does it link against
a separate gzstream library, making the m5 library unusable.
How can I make it compile gzstream?
-Derek
When you compile m5 as a static library, e.g.
scons build/ALPHA_SE/libm5_prof.a
it doesn't compile gzstream into the library, nor does it link against
a separate gzstream library, making the m5 library unusable.
How can I make it compile gzstream?
There should be a libgzstream.a in
On Fri, Aug 7, 2009 at 12:46 PM, nathan binkertn...@binkert.org wrote:
When you compile m5 as a static library, e.g.
scons build/ALPHA_SE/libm5_prof.a
it doesn't compile gzstream into the library, nor does it link against
a separate gzstream library, making the m5 library unusable.
How can
Command:
g++ -o bochs -I/u/d/r/drh5/mfacet/rocks
-I/u/d/r/drh5/mfacet/rocks/bochs
-I/u/d/r/drh5/mfacet/rocks/gem5/src/mem/ruby -DBX_WITH_RUBY=1
-DBX_241=1 -g -pg -O2 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES
-I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT
-DBX_SHARE_PATH=\/usr/local/share/bochs\
I think this is because of the ordering on the command line. If I
recall correctly, when two libraries depend on each other, the
providing library needs to be listed *after* the consuming library.
So you should put gzstream after m5.
This is because with static libs linked with -l, the linker
Well that is handy to know. Seems to do the trick. Thanks, Nate
So, now how can I get scons to build the gzstream library when you
specify a static library target?
On Fri, Aug 7, 2009 at 3:44 PM, nathan binkertn...@binkert.org wrote:
I think this is because of the ordering on the command
Well that is handy to know. Seems to do the trick. Thanks, Nate
So, now how can I get scons to build the gzstream library when you
specify a static library target?
Well, you can just specify gzstream as a target: build/gzstream/libgzstream.a
I think that the longer term solution is to just
