public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tim Drury <tdrury@siliconmotorsports.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] make tests compile error for eb40
Date: Wed, 17 Jul 2002 08:24:00 -0000	[thread overview]
Message-ID: <200207170900.51584.tdrury@siliconmotorsports.com> (raw)


In trying to release the EB40a port, I'm trying to make and run the tests.
I can compile/run redboot without a problem, but when I try to 'make tests'
after the 'ecosconfig tree' command, I get the following error:

/usr/local/ecos/tests/install/lib/libtarget.a(redboot_main.o): In function 
`do_go':
/usr/local/ecos/cvs_td_patch/ecos/packages/redboot/current/src/main.c:713: 
undefined reference to `RedBoot_version'
collect2: ld returned 1 exit status

The redboot main.c references an extern RedBoot_version variable which
is declared in version.c in the redboot/src directory, but this file doesn't
seem to be getting compiled or linked when running 'make tests'.  But
'make' after targetting redboot works.  I found this in the redboot cdl
file:

        make -priority 320 {
            <PREFIX>/bin/redboot.elf : $(PREFIX)/lib/target.ld 
$(PREFIX)/lib/vectors.o $(PREFIX)/lib/libtarget.a $(PREFIX)/lib/libextras.a
                    @sh -c "mkdir -p $(dir $@)"
                    $(CC) -c $(INCLUDE_PATH) $(CFLAGS) -o 
$(PREFIX)/lib/version.o $(REPOSITORY)/$(PACKAGE)/src/version.c
                    $(CC) $(LDFLAGS) -L$(PREFIX)/lib -Ttarget.ld -o $@ 
$(PREFIX)/lib/version.o
        }

So it would seem that when building the redboot.elf, the version.c file
is compiled and linked here.  

My question:  how do I get version.c to get compiled and linked during
'make tests'?  When do those lines in the redboot cdl get invoked?
Should they be there or should version.c get compiled like all the other
support source files in redboot/src.  Why is version.c special?

I can certainly fix this by hacking the makefile for 'make tests', but I want
to do it the right way.

-tim drury


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

             reply	other threads:[~2002-07-17 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17  8:24 Tim Drury [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-17  7:30 Tim Drury
2002-07-17  7:37 ` Gary Thomas
2002-07-17  7:58   ` Tim Drury
2002-07-17  8:13     ` Gary Thomas

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=200207170900.51584.tdrury@siliconmotorsports.com \
    --to=tdrury@siliconmotorsports.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).