[Octave-bug-tracker] [bug #45632] "make install" fails with "GraphicsMagick" built from source

[Mike Miller]

Update of bug #45632 (project octave):

                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #3:

@cto, no one is saying it's not a bug, just that we need more information to
know how to reproduce this or what's different about your setup. Maybe it's a
bug and maybe it's now. Carnë is simply saying that he frequently builds
GraphicsMagick from source and successfully installs Octave, so he doesn't hit
whatever problem you are encountering. So it's not as simple as saying Octave
doesn't support a custom-built GraphicsMagick.

I guess I would start by asking where does the path
/usr/packs/lib/libstdc++.la come from? Can you search your Octave build
directory to see if it appears anywhere? What about in the
/usr/packs/graphics_magick-1.3.21/lib directory?

If I had to guess, I would say it is in a *.la file somewhere. Whenever I see
these types of errors about missing libraries or extra library paths being
linked in, it is sometimes because of a .la file somewhere that libtool is
reading during the link stage. That's why most people delete *.la after doing
"make install". Do you have any .la files under /usr/packs? Does deleting them
make things better?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45632>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/