From: Vikram Dhillon <dhillonv10@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove macro MAXHOSTNAMELEN from <asm-generic/param.h>.
Date: Tue, 29 Dec 2009 21:05:42 -0500 [thread overview]
Message-ID: <ea6602020912291805l2a1bd85cx9af7a4312aabfa17@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0912292002370.6803@localhost>
I agree with you, the only place this macro is being used in glibc,
there are some really nice packages like MATLAB that depend on it, but
in distributions like Solaris there are conflicts in the newer version
and glibc so the trend seems to be moving away from glibc dependency
because of those conflicts. We might more of packages moving away from
glibc so let's wait and see what happens next :D
Regards,
Vikram Dhillon
~~~
There are lots of Linux users who don't care how the kernel works, but
only want to use it. That is a tribute to how good Linux is.
-- Linus Torvalds
On Tue, Dec 29, 2009 at 8:03 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> On Wed, 30 Dec 2009, Stephen Rothwell wrote:
>
>> Hi Robert,
>>
>> On Tue, 29 Dec 2009 19:32:15 -0500 (EST) "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
>> >
>> > Since nothing in the entire tree makes use of this macro, remove
>> > it. This removal should eventually propagate to all of the
>> > arch-specific param.h files.
>>
>> Except if the only place this is picked up by glibc is the kernel
>> header files, then it will disappear from user mode and some
>> packages may break.
>
> true, but this still takes me back to my original observation -- why
> is this macro being defined in a kernel header file if the kernel
> itself has absolutely no interest in it and doesn't use it in any way?
>
> if glibc wants it, it might as well define it.
>
> rday
> --
>
>
> ========================================================================
> Robert P. J. Day Waterloo, Ontario, CANADA
>
> Linux Consulting, Training and Kernel Pedantry.
>
> Web page: http://crashcourse.ca
> Twitter: http://twitter.com/rpjday
> ========================================================================
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2009-12-30 2:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 0:32 Robert P. J. Day
2009-12-30 0:56 ` Stephen Rothwell
2009-12-30 1:03 ` Robert P. J. Day
2009-12-30 2:05 ` Vikram Dhillon [this message]
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=ea6602020912291805l2a1bd85cx9af7a4312aabfa17@mail.gmail.com \
--to=dhillonv10@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®