public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: paolo.teti@transport.alstom.com
To: help-gnats@gnu.org
Subject: differences in the elaboration order
Date: Thu, 24 Feb 2005 13:18:00 -0000	[thread overview]
Message-ID: <OF9C1EC97E.17E32DE2-ONC1256FB2.0047AAC3-C1256FB2.00488084@transport.alstom.com> (raw)

Dear all,

Is possible that the elaboration order is formally different if I move the 
environment 
from a workstation to another?

Looking at the GNAT source code seems that the elaboration order algorithm 
use 
information as paths name etc. (e.g. machine dependent information).

Clear the elaboration orders even if formally different is also valid 
because GNAT check it's validity,
but I prefer to know if it may be different if I move the env. between two 
workstation.

Note that I compile for a target machine, not for the host one.

Regards, Paolo



_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

             reply	other threads:[~2005-02-24 13:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24 13:18 paolo.teti [this message]
2005-02-24 17:16 ` Chad Walstrom

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=OF9C1EC97E.17E32DE2-ONC1256FB2.0047AAC3-C1256FB2.00488084@transport.alstom.com \
    --to=paolo.teti@transport.alstom.com \
    --cc=help-gnats@gnu.org \
    /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).