From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Mono: fixing latest build failures
Date: Mon, 11 May 2015 22:55:29 +0200 [thread overview]
Message-ID: <55511741.7090802@openwide.fr> (raw)
In-Reply-To: <CA+TH9VnCUu0+C5Qeu=UX2_Qpd3dZ8qrZ4074Qkg1DkhQ045cjA@mail.gmail.com>
Hi Angelo,
Le 11/05/2015 22:44, Angelo Compagnucci a ?crit :
> Dear Peter Korsgaard,
>
> 2015-05-11 22:36 GMT+02:00 Peter Korsgaard <peter@korsgaard.com>:
>>>>>>> "Angelo" == Angelo Compagnucci <angelo.compagnucci@gmail.com> writes:
>>
>> > This patch series should fix the latest build failures for mono.
>> > Fixes http://autobuild.buildroot.net/results/227/227f942107e4fcbc14bb1e7d97e1e2758d6f3f2d/
>>
>> It unfortunately doesn't sem to have fixed the issue :/
>>
>> http://autobuild.buildroot.net/results/81a/81aadff4232cf1f1c36d8effe309a87d706b858f/build-end.log
>
> That's really unfortunate cause on my test machine everithing goes
> well. I tested up to make -j32 and make without arguments, never
> encountered that problem.
>
> Could you suggest a better way to find the root cause of the bug?
This issue look like the imagemagick one:
http://git.buildroot.net/buildroot/commit/?id=7395ee9d3b88e45798143e05a28d6d4b51409130
You need to find by looking the Makefile from which targets the same file can be
installed.
Not easy though.
Best regards,
Romain
>
> Sincerely, Angelo
>
>>
>> --
>> Bye, Peter Korsgaard
>
>
>
next prev parent reply other threads:[~2015-05-11 20:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 8:41 [Buildroot] [PATCH 0/3] Mono: fixing latest build failures Angelo Compagnucci
2015-05-09 8:41 ` [Buildroot] [PATCH 1/3] package/mono: fixing mono version Angelo Compagnucci
2015-05-09 8:41 ` [Buildroot] [PATCH 2/3] package/mono: adding hash file Angelo Compagnucci
2015-05-09 8:41 ` [Buildroot] [PATCH 3/3] package/monolite: " Angelo Compagnucci
2015-05-11 7:05 ` [Buildroot] [PATCH 0/3] Mono: fixing latest build failures Peter Korsgaard
2015-05-11 20:36 ` Peter Korsgaard
2015-05-11 20:44 ` Angelo Compagnucci
2015-05-11 20:55 ` Romain Naour [this message]
2015-05-12 5:55 ` Angelo Compagnucci
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=55511741.7090802@openwide.fr \
--to=romain.naour@openwide.fr \
--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