From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Pull request for branch x11r75patches
Date: Sat, 13 Mar 2010 22:19:52 +0000 [thread overview]
Message-ID: <4B9C0F88.7000209@carallon.com> (raw)
In-Reply-To: <4B9BE875.9040500@gmail.com>
>> xproto_xf86miscproto: bump version
>> xlib_libpciaccess: bump version
>
> libpciaccess fails... due to libtool patch:
>
> >>> Patching libtool
>
> Applying buildroot-libtool.patch using plaintext:
> patching file ltmain.sh
> Hunk #1 FAILED at 273.
> Hunk #2 succeeded at 5412 (offset 3005 lines).
> Hunk #3 FAILED at 2551.
> Hunk #4 FAILED at 2895.
> Hunk #5 succeeded at 8058 with fuzz 1 (offset 2446 lines).
> Hunk #6 FAILED at 5937.
> 4 out of 6 hunks FAILED -- saving rejects to file ltmain.sh.rej
> Patch failed! Please fix buildroot-libtool.patch!
> make: ***
> [/home/paulius/buildroot/output/build/xlib_libpciaccess-0.11.0/.stamp_patched]
> Error 1
>
Odd, I definitely have it building, will try to work out why it works
for me.
It's easy to fix by disabling the libtool step. Would be good to fixup
the libtool patching though so it spots what version the package has and
patches accordingly.
Anyone an expert on the libtool patch. Is the patch not needed for 2.2.6
of ltmain.sh? If so I guess we can check the version before patching.
Will
next prev parent reply other threads:[~2010-03-13 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 22:50 [Buildroot] Pull request for branch x11r75patches Will Wagner
2010-03-09 22:58 ` H Hartley Sweeten
2010-03-09 23:01 ` Will Wagner
2010-03-10 19:41 ` Thomas Petazzoni
2010-03-13 19:33 ` Paulius Zaleckas
2010-03-13 22:19 ` Will Wagner [this message]
2010-03-14 15:52 ` Paulius Zaleckas
2010-03-14 22:26 ` Will Wagner
2010-03-15 9:41 ` Paulius Zaleckas
2010-03-22 19:37 ` William Wagner
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=4B9C0F88.7000209@carallon.com \
--to=will_wagner@carallon.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