Ah, I had the same trouble under PPC Linux. The AbiWord_d binary links
up OK, but I get linking errors for the static version (something along
the lines of "in libstdc++ (filebuf.o): undefined reference to
__get_eh_context").
I commented out the static target in a Makefile deep in the bowels of
the tree. Is there a better way to do this? I was too worn out to tear
into the Makefile tree last night.
>> Then it compiles nicely and I get a linux .. bla bla dir but I dont get
>> a dist dir as I did in 0.5.5 what might be the cause?
>
>with 0.7.0 we build everything into abi/src/$os_..._{obj,dbg}/{bin,obj...}
>with the executables and a 'canonical' layout of the associated files
>(we're still tinkering with this too).
Man, when it got to the canonical part, it raised all sorts of holy hell.
Part of it was not finding the unixfonts directory where it was expecting
to find it -- I'd moved it to /opt/AbiSuite/fonts, thinking that it would
be a good place to keep a rapidly changing AbiSuite until things settle
down a bit -- but some of the error messages seem to imply other problems.
Finally(!), I moved the _d app to /opt/AbiSuite/bin/AbiWord, and attempted
to run it. It kept complaining about not finding fonts in /home/larry/fonts
(which is not surprising since that directory doesn't exist), even though
I had done xset and set ABIWORD_FONTDIR (or the actual env variable).
But yesterday, *anything* to do with Unix, both at work and at home, was
like pulling teeth. I'll give it another shot tonight. Any advice would
probably be useful.
Larry