From: Albert Chin <gcc@lists.thewrittenword.com>
To: gcc@gcc.gnu.org
Subject: Building LyX 1.2.0 on HP-UX 11.11 with G++ 3.2
Date: Thu, 22 Aug 2002 05:31:00 -0000 [thread overview]
Message-ID: <20020822073107.A5468@oolong.il.thewrittenword.com> (raw)
I configured and built GCC 3.2 on hppa2.0w-hp-hpux11.11:
$ CC="cc -Ae +DAportable" ../configure --with-gnu-as \
--with-included-gettext --enable-shared
I then tried to build LyX 1.2.0, a C++ application and received errors
about unresolved symbols in the final link stage:
g++ -O2 -march=1.1 [.o files] mathed/.libs/libmathed.a
insets/.libs/libinsets.a frontends/.libs/libfrontends.a -lforms -lXpm
graphics/.libs/libgraphics.a support/.libs/libsupport.a
../sigc++/.libs/libsigc.a ../intl/libintl.a -lSM -lICE -lc -lm
-L/usr/lib/X11R6 -lX11
/usr/ccs/bin/ld: Unsatisfied symbols:
typeinfo name for MathStackrelInset(first referenced in
mathed/.libs/libmathed.a(formulabase.o)) (data)
ControlInset<InsetGraphics, InsetGraphicsParams>::updateSlot(bool)
(first referenced in frontends/.libs/libfrontends.a(Alert.o)) (code)
typeinfo name for InsetError(first referenced in
insets/.libs/libinsets.a(inset.o)) (data)
typeinfo name for InsetParent(first referenced in
insets/.libs/libinsets.a(inset.o)) (data)
...
$ cd /opt/build/lyx-1.2.0/src
$ nm -C libmathed.a | grep MathStackrelInset
U MathStackrelInset::MathStackrelInset()
...
00000000 T MathStackrelInset::MathStackrelInset()
00000000 T MathStackrelInset::MathStackrelInset()
00000000 t MathStackrelInset::~MathStackrelInset()
00000000 t MathStackrelInset::~MathStackrelInset()
00000000 T MathStackrelInset::draw(Painter&, int, int) const
00000000 T MathStackrelInset::clone() const
00000000 T MathStackrelInset::write(WriteStream&) const
00000000 T MathStackrelInset::metrics(MathMetricsInfo const&) const
00000000 T MathStackrelInset::normalize(NormalStream&) const
4000018c D typeinfo for MathStackrelInset
U typeinfo name for MathStackrelInset
40000040 D vtable for MathStackrelInset
$ nm -C libfrontends.a | grep updateSlot | grep InsetGraphicsParams
U ControlInset<InsetGraphics, InsetGraphicsParams>::updateSlot(bool)
00000000 t ControlInset<InsetGraphics, InsetGraphicsParams>::updateSlot(bool)
The 'nm' above is from GNU binutils. The HP 'nm' doesn't demangle the
C++ symbol names correctly as its -C option works only with ELF
objects.
Did I build GCC wrong? I have similar problems building another C++
application, Octave.
--
albert chin (china@thewrittenword.com)
next reply other threads:[~2002-08-22 5:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 5:31 Albert Chin [this message]
2002-08-22 9:29 ` Albert Chin
2002-08-22 9:34 ` John Levon
2002-08-22 9:48 ` Albert Chin
2002-08-22 12:12 ` Jeff Law
2002-08-22 12:15 ` Albert Chin
2002-08-22 9:40 ` Jeff Law
2002-08-22 11:02 ` Albert Chin
2002-08-22 12:02 ` Jeff Law
2002-08-22 15:08 John David Anglin
2002-08-22 15:14 ` Jeff Law
2002-08-22 15:45 ` John David Anglin
2002-08-22 16:34 ` Jeff Law
2002-08-22 17:11 ` John David Anglin
2002-08-23 5:32 ` Albert Chin
2002-08-23 10:08 ` Jeff Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020822073107.A5468@oolong.il.thewrittenword.com \
--to=gcc@lists.thewrittenword.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).