|
| From: | John W. Eaton |
| Subject: | [Octave-bug-tracker] [bug #49018] mxe-octave GNU/Linux native build: unable to link with Qscintilla |
| Date: | Fri, 9 Sep 2016 00:13:20 +0000 (UTC) |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 |
Follow-up Comment #11, bug #49018 (project octave):
Is there any other version of the libarary installed on the system in a
directory where the compiler/linker might be searching?
To see exactly the commands that the compiler front end executes, you can copy
the failed program text from the config.log file into a file, then run the
command that failed in a shell window, adding -v so that g++ will show you the
commands it executes. Maybe from that it will become apparent if there is
another library that the compiler/linker is using?
You can use nm on the libqscintilla2.a file to see whether it actually does
define the symbol. Something like
usr/bin/nm --demangle usr/i686-w64-mingw32/lib/libqscintilla2.a
in the top-level mxe-octave directory should do it.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49018>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |