From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 00/37] efl bump to 1.14.2
Date: Mon, 24 Aug 2015 23:42:07 +0200 [thread overview]
Message-ID: <55DB8FAF.7060509@openwide.fr> (raw)
In-Reply-To: <CAAMcf8COScfy62sEC4uPKHw=LgyLWWtic9ypCF0DZMfu21hzdg@mail.gmail.com>
Hi Vicente
Le 21/08/2015 19:56, vj a ?crit :
> Hello Romain,
>
> On Fri, Aug 21, 2015 at 10:51 AM, Romain Naour <romain.naour@openwide.fr> wrote:
>> Hi Vicente,
>>
>> Le 21/08/2015 02:30, vj a ?crit :
>>> Hello Romain,
>>> I've tested you efl update
>>> https://github.com/RomainNaour/buildroot/tree/efl-1.15.0-v1
>>> It did not work, :(
>>> But applying the two patches below works again!
>>> The first one was already commented in a previous e-mail.
>>
>> Yes, sorry I haven't looked at your issue yet.
>>
>> libmount seems to be optional and can be disabled with --disable-libmount:
>> https://github.com/RomainNaour/buildroot/blob/efl-1.15.0-v1/package/efl/efl.mk#L35
>
> Without that dependency it failed with 1.14.2.
> When I saw the dependency was not there in 1.15.0, I just added it
> again without checking.
> Just now I've tried it again without that patch and it's fine, so, you
> can forget it.
> Sorry for the hassle.
It's ok ;-) I haven't heavily tested with a minimal config.
Maybe next time can you post the last ~100 build log lines, it not always easy
to reproduce a build issue...
>
>>
>> But since it's not recommended to disable it, I'll apply your patch :)
>>
>>> The second is related to a regression in efl-1.15.0.
>>
>> Can you report your issue to the efl mailing list ?
>
> I know it would be better to have it fixed upstream, but have no time
> for that now.
> If you would like to, feel free to report it.
> To debug it, it helps enabling the WRN and DGB macros in eina_module.c.
Well, I can't really report an issue that I can't reproduce.
See, I reported the issue about SDL2 dependency and it's now fixed in the efl
1.15.1. So, I can drop the last patch and avoid to autoreconf the package.
Also, I'm probably not the good person to report an efl issue.
Honestly, I don't know what to do with -fvisibility=default.
It would be better if you can send just an email to the enlightenment mailing
list to report your issue.
>
>>
>>> The testing I've done has been with the musl libc and with
>>> BR2_PACKAGE_EFL_RECOMMENDED_CONFIG unset.
>>> Basically the same config as in the previous e-mail.
>>>
>>> A minor issue: check the spelling of recommanded.
>>
>> Ha indeed recommanded is used in Config.in prompt
>> (my French was turned on sorry ;-) )
>>
>> Thanks for testing!
>
> Thanks for adding musl and maintaining efl!
You're welcome!
Best regards,
Romain
next prev parent reply other threads:[~2015-08-24 21:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 0:30 [Buildroot] [RFC 00/37] efl bump to 1.14.2 vj
2015-08-21 9:51 ` Romain Naour
2015-08-21 10:18 ` Romain Naour
2015-08-21 17:56 ` vj
2015-08-24 21:42 ` Romain Naour [this message]
2015-08-24 22:09 ` vj
2015-09-05 14:55 ` Romain Naour
2015-09-27 0:37 ` vj
2015-09-28 21:00 ` Romain Naour
2015-10-05 19:41 ` [Buildroot] efl: fix framebuffer support Vicente Bergas
2015-10-05 19:41 ` Vicente Bergas
2015-10-09 21:32 ` Romain Naour
2015-10-09 21:04 ` Romain Naour
-- strict thread matches above, loose matches on Subject: below --
2015-08-03 18:55 [Buildroot] [RFC 00/37] efl bump to 1.14.2 vj
2015-08-03 23:10 ` Romain Naour
2015-07-26 18:55 Romain Naour
2015-08-06 8:45 ` Romain Naour
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=55DB8FAF.7060509@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