From: Jakub Jelinek <jakub@redhat.com>
To: ultralinux@vger.kernel.org
Subject: Re: "sparc_cpu_model" undefined
Date: Fri, 19 May 2000 12:49:20 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-95874054230333@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-95874021030030@msgid-missing>
On Fri, May 19, 2000 at 05:34:37AM -0700, Murray Stokely wrote:
>
> I can't compile any code that includes asm/io.h with Red Hat 6.1, or
> 6.2 on my Ultra5. This includes many useful programs such as 'sane',
> the scanner drivers. The defines are all messed up so that the
> headers can't tell what type of sparc you are compiling for. This
> problem has been reported on this list before but I've never seen a
> solution and can't find any with the search engine. Can someone point
> me in the right direction?
Don't include asm/io.h ever.
sane package Red Hat ships has this fixed (see sane src.rpm in PowerTools).
Jakub
next prev parent reply other threads:[~2000-05-19 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-19 12:34 "sparc_cpu_model" undefined Murray Stokely
2000-05-19 12:49 ` Jakub Jelinek [this message]
2000-05-19 15:23 ` Pete Zaitcev
2000-05-20 1:44 ` Murray Stokely
2000-05-20 6:05 ` Jakub Jelinek
2000-05-21 21:48 ` Murray Stokely
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=marc-linux-ultrasparc-95874054230333@msgid-missing \
--to=jakub@redhat.com \
--cc=ultralinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.