From: Joop Stakenborg <pa3aba@debian.org>
To: LaMont Jones <lamont@hp.com>
Cc: lamont+buildd@hp.com, 193261@bugs.debian.org
Subject: [parisc-linux] Re: Bug#193261: glfer_0.3.2-1(hppa/unstable): FTBFS: assumes sys/io.h exists
Date: Fri, 16 May 2003 21:24:56 +0200 [thread overview]
Message-ID: <3EC53B08.2050904@debian.org> (raw)
In-Reply-To: <20030516191505.GA24104@security.hp.com>
LaMont Jones wrote:
> severity 193261 important
> --
> On Wed, May 14, 2003 at 05:04:00PM +0200, Joop Stakenborg wrote:
>
>>>There are many architectures where sys/io.h does not exist.
>>
>>Sorry about that. I will make it a i386-only package for now.
>
>
> Please don't do that. This bug should be important, not serious,
> which makes it not release-critical. (Sorry about that...)
>
> Unless the package is truely i386 specific in _function_ (not
> compile-ability), or depends on such, it should be Architecture: any.
>
Okay,
where do I find information on functions and devices available on other
architectures, e.g. glfer uses inb, outb and ioperm (they are in
sys/io.h) on the parallel/serial port.
> lamont
>
>
Thanks,
Joop
parent reply other threads:[~2003-05-16 19:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20030516191505.GA24104@security.hp.com>]
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=3EC53B08.2050904@debian.org \
--to=pa3aba@debian.org \
--cc=193261@bugs.debian.org \
--cc=lamont+buildd@hp.com \
--cc=lamont@hp.com \
/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