public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "[p e r c e p t i c o n]" <percepticon@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Newbie new to the list
Date: Wed, 23 Feb 2011 10:19:00 -0000	[thread overview]
Message-ID: <AANLkTimSDTLWo-qFPe6TGp62ECiVtMs9+u3cp+TdJRUr@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=wmjhdpx=wZqz0U-FGV-Pa-o+qbWb=b=XTzK9w@mail.gmail.com>

On 23 February 2011 05:29, [p e r c e p t i c o n]
<percepticon@gmail.com> wrote:
> hi again,
>
> ok, last week i mysteriously got it to compile my shared lib.  this week
> however, the errors returned even though i'm doing the exact same thing.
> here's the message:

Obviously you're not doing exactly the same thing, or you'd get the
same results.

> g++   -fPIC -DUNIX -D_REENTRANT -I. -I./../include  AuthModule.cpp -c -o
> sampleAuth/AuthModule.o

No -m32 here, so the output file is 64-bit

> g++ -shared -m32 -lstdc++ -o ./sampleAuth/AuthModule.so
> ./sampleAuth/AuthModule.o

-m32 here, requesting 32-bit output

> /usr/bin/ld: warning: i386:x86-64 architecture of input file
> `./sampleAuth/AuthModule.o' is incompatible with i386 output

It's telling you that AuthModule.o cannot be linked into a 32-bit
file, because it's 64-bit.

> i set LD_LIBRARY_PATH in my env vars to point to the 32bit libs...
> i also set LDFLAGS to -L/path/to/32bitlibs
> it's also tellimg me that it std::basic_string is not defined even though as
> you can see above i'm linking the std lib...

Have you used #include <string> ?

      parent reply	other threads:[~2011-02-23  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18  2:11 [p e r c e p t i c o n]
2011-02-18  7:11 ` Kai Ruottu
2011-02-18  9:14 ` Jonathan Wakely
     [not found]   ` <AANLkTimm9x5so-Rj8Do0x10jWXKvDo+Rt74U7Mq7YWNS@mail.gmail.com>
     [not found]     ` <AANLkTi=wmjhdpx=wZqz0U-FGV-Pa-o+qbWb=b=XTzK9w@mail.gmail.com>
2011-02-23 10:19       ` Jonathan Wakely [this message]

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=AANLkTimSDTLWo-qFPe6TGp62ECiVtMs9+u3cp+TdJRUr@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=percepticon@gmail.com \
    /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).