mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] No c headers in sysroot-target/usr/include but all compiles well
Date: Fri, 14 Nov 2014 11:42:16 +0100	[thread overview]
Message-ID: <20141114104216.GC30787@pengutronix.de> (raw)
In-Reply-To: <916A03CCEB30DF44AD98D4CFDC7448D02A7EAF2D@nooslzsmx1.zenitelcss.com>

Hi,

On Fri, Nov 14, 2014 at 10:19:58AM +0000, Alan Martinovic wrote:
> as the subject states, my IDE constantly complains about missing header files (example. <stdio.h> or <signal.h>).
> The sysroot points to  sysroot-target/.
> Checking the sysroot-target/usr/include the header files really aren't there.
> 
> What confuses me is that the compilation always passes without a problem.
> I'm using the arm-v5te-linux-gnueabi-gcc compiler.
> 
> Shouldn't the header files be there? I have glibc selected in the config.
> Since they aren't, you have any ideas on why would the compilation succeed?

These headers are in the toochain sysroot:
"arm-v5te-linux-gnueabi-gcc -print-sysroot" should give you the path.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-11-14 10:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14 10:19 Alan Martinovic
2014-11-14 10:42 ` Michael Olbrich [this message]
2014-11-14 10:46   ` Alan Martinovic
2014-11-14 10:52     ` Marc Kleine-Budde
2014-11-14 11:10       ` Alan Martinovic

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=20141114104216.GC30787@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.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