Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sjhill at realitydiluted.com <sjhill@realitydiluted.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libpng
Date: Wed, 5 Mar 2008 08:06:43 -0600	[thread overview]
Message-ID: <20080305140643.GA626@real.realitydiluted.com> (raw)
In-Reply-To: <87fxv5qnfg.fsf@macbook.be.48ers.dk>

>  sjhill> Fix patch. Apparently people don't know how to test
>  sjhill> their changes before cheking them in.
> 
> Strange. It seems like my tree was missing your patch from the 28th -
> sorry about that.
> 
> Everything seems to work fine without it though, what is the patch
> supposed to fix?
> 
At least when compiling for ARM, the build fails because of 'setjmp.h'
being included multiple times. I thing the check is stupid, so I removed
it.

-Steve

  reply	other threads:[~2008-03-05 14:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 13:35 [Buildroot] svn commit: trunk/buildroot/package/libpng sjhill at uclibc.org
2008-03-05 14:02 ` Peter Korsgaard
2008-03-05 14:06   ` sjhill at realitydiluted.com [this message]
2008-03-05 14:52     ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2009-02-27 14:59 jacmet at uclibc.org
2009-02-12 12:17 jacmet at uclibc.org
2009-01-12 12:45 laird at uclibc.org
2008-10-29 12:49 laird at uclibc.org
2008-10-29 13:53 ` Peter Korsgaard
2008-10-29 14:15   ` Daniel J Laird
2008-10-29 15:33   ` Daniel J Laird
2008-10-29 15:58     ` Peter Korsgaard
2008-10-06 15:11 jacmet at uclibc.org
2008-03-04 11:36 jacmet at uclibc.org
2008-03-04 11:36 jacmet at uclibc.org
2008-02-28 13:46 sjhill at uclibc.org
2008-02-28 21:43 ` Ulf Samuelsson
2007-08-05 14:00 aldot at uclibc.org
2007-08-01  8:36 ulf at uclibc.org
2007-08-01  9:47 ` Hebbar
2007-07-29  7:14 ulf at uclibc.org
2007-02-03 18:47 andersen at uclibc.org
2007-01-11  7:26 andersen at uclibc.org
2007-01-10 10:29 andersen at uclibc.org

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=20080305140643.GA626@real.realitydiluted.com \
    --to=sjhill@realitydiluted.com \
    --cc=buildroot@busybox.net \
    /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