public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "James Yates" <j.yates@quartzuk.com>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] SH2 Build Problems
Date: Fri, 17 Oct 2003 10:48:00 -0000	[thread overview]
Message-ID: <CB39E7B8FC98924D85DFBED207E4CC9831F90F@ip02.quartzelec.adsl.gxn.net> (raw)

Many Thanks Andrew. I have finally sorted it out although i think my eyes are giving up on my after careful comparing lots of files. It turns out that line 2 of my custom build step had the -S missing from it so gcc was trying to assemble and link the file rather than just compile it. 
Many thanks, no I can proceed.

   James Yates

-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch]
Sent: 17 October 2003 11:05
To: James Yates
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] SH2 Build Problems


> The fgrep command is specified in the architecture cdl script:
> 
> make -priority 1 {
>         <PREFIX>/include/cyg/hal/sh2_offsets.inc : <PACKAGE>/src/var_mk_defs.c
>         $(CC) $(CFLAGS) $(INCLUDE_PATH) -Wp,-MD,sh2_offsets.tmp -o var_mk_defs.tmp -S $<
>         fgrep .equ var_mk_defs.tmp | sed s/#// > $@
>         @echo $@ ": \\" > $(notdir $@).deps
>         @tail +2 sh2_offsets.tmp >> $(notdir $@).deps
>         @echo >> $(notdir $@).deps
>         @rm sh2_offsets.tmp var_mk_defs.tmp
>     }
> 

> The scripts in both the working and non-working trees are
> identical. Can anyone tell me where this fgrep command is called
> from in the build process or why in one build this doesn't happen
> the second time.

The "-priority 1" controls when this section of make script is
executed. See:

http://ecos.sourceware.org/ecos/docs-latest/cdl-guide/build.make.html#BUILD.CUSTOM

One guess as to why it does not do it is because the dependencies are
wrong somehow. It thinks the target is up to date so there is no need
to rebuilt it. Deleting the file should force it to rebuild it.

   Andrew

--
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:[~2003-10-17 10:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17 10:48 James Yates [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-17  9:37 James Yates
2003-10-17 10:04 ` Andrew Lunn

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=CB39E7B8FC98924D85DFBED207E4CC9831F90F@ip02.quartzelec.adsl.gxn.net \
    --to=j.yates@quartzuk.com \
    --cc=andrew@lunn.ch \
    --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).