Hi,
no specific order needed.
Unfortunately the object files (actually their names) for the same
source file are different in the apl build and in the libapl build.
Also the Makefiles and everything in .deps/
Therefore you always need a ./configure or ./configure --with-libapl
before each of the builds.
And a make clean or even make distclean before each ./configure is
always a good idea.
The complaints in make distclean are because distclean does not know
what was built beforehand, so it wants
to remove files that may belong to the other build.
The cleanest solution to all of this is to check out GNU APL into
different directories - one for apl and one for libapl.
/// Jürgen
On 01/29/2017 05:35 PM, enz...@gmx.com wrote:
is there a preferred order to compiling the apl binary and libapl
does doing one before the other deprive something of something? :) all file
sizes seem the exact same except of course libapl.h/.la/.so and bin/apl
depending on whether --with-libapl is used
i am doing the libapl first then the apl binary
---
make distclean gives a lot of
rm -f Makefile
make[2]: Leaving directory `/transfer/usr.src/apl/apl-866/src/testcases'
make[2]: Entering directory `/transfer/usr.src/apl/apl-866/src'
Makefile:901: .deps/apl-Archive.Po: No such file or directory
Makefile:902: .deps/apl-ArrayIterator.Po: No such file or directory
Makefile:903: .deps/apl-Assert.Po: No such file or directory
Makefile:904: .deps/apl-Avec.Po: No such file or directory
Makefile:905: .deps/apl-Backtrace.Po: No such file or directory
Makefile:906: .deps/apl-Bif_F12_FORMAT.Po: No such file or directory
....
i guess using make clean is the preferred way?
