e: Problem to use VFS modules

[Andrew Tridgell]

> Yes, but what about HPUX or Solaris or AIX or SCO Unix etc etc.
> The point is that all this knowledge is already in another
> program (libtool) and this should be used in preference to adding
> operating specific hacks to the Makefile.

I just wish the knowledge in libtool was separable. "libtool knows
best" seems to be its motto. I definately do not want to go the way
that the tng branch went with strange shell scripts launching stuff,
and making all of samba built using libtool.

If we can use libtool to separate out just the bits that need to be
compiled as pic, and the bits that create the .so then great. If doing
that means we have to completely change the way we build stuff then
forget it.

I suppose what I'd really like to see is two new scripts in the
source/scripts directory. One will take a .c and produce a .po that is
appropriate for making into a shareed library. The other will take a
bunch of .po files and generate a .so. Then we don't call libtool in
the Makefile, we call these scripts and if they use libtool to get the
job done then who cares.

And please, nobody ever create a ".libs" directory and try to hide
the bin/* executables behind shell scripts that do magic stuff. That
is just completely gross.

Cheers, Tridge