All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] Question concerning buildroot-libtool.patch
Date: Thu, 24 Jun 2010 13:35:53 +0200	[thread overview]
Message-ID: <201006241335.53291.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20100624092558.428c8478@surf>

Thomas > Something must have changed somewhere :)
Yeah that might be possible - since I can't get it to work with an older 
version of buildroot either.

As my development system is my normal home pc, it is quite prune to updates 
and changes :) 
Since I've just graduated and thus unemployed setting up a dedicated 
development environment isn't an option unfortunately :/

Thomas > You can use <pkg>_LIBTOOL_PATCH=NO to disable the 
Thomas > buildroot-libtool.patch on > this  specific <pkg>.

Seems to work - I'll create a new patch for pidgin, including a version bump 
too :)


Thanks,
Peter



Am Donnerstag 24 Juni 2010 09:25:58 schrieb Thomas Petazzoni:
> Hello,
> 
> On Thu, 24 Jun 2010 00:57:46 +0200
> 
> Peter H?we <PeterHuewe@gmx.de> wrote:
> > It used to work with an older version of Buildroot (~ git 2010-05-14) -
> > but as far as I can see nothing has changed on the patch / or the pidgin
> > source I've used.
> 
> I don't see how it's possible that the same patch doesn't apply on the
> same codebase as before. Our buildroot-libtool.patch hasn't changed for
> years. 
> 
> > Any ideas how I can fix this? Unfortunately I'm not that into the whole
> > buildroot system (yet, but I'd like to learn and contribute to it).
> 
> You can use
> 

> 
> Regards,
> 
> Thomas
> 

  reply	other threads:[~2010-06-24 11:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 22:57 [Buildroot] Question concerning buildroot-libtool.patch Peter Hüwe
2010-06-24  7:25 ` Thomas Petazzoni
2010-06-24 11:35   ` Peter Hüwe [this message]
2010-06-24 14:03     ` Thomas Petazzoni

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=201006241335.53291.PeterHuewe@gmx.de \
    --to=peterhuewe@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.