public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jeroen Hofstee <dasuboot@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] Building under Cygwin - "-ansi" flag?
Date: Tue, 20 May 2014 20:06:57 +0200	[thread overview]
Message-ID: <1400609217.2002.37.camel@yellow> (raw)
In-Reply-To: <CA+gZxsOCcpZmuAbvqXT2zWZgnkrxMjVx7G53m06=hqVgaX6pnQ@mail.gmail.com>

Dear Vasili,

On ma, 2014-05-19 at 12:45 +0300, Vasili Galka wrote:
[...]

> 2. I see a reoccurring pattern of some headers being used from the host,
>    causing mismatches and arising build errors. Then some way is sought
>    to include headers from U-Boot tree prior to them which solves the
>    problem. This happens for both Linux and Cygwin. 

you can add FreeBSD to the list as well, see [1]

>    This pattern is a
>    result of the original decision from 2004 to prioritize the host
>    include paths over the paths from U-Boot tree. 

any reference?

> I see this happening
>    again and again with different headers in the future. So here comes
>    the question, is it really the right thing prioritize the include
>    paths this way? Why do host paths MUST come first?
>    I'll try reverting this locally and looking what breaks and what
>    alternative solutions exist.

I have no idea why it is the way it is, but keep in mind that e.g. stdio
headers in u-boot is quite something different then stdio for the target
userland.

Regards,
Jeroen

[1] http://lists.denx.de/pipermail/u-boot/2014-May/179301.html

  reply	other threads:[~2014-05-20 18:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 11:49 [U-Boot] Building under Cygwin - "-ansi" flag? Vasili Galka
2014-05-09 15:08 ` Tom Rini
     [not found]   ` <CA+gZxsNyypaz+Qf2DyDDX0tQY=+dr6J=ym2joKfJS9GqcnwNTg@mail.gmail.com>
2014-05-19  9:45     ` Vasili Galka
2014-05-20 18:06       ` Jeroen Hofstee [this message]
2014-05-21  8:50         ` Vasili Galka
2014-05-22 18:27           ` Jeroen Hofstee
2014-06-05 12:51             ` Vasili Galka
2014-06-06 10:43               ` Masahiro Yamada
2014-06-06 12:13                 ` Vasili Galka
2014-06-06 10:42       ` Masahiro Yamada
2014-06-06 10:58 ` Masahiro Yamada

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=1400609217.2002.37.camel@yellow \
    --to=dasuboot@myspectrum.nl \
    --cc=u-boot@lists.denx.de \
    /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