Remote head created (please merge it away)

[John W. Eaton]

On 27-Aug-2011, Jordi Gutiérrez Hermoso wrote:

| I'm still having trouble building. It looks like not all symbols are
| getting read properly. When linking liboctinterp, there seem to be two
| symbols besides all the bsxfun_pow symbols I recently created that
| aren't being found. If I manually link to liboctave, that linker error
| goes away. What is happening here?

Do you have a previously installed copy of Octave using the same
prefix as you are currently using for building?

I also had a link problem with mixed integer-real bsxfun_pow symbols
but it went away when I deleted my previously installed version.  So
it seems that the linker was somehow looking in the installation
directories for liboctave instead of looking in the ../liboctave build
directory.

When I deleted the installed version, the linker apparently somehow
knows to look in the installation directory tree, because the symbols
are found?  Or, it is just ignoring the undefined symbols?  But why in
that case and not the other?  I'm a bit confused here.

I see that things work as I would expect when I explicitly add
../liboctave/liboctave.la and ../libcruft/libcruft.la to octave_LDADD
in src/Makefile.am.  Then libtool generates a command that includes
"../liboctave/.libs/liboctave.so ../libcruft/.libs/libcruft.so" and
the symbols are found from those files, not from my (possibly out of
date) installed version.

But I would just like this to work without having to specify multiple
levels of library dependencies.  If liboctinterp is linked to
everything that it needs, and the main Octave program only directly
calls functions from liboctinterp, shouldn't I be able to link with
liboctinterp only, and not have to know what other libraries
liboctinterp depends on?  It seems libtool should also know (or we
should be able to force it) to link to the uninstalled versions of the
dependent libraries instead of installed libraries.  But I don't see
how to do that.

| Also, LDFLAGS seem to be completely ignored, which is a problem I have
| been having earlier.

If I do

  make LDFLAGS=-foobar

I see "-foobar" added to the final link command.  Is that not working
for you, or is there some other problem with LDFLAGS that you are
seeing?

| Note that I deliberately branched here. It's a trivial to merge back
| the two heads on the default branch, but I was hoping you would do it
| while fixing the build problem I see. I made the extra head because
| that builds, but it doesn't build with your changes.

I merged since the build seems to be working for me now.

jwe