From: Jean-Christian de Rivaz <jc@eclis.ch>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot-libtool.patch failed with dbus 1.3.0
Date: Fri, 07 Aug 2009 21:52:16 +0200 [thread overview]
Message-ID: <4A7C85F0.7070604@eclis.ch> (raw)
Hi all,
In the hope to close a dbus issue, I tryed to update it to the version
1.3.0 by changing the DBUS_VERSION in package/dbus/dbus.mk.
Unfortunately this raised a libtool problem that seem specific to
buildroot as the native dbus archive compile without this problem:
>>> dbus 1.3.0 Extracting
>>> dbus 1.3.0 Patching libtool
Applying buildroot-libtool.patch using plaintext:
patching file ltmain.sh
Hunk #1 FAILED at 273.
Hunk #2 succeeded at 5425 (offset 3017 lines).
Hunk #3 FAILED at 5569.
Hunk #4 FAILED at 5913.
Hunk #5 succeeded at 8089 with fuzz 1 (offset 2466 lines).
Hunk #6 FAILED at 8414.
4 out of 6 hunks FAILED -- saving rejects to file ltmain.sh.rej
Patch failed! Please fix buildroot-libtool.patch!
make: ***
[/home/jcdr/try/buildroot/build_i686/dbus-1.3.0/.stamp_libtool_patch]
Erreur 1
I tested also the last buildroot git tree with ARM and i386: same
result.
If I understand correctly, buildroot have a script
package/Makefile.autotools.in that try to patch the ltmain.sh for his
specific need. How can I disable or fix this ?
Best Regards,
Jean-Christian de Rivaz
next reply other threads:[~2009-08-07 19:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 19:52 Jean-Christian de Rivaz [this message]
2009-08-07 20:17 ` [Buildroot] buildroot-libtool.patch failed with dbus 1.3.0 Thomas Petazzoni
2009-08-07 21:40 ` [Buildroot] [PATCH] " Jean-Christian de Rivaz
2009-08-07 22:43 ` Thomas Petazzoni
2009-08-07 23:07 ` Jean-Christian de Rivaz
2009-08-08 18:09 ` Thomas Petazzoni
2009-08-08 22:36 ` Jean-Christian de Rivaz
2009-08-08 22:59 ` Thomas Petazzoni
2009-08-10 7:29 ` Jean-Christian de Rivaz
2009-08-10 7:39 ` Jean-Christian de Rivaz
2009-08-09 22:17 ` Thomas Petazzoni
2009-08-10 7:37 ` Jean-Christian de Rivaz
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=4A7C85F0.7070604@eclis.ch \
--to=jc@eclis.ch \
--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