Buildroot里面 - 应用补丁失败 [英] Buildroot - Applying A Patch Failed

查看:1005
本文介绍了Buildroot里面 - 应用补丁失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我试图建立我的 Phidg​​etSBC <定制的内核映像/ A>,但我在生成过程中得到了失败:

I'm trying to build a custom kernel image for my PhidgetSBC but I'm getting a failure during the build:

4.96 bluez的提取

bluez 4.96 Extracting

4.96 bluez的修补包/ bluez的

bluez 4.96 Patching package/bluez

在的config.guess config.sub脚本文件;在$做我(找
  /home/kerubu/buildroot_phidgetsbc/new/buildroot-phidgetsbc_1.0.4.20111028/output/build/bluez-4.96
  -name $文件);做CP包/ gnuconfig / $文件I $;完成的;做

for file in config.guess config.sub; do for i in $(find /home/kerubu/buildroot_phidgetsbc/new/buildroot-phidgetsbc_1.0.4.20111028/output/build/bluez-4.96 -name $file); do cp package/gnuconfig/$file $i; done; done

修补的libtool

Patching libtool

应用使用明文的buildroot-libtool.patch:修补文件
  ltmain.sh

Applying buildroot-libtool.patch using plaintext: patching file ltmain.sh

大块#1失败273。

猛男#2成功在5412(偏移3005线)。

Hunk #2 succeeded at 5412 (offset 3005 lines).

大块#3次失败在2551。

Hunk #3 FAILED at 2551.

猛男#4失败的2895。

Hunk #4 FAILED at 2895.

猛男#5成功在8058细毛1(偏移2446线)。

Hunk #5 succeeded at 8058 with fuzz 1 (offset 2446 lines).

猛男#6失败在5937。

Hunk #6 FAILED at 5937.

4,满分失败6帅哥的 - 节能拒绝到文件ltmain.sh.rej

4 out of 6 hunks FAILED -- saving rejects to file ltmain.sh.rej

补丁失败!请修正的buildroot-libtool.patch!

Patch failed! Please fix buildroot-libtool.patch!

请: *
  [/home/kerubu/buildroot_phidgetsbc/new/buildroot-phidgetsbc_1.0.4.20111028/output/build/bluez-4.96/.stamp_patched]
  错误1

make: * [/home/kerubu/buildroot_phidgetsbc/new/buildroot-phidgetsbc_1.0.4.20111028/output/build/bluez-4.96/.stamp_patched] Error 1

我不知道如何从这里着手。有没有人有什么建议吗?

I'm not sure how to proceed from here. Does anyone have any advice?

推荐答案

呀,你用的是旧版本的Buildroot里面中,我们只有对libtool的1.5补丁,但你的配合bluez版本可能使用libtool 2.2。作为一个快速的解决方法,你可以尝试以下行添加到的bluez .mk文件:

Yeah, you use an old version of Buildroot in which we only had a patch against libtool 1.5, but your version of Bluez probably uses libtool 2.2. As a quick workaround, you can try to add the following line to the bluez .mk file :

BLUEZ_LIBTOOL_PATCH = NO

这将告诉Buildroot里面不适用libtool补丁。

which will tell Buildroot to not apply the libtool patch.

不过,libtool的处理一直以来在Buildroot里面相当一段时间的改善,所以这是一个有点羞耻不采取较新的Buildroot里面的发​​行版的优势

However, the libtool handling has been improved since quite some time in Buildroot, so it's a bit of shame to not take advantage of the newer Buildroot releases.

这篇关于Buildroot里面 - 应用补丁失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆