Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@enix.org>
To: linux-mips@linux-mips.org
Subject: Missing include/asm-mips/reg.h ?
Date: Tue, 7 Sep 2004 18:49:03 +0200	[thread overview]
Message-ID: <20040907164903.GB32393@enix.org> (raw)

Hello,

While trying to compile uClibc, I get an error concerning Linux kernel
headers. The file include/asm-mips/user.h includes the file asm/reg.h,
but the file include/asm-mips/reg.h doesn't exist. So the EF_SIZE symbol
required by the definition of the user structure is not declared.

I checked the linux-mips CVS but couldn't find this file.

How should I proceed ?

Thanks,

Thomas
-- 
PETAZZONI Thomas - thomas.petazzoni@enix.org 
http://thomas.enix.org - Jabber: kos_tom@sourcecode.de
KOS: http://kos.enix.org/ - Lolut: http://lolut.utbm.info
Fingerprint : 0BE1 4CF3 CEA4 AC9D CC6E  1624 F653 CB30 98D3 F7A7

             reply	other threads:[~2004-09-07 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07 16:49 Thomas Petazzoni [this message]
2004-09-07 19:00 ` Missing include/asm-mips/reg.h ? Thiemo Seufer
2004-09-08  7:04 ` Thomas Petazzoni

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=20040907164903.GB32393@enix.org \
    --to=thomas.petazzoni@enix.org \
    --cc=linux-mips@linux-mips.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