From: Gary Thomas <gthomas@redhat.com>
To: danish iftikhar <d_iftikhar@hotmail.com>
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] linker problem : missing crt0.o
Date: Fri, 15 Sep 2000 05:19:00 -0000 [thread overview]
Message-ID: <XFMail.20000915061902.gthomas@redhat.com> (raw)
In-Reply-To: <F190iQTjGsEhM7p6NYY0000ab94@hotmail.com>
On 15-Sep-2000 danish iftikhar wrote:
>
> Hi
>
> i am trying to make an executable for eCos using arm-elf-gcc .
> but during make , it gave the error :
> tools/H-i686-pc-linux-gnu/arm-elf/bin/ld: cannot open crt0.o: No such file
> or directory
> collect2: ld returned 1 exit status
>
> moreover i could not found crt0.o in any place .
> do i have to install it seperately or is there some specific way to invoke
> this .
> what additions are required to be done for Makefile.
>
> any suggestions are welcome
Look at the example Makefile provided. You'll see that we use our own
startup and library files (-nostdlib), not "crt0.o" and friends.
If you're using the tools from a command line, another way to see how
applications are built is by building a test. For example, assuming
that your build/install tree is "arm_test" and you've installed eCos
version 'VVV': (VVV would be something like v1_3_13)
% cd arm_test
# build eCos kernel library
% make
# create a test
% make -C kernel/VVV/src tests TESTS=tests/tm_basic
This will create the kernel 'tm_basic' test, with the result ending up
in the directory "install/tests/kernel/VVV/tests/"
prev parent reply other threads:[~2000-09-15 5:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-14 23:11 danish iftikhar
2000-09-15 5:19 ` Gary Thomas [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=XFMail.20000915061902.gthomas@redhat.com \
--to=gthomas@redhat.com \
--cc=d_iftikhar@hotmail.com \
--cc=ecos-discuss@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).