linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Erick Ween" <jween@som.llu.edu>
To: daenzerm@student.ethz.ch
Cc: linuxppc-dev@lists.linuxppc.org
Subject: compile problems with header includes
Date: Mon, 6 Nov 2000 13:53:58 -0800	[thread overview]
Message-ID: <7737441D14ED.AAA1D34@som.llu.edu> (raw)


Iain Sandoe wrote:

> [root@athena stable-dma-int]# make vmlinux
> gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o
> scripts/split-include scripts/split-include.c
> In file included from /usr/include/errno.h:36,
>		   from scripts/split-include.c:26:
> /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory
>
> On 2.4.0-test4 (just to see if the build script makes *any* difference):
>
> [root@athena linux-2.4.0-t4-wrk]# make vmlinux
> gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o
> scripts/split-include scripts/split-include.c
> In file included from /usr/include/errno.h:36,
>		   from scripts/split-include.c:26:
> /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory

You are lacking the glibc header files. On my Debian potato system I have:

> dpkg -S linux/errno.h
libc6-dev: /usr/include/linux/errno.h

I've been having this same problem too, but DO have the header files
installed. Any idea of what else might be broken for gcc not to find the
header? (I use a linuxppc2K/redhat system).

Jon

Jon Erik Ween, MD
Cognitive and Cerebrovascular Neurology
Loma Linda University


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~2000-11-06 21:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7737441D14ED.AAA1D34@som.llu.edu \
    --to=jween@som.llu.edu \
    --cc=daenzerm@student.ethz.ch \
    --cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).