From: Martin Buchholz <martin@xemacs.org>
To: Martin Schulze <joey@infodrom.north.de>
Cc: 33663@bugs.debian.org, control@bugs.debian.org,
"Matt Armstrong" <mattarmst@hotmail.com>,
Raul Miller <moth@debian.org>,
zsh-workers@math.gatech.edu
Subject: Re: Bug#33663: Debian GNU Linux 2.0 libc.h
Date: Sun, 21 Feb 1999 19:52:59 +0900 (JST) [thread overview]
Message-ID: <14031.58763.947276.364518@mulelab.etl.go.jp> (raw)
In-Reply-To: <19990221105937.B2400@finlandia.artis.uni-oldenburg.de>
>>>>> "MS" == Martin Schulze <joey@finlandia.Infodrom.North.DE> writes:
MS> reassign 33663 libc6-dev
MS> thanks
"Matt Armstrong" <mattarmst@hotmail.com> writes:
MA> That header is coming from the libxg-dev package, described as "graphics
MA> libraries from plan 9." That package isn't part of the default install,
MA> but it is available as part of the stable release. You could try a
MA> "dpkg --purge libxg-dev" to get rid of it.
MA> The moron that came up with the idea was Raul Miller <moth@debian.org>.
MA> You should file a Debian bug against the package -- having that
MA> incompatible libc.h in /usr/include just seems broken.
MA> In any case, since the header can appear in stable release Debian
MA> systems, a fix to zsh seems warranted.
MS> Martin Buchholz wrote:
>> This operating system appears to include a /usr/include/libc.h which
>> contains this bogus code:
>>
>> #define dup(a,b) dup2(a,b)
MS> What is bogos here? Defining a function as alias for another
MS> one is absolutely not bogus.
Excuse me??? I'm sorry, I'm not a flamer, but you are really really
asking for it. Perhaps you've never tried to maintain the configure
script for a package.
There are standards for this stuff. Look at:
http://www.opengroup.org/onlinepubs/7908799/xsh/dup.html
#include <unistd.h>
int dup(int fildes);
int dup2(int fildes, int fildes2);
>> It has this copyright notice:
>>
>> /* Copyright (c) 1992 AT&T - All rights reserved. */
>>
>> /* Plan 9 C library interface */
>>
>>
>> <flame on>
>> I don't know what moron came up with the idea of including ANOTHER
>> operating system's headers with Debian Linux. When people talk about
>> code reuse, I don't think this is what they had in mind.
>> <flame off>
MS> Did you notice that several files have a copyright from another operating
MS> system? It's called *BSD. AT&T has invented unix some time ago and
MS> as long as their files are free and they're fine there is no reason
MS> for not including them.
This is not about legal issues, or about freedom. (or free beer, for
that matter)
Have you ever heard of `configure'? Have you considered that some
software might try to examine its environment, and deduce some things
from that examination? Maybe it will check if there is a libc.h
installed, and will
#include <libc.h>
if so?
MS> I'd consider this a sa non-bug.
Please please please please reconsider.
If you don't consider this a bug, I will recommend that all my friends
uninstall Debian and install Red Hat or Suse instead. I'm a long time
Red Hat user, and although it has not been without problems, I never
once experienced anything this stupid.
Martin
parent reply other threads:[~1999-02-21 10:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <19990221105937.B2400@finlandia.artis.uni-oldenburg.de>]
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=14031.58763.947276.364518@mulelab.etl.go.jp \
--to=martin@xemacs.org \
--cc=33663@bugs.debian.org \
--cc=control@bugs.debian.org \
--cc=joey@infodrom.north.de \
--cc=mattarmst@hotmail.com \
--cc=moth@debian.org \
--cc=zsh-workers@math.gatech.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).