public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Marc Michalewicz <marc.michalewicz@pixy.ch>
To: "Neundorf, Alexander" <Alexander.Neundorf@jenoptik.com>
Cc: ecos-devel <ecos-devel@sources.redhat.com>
Subject: Re: AW: undefined reference to `__impure_ptr' during linking test
Date: Wed, 01 Jun 2005 10:05:00 -0000	[thread overview]
Message-ID: <1117620314.20511.35.camel@c29.pixybugs.dyndns.org> (raw)
In-Reply-To: <5A8A17126B73AC4C83968F6C4505E3C5022BAA5F@JO-EX01.JENOPTIK.NET>

Thanks a lot,

this helped; i can build all tests now !

Next question is addressed to ecos-discuss - I just saw that this is the
right list for things like that.

Cheers,
Marc


Am Mittwoch, den 01.06.2005, 10:33 +0200 schrieb Neundorf, Alexander:
> Hi,
> 
> > Von: ecos-devel-owner@sources.redhat.com
> > 
> > Hello again !
> > 
> > puhh, I am getting closer to my first kernel - i think and hope.
> > So, now I succees in building a library, but when trying to link tests
> > I am getting now strange messages about undefined refernence:
> > 
> > "
> > /usr/share/gnuh8300_v0501_elf-1/lib/gcc/h8300-elf/3.4-GNUH8_v0
> > 501/../../../../h8300-elf/lib/h8300s/int32/libsupc++.a(vtermin
> > ate.o)(.text+0xca): In function `.L2':
> > : undefined reference to `__impure_ptr'
> > "
> > 
> > It is only this "impure_ptr", and only in "vterminate.o" nothing else
> > which is not found.
> > 
> > Did anybody experience this before and has a solution ?
> 
> I'm using gcc 3.4.1 and I think I had the same problem. Since then I compile and link the following reent.c, taken from newlib:
> 
> ---------8<-----------8<---------------8<----------------
> 
> #if (__GNUC__ == 3) && (__GNUC_MINOR__ == 4)
> 
> 
> #include <reent.h>
> 
> /* Note that there is a copy of this in sys/reent.h.  */
> #ifndef __ATTRIBUTE_IMPURE_PTR__
> #define __ATTRIBUTE_IMPURE_PTR__
> #endif
> 
> #ifndef __ATTRIBUTE_IMPURE_DATA__
> #define __ATTRIBUTE_IMPURE_DATA__
> #endif
> 
> static struct _reent __ATTRIBUTE_IMPURE_DATA__ impure_data = _REENT_INIT (impure_data);
> struct _reent *__ATTRIBUTE_IMPURE_PTR__ _impure_ptr = &impure_data;
> 
> #endif
> 
> ---------8<-----------8<---------------8<----------------
> 
> Seems to work.
> 
> Alex
> 

      reply	other threads:[~2005-06-01 10:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01  8:33 Neundorf, Alexander
2005-06-01 10:05 ` Marc Michalewicz [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=1117620314.20511.35.camel@c29.pixybugs.dyndns.org \
    --to=marc.michalewicz@pixy.ch \
    --cc=Alexander.Neundorf@jenoptik.com \
    --cc=ecos-devel@sources.redhat.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).