From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] glmark2 build failure
Date: Tue, 8 Oct 2019 23:02:31 +0200 [thread overview]
Message-ID: <20191008230231.11da9a76@gmx.net> (raw)
In-Reply-To: <CAOMZO5BiMG8TWDd93abA2aWXCyTZ3c7LYByg907oMCTmhqcQTg@mail.gmail.com>
Hello *,
On Mon, 7 Oct 2019 12:53:09 -0300, Fabio Estevam <festevam@gmail.com> wrote:
> Hi Thomas,
>
> On Mon, Oct 7, 2019 at 12:36 PM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> >
> > Hello,
> >
> > +Bernd in Cc.
> >
> > On Mon, 7 Oct 2019 11:01:12 -0300
> > Fabio Estevam <festevam@gmail.com> wrote:
> >
> > > --prefix=/usr --libdir=/usr/lib --prefix=/usr --with-flavors=
> >
> > --with-flavors is empty
> >
> > I guess it's a fallout of cf66a67112cd706d2e71665e45e8f6453fd53963. Do
> > you have udev enabled in your configuration ? If not that's the
>
> imx6-sabresd_qt5_defconfig does not select udev, so no, I don't have it enabled.
Changing
System-Configuration --> /dev management --> Dyanmic using devtempfs + mdev
to
System-Configuration --> /dev management --> Dyanmic using devtempfs + eudev
fixes the glmark2 compile failure for the imx6-sabresd_qt5_defconfig...
Regards,
Peter
>
> Regards,
>
> Fabio Estevam
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2019-10-08 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 14:01 [Buildroot] glmark2 build failure Fabio Estevam
2019-10-07 15:36 ` Thomas Petazzoni
2019-10-07 15:53 ` Fabio Estevam
2019-10-08 21:02 ` Peter Seiderer [this message]
2019-10-09 17:26 ` Fabio Estevam
2019-10-07 21:18 ` Arnout Vandecappelle
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=20191008230231.11da9a76@gmx.net \
--to=ps.report@gmx.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.