From: Bart Veer <bartv@redhat.com>
To: igor@bluewind.it
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Problems while cross compiling for ARM
Date: Wed, 08 Nov 2000 06:13:00 -0000 [thread overview]
Message-ID: <200011081413.eA8EDDc28619@sheesh.cygnus> (raw)
In-Reply-To: <3A092BFD.28088.154496@localhost>
>>>>> "Igor" == Igor Trevisan <igor@bluewind.it> writes:
Igor> I built an ARM-Thumb development tool for Linux following
Igor> step by step all the instructions I found in the page:
Igor> "Building the thumb-elf development tools for Linux", and
Igor> I'm still trying to cross-compile a simple "hello.c" file
Igor> but I don't succeed. I'm using the tool without eCos. Now my
Igor> arm-gcc find the include files; but I have to do with the
Igor> following new error message:
Igor> /tools/H-i686-pc-linux-gnu/lib/gcc-lib/arm-elf/2.97/../../../../arm-elf/bin/ld:
Igor> cannot open crt0.o: File o directory inesistente
Igor> collect2: ld returned 1 exit status
Igor> What can I do to avoid this problem?
Igor> Thanks in advance to everyone that will help me.
If you are using newlib rather than eCos then there should be a crt0.o
file in a lib directory somewhere inside the install tree. You may
need to specify a suitable path using a -L argument to arm-elf-gcc,
although I would have expected the compiler to be able to find this
directory automagically. It is a long time since I did any work with
newlib rather than eCos so I am afraid I cannot remember all the
details. You may have more luck asking this question on the cross-gcc
mailing list, http://sources.redhat.com/ml/crossgcc , since the people
on the ecos-discuss mailing list are usually not particularly
interested in newlib anymore.
Bart Veer // eCos net maintainer
prev parent reply other threads:[~2000-11-08 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 1:43 Igor Trevisan
2000-11-08 4:25 ` Rafael RodrÃguez Velilla
2000-11-08 6:13 ` Bart Veer [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=200011081413.eA8EDDc28619@sheesh.cygnus \
--to=bartv@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=igor@bluewind.it \
/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).