From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/2927 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: musl setup attempt Date: Sat, 16 Mar 2013 18:58:25 -0400 Message-ID: <20130316225824.GK20323@brightrain.aerifal.cx> References: <5140CA2B.2060902@barfooze.de> <20130315141141.1f14e6a4.idunham@lavabit.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1363474717 13277 80.91.229.3 (16 Mar 2013 22:58:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 16 Mar 2013 22:58:37 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-2928-gllmg-musl=m.gmane.org@lists.openwall.com Sat Mar 16 23:59:03 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1UH046-00067L-7H for gllmg-musl@plane.gmane.org; Sat, 16 Mar 2013 23:59:02 +0100 Original-Received: (qmail 30421 invoked by uid 550); 16 Mar 2013 22:58:38 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 30413 invoked from network); 16 Mar 2013 22:58:38 -0000 Content-Disposition: inline In-Reply-To: <20130315141141.1f14e6a4.idunham@lavabit.com> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:2927 Archived-At: On Fri, Mar 15, 2013 at 02:11:41PM -0700, Isaac Dunham wrote: > On Fri, 15 Mar 2013 07:54:39 -0400 > LM wrote: > > > I have really mixed results with reporting portability bugs. More > > often than not, projects refuse to accept the bugs unless they're for > > platforms they officially support. I typically work with > > cross-platform software, but many of the cross-platform projects still > > only officially support a limited number of systems. Some of them > > have even been down-right nasty when I submit a patch to fix an issue > > for my platform. (Of course, I've run across some projects where the > > developers have been very nice too and fix things extremely quickly.) > > Am very curious if anyone else has had problems with this sort of > > thing and how you handle the situation. > > A few points: > 1) Patches beat bug reports. Make sure that you note upstream policy > about copyright assignments and so on, though. > Also follow the code style upstream uses. > 2) Make sure it's not going to break upstream policy. > Examples: don't change -std=c89 > 3) Make sure it doesn't disable something for other platforms (eg, > breaking tests for uclibc) > 4) Make it as little change as appropriate > 5) If at all possible, test on other platforms. > > The best response I had was a trivial patch for libnl (adding a > couple headers) which I prepared, tested on musl and glibc, then > sent with a comment that it fixed build on musl and worked on glibc. > It was applied almost immediately. Thank you. This email belongs on the wiki. Rich