From: LM <lmemsm@gmail.com>
To: musl@lists.openwall.com
Subject: Re: musl setup attempt
Date: Fri, 15 Mar 2013 07:54:39 -0400 [thread overview]
Message-ID: <CAFipMOEecWFsspbO7hxozHe37nQVXgoSvEYVZMDZWLiFuDXFpA@mail.gmail.com> (raw)
In-Reply-To: <5140CA2B.2060902@barfooze.de>
On Wed, Mar 13, 2013 at 2:49 PM, John Spencer <maillist-musl@barfooze.de> wrote:
> mostly finding portability bugs in programs, like missing include
> directives, and then reporting the issue upstream
> (and keep nagging them until they finally fix it).
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.
I'm currently looking into whether I can find enough Open Source
implementations for the types of applications I need that avoid any
projects where the developers are unfriendly. I further limited
things down to applications that will run reasonably well on older
systems. That cuts out a lot of Open Source applications (and
libraries). Will see if I can still put together a coherent and
useful system under those conditions.
next prev parent reply other threads:[~2013-03-15 11:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 11:54 LM
2013-03-13 14:07 ` Isaac Dunham
2013-03-13 18:49 ` John Spencer
2013-03-15 11:54 ` LM [this message]
2013-03-15 21:11 ` Isaac Dunham
2013-03-16 13:36 ` LM
2013-03-16 22:58 ` Rich Felker
2013-03-14 11:02 LM
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=CAFipMOEecWFsspbO7hxozHe37nQVXgoSvEYVZMDZWLiFuDXFpA@mail.gmail.com \
--to=lmemsm@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).