public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Mike Sweeney <msweeney77@gmail.com>
Cc: ecos-discuss@sourceware.org
Subject: Re: [ECOS] Order in which CDL scripts are processed
Date: Sun, 03 Jun 2007 16:18:00 -0000	[thread overview]
Message-ID: <4662E9D4.5000804@mlbassoc.com> (raw)
In-Reply-To: <70d4f620706030625r3f31543amc5fb3b5f8249fe1b@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mike Sweeney wrote:
> While looking through the code for the CYGPKG_HAL_ARM_XSCALE_CORE
> package I noticed that it exports some header files to cyg/hal in the
> install tree. In particular, it exports hal_cache.h which contains
> some cache size definitions and such. Furthermore, some of the generic
> ARM platform HAL packages such as the CYGPKG_HAL_ARM_AEB export
> hal_cache.h to the same directory. Now, granted since the generic ARM
> targets won't include the XScale package there won't be a conflict,
> but out of curiousity if I did export a hal_cache.h from an XScale
> variant HAL package is there any guarantee as to which hal_cache.h
> would end up in the install tree under include/cyg/hal, i.e. the one
> from CYGPKG_HAL_ARM_XSCALE_CORE or the one from my XScale variant HAL
> package?
> 
> In a nutshell, if I export the same header file to the same directory
> from two different packages, which one wins out or is it undefined
> behavior?

Undefined and probably no guaranteed behaviour, so don't do it.

If you need platform and/or variant changes/additions, there are
files for that (which are in turn included by the main hal_cache.h)


- --
- ------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGYunUmaKbSsQGV8ARAqoFAJ9pYUNUwhP8DRH1oH6miCx6qKafqACgpdJ3
F34+z7BFqK71nIUAM7y/yok=
=+08s
-----END PGP SIGNATURE-----

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

  reply	other threads:[~2007-06-03 16:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03 13:25 Mike Sweeney
2007-06-03 16:18 ` Gary Thomas [this message]
2007-06-03 16:33   ` Mike Sweeney

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=4662E9D4.5000804@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@sourceware.org \
    --cc=msweeney77@gmail.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).