On Fri, Aug 7, 2009 at 12:46 PM, nathan binkert<[email protected]> 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 I make it compile gzstream? > There should be a libgzstream.a in build/gzstream/libgzstream.a. > You'll have to specify that in your final link stage along with > -lm5_foo
Yes, there should, but theres not. If you build the dynamic library libgzstream.a gets built, but when you build the static library this is the contents of build/gzstream: ale-01:rocks (64)% ls gem5/build/gzstream/ gzstream.cc@ gzstream.hh@ SConscript@ I also built the dynamic m5 library so that libgztream.a would be created, but linking against it doesn't fix the problem. > > The reason things are this way is because we build an intermediate > library for gzstream. We could instead just link gzstream.cc directly > into m5 (the binary, shared lib, and static lib) that would require > some scons hacking right now, but will be a lot easier once I finish > my other scons stuff. I can add it to my todo list if people would > prefer this. > > Nate > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
