pschecklibs -force build does not work fresh after svn export

[Sebastian Jester]

Some Mac oddities require pschecklibs -force build to avoid problems during compilation, but one can't run this command fresh after an svn export because the psconfig.csh in export_dir/psconfig doesn't exist yet. However, in a way, forcing compilation of build tools only makes sense if it's the first thing that happens.

Some form of calling psbuild -dev is required before pschecklibs -force works. Do we need pschecklibs -dev?

This problem occurs on all platforms; our Linux version has an older autoconf than required by IPP, so I ran into it also on Linux.

[eugene]

fyi: the psbuild -bootstrap generates the psconfig.csh file. adding a -force option to psbuild might be helpful as well.

[Sebastian Jester]

I know, except psbuild -bootstrap generates a psconfig.csh in some system-global location, which I don't necessarily want to change. But psbuild -bootstrap /tmp is a workaround (maybe psbuild -bootstrap . works, too?)

Moreover, the trick with

unset D
unset U
etc.

is needed inside pschecklibs, too, to avoid the problems with libtool from ticket:1078 when pschecklibs is called directly from the command line and not by psbuild.