> > > > However, one must make very sure that > > > > -DUTF8, and -lslang / -lslang-utf8 matches. > > > > > > Sounds okay, but you surely meant libslang-utf8.a and libslang.a > > > > > > > er... I didn't. > > Ah, we are talking about -pic ? > > No, we are talking about slang1-utf8-dev vs. slang1-dev. Both are needed > to the same time *to build* dbootstrap. I am not sure about library > reduction, does it care about SONAMEs and possible namespace conflicts? > If it does, -pic packages should also not conflict. When we have the > complete series of defaut and -utf8 applications, the whole thing will > be reduced correctly. My recent impression was, that mklibs.py looks in > the local directory first, then in the systemwide directory. If this is > correct, we could just copy the needed pic-lib to the build directory.
Note that, if we are talking about lib reduction, and shared library, we are not talking about libslang.a. We are talking about libslang-pic.a, and libslang-utf8-pic.a, and libslang.so symlink pointing to the appropriate slang lib. We don't really need the static library, static library is for building the static library with. regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]