All of lore.kernel.org
 help / color / mirror / Atom feed
From: Toni Van Remortel <t.vanremortel@ha.be>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: fstream on PPC?
Date: Tue, 18 Nov 2003 09:58:29 +0100	[thread overview]
Message-ID: <1069145908.1006.2.camel@toni> (raw)
In-Reply-To: <20031117155350.D76B7C5F59@atlas.denx.de>


Op ma 17-11-2003, om 16:53 schreef Wolfgang Denk:
> Dear Toni,
>
> in message <1069081757.25853.5.camel@toni> you wrote:
> >
> > But when I allow the functions that use fstream (for saving and loading
> > small files over NFS), I get the following error:
> >
> > Linking test...
> > /opt/eldk/usr/ppc-linux/bin/ld: warning: libstdc++-libc6.2-2.so.3,
> > needed by /opt/PPC_X/usr/X11R6/lib/libGLU.so, not found (try using
> > -rpath or -rpath-link)
> ...
> > and more than a dozen of these errors. It's a linking problem, that's
> > what I know. But I don't know how to get to the problem-core. Can I
>
> Why not? The error message is pretty plain english:
>
> Your  link  step  included   the   /opt/PPC_X/usr/X11R6/lib/libGLU.so
> library,    which    in    turn    tried    to   link   against   the
> libstdc++-libc6.2-2.so.3 library, which was not found by the linker.

Strange. It did found it before. Should check that further then.
Although the resulting binary runs fine on the EP405.

> > solve this by a quick hack? Or is it hopeless to start messing with
> > fstream on PPC?
>
> I don't know where  you  got  the  /opt/PPC_X/usr/X11R6/lib/libGLU.so
> library  from.

Compiled from source, linked against ELDK. Works perfectly.

> > PS: don't mind the warning about libstdc++-libc6.2-2.so.3, it's in place
> > on the embedded system.
>
> You must be joking. Of course you have to mind this.  It's  the  root
> cause  of your problems. And other problems are lurking to hit you as
> libstdc++-libc6.2-2.so.3 is most probably incompatible to  the  ELDK,
> too.

Hmm. Still find it strange. It compiles, it runs, and it only complains
at compile time. Very odd, but I'll try to remove the first warning and
see what happens.

Thanks for your help.
--
                           Toni Van Remortel
              Wetenschappelijk Medewerker - D-science lab
  Real time Linux for embedded systems: http://linemb.d-sciencelab.com
              Tel: +32 3 205 61 72 - Fax: +32 3 205 61 95
                      E-mail: t.vanremortel@ha.be


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-11-18  8:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17 15:09 fstream on PPC? Toni Van Remortel
2003-11-17 15:53 ` Wolfgang Denk
2003-11-18  8:58   ` Toni Van Remortel [this message]
2003-11-18  9:38     ` Toni Van Remortel

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=1069145908.1006.2.camel@toni \
    --to=t.vanremortel@ha.be \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wd@denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.