Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Stephen P. Becker" <geoman@gentoo.org>
To: Andre.Messerschmidt@infineon.com
Cc: linux-mips@linux-mips.org
Subject: Re: Mozilla Firefox compile problem
Date: Mon, 18 Oct 2004 08:55:30 -0400	[thread overview]
Message-ID: <4173BD42.9050009@gentoo.org> (raw)
In-Reply-To: <34A8108658DCCE4B8595675ABFD8172709FAFE@dusse201.eu.infineon.com>

Andre.Messerschmidt@infineon.com wrote:
> Hi,
> 
> I am trying to compile Mozilla Firefox 1.0PR with Montavista Pro 3.1 toolchain (I linked mips_fp_be to mips-linux), but I get the following error messages:
> 
> ---- snip ---------------------------------------------------
> mips-linux-g++  -I/opt/mvx/usr/X11R6/include -fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wno-long-long -Wa,-xgot -pthread -pipe  -DDEBUG -D_DEBUG -DDEBUG_am -DTRACING -g -fno-inline -o nsIFileEnumerator nsIFileEnumerator.o           -L../../dist/bin -L../../dist/lib -L../../dist/bin -lxpcom  -L/data2/Sources/inca/mozilla/dist/lib -lplds4 -lplc4 -lnspr4 -lpthread -ldl   -ldl -lm
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub203()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub156()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub184()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub128()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub226()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub246()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub112()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub180()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub230()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub147()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub151()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub116()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub111()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub231()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub141()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub104()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub58()'
> ../../dist/bin/libxpcom.so: undefined reference to `nsXPTCStubBase::Stub53()'
> 
> ...
> 

https://bugzilla.mozilla.org/show_bug.cgi?id=71627

The patch there will fix the compile, but the resulting binary probably 
won't run.

Steve

  parent reply	other threads:[~2004-10-18 12:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-18  8:24 Mozilla Firefox compile problem Andre.Messerschmidt
2004-10-18  8:24 ` Andre.Messerschmidt
2004-10-18 12:55 ` Stephen P. Becker [this message]
2004-10-18 22:51   ` Thiemo Seufer
  -- strict thread matches above, loose matches on Subject: below --
2004-10-20  7:10 Andre.Messerschmidt
2004-10-20  7:10 ` Andre.Messerschmidt
2004-10-20 10:53 ` Thiemo Seufer

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=4173BD42.9050009@gentoo.org \
    --to=geoman@gentoo.org \
    --cc=Andre.Messerschmidt@infineon.com \
    --cc=linux-mips@linux-mips.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