Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] new package: libpciaccess
Date: Thu, 27 Dec 2012 21:08:59 +0200	[thread overview]
Message-ID: <50DC9CCB.8060304@petroprogram.com> (raw)
In-Reply-To: <50DC925D.4050805@petroprogram.com>

27.12.2012 20:24, Stefan Fr?berg kirjoitti:
> Hi Thomas
>
> 23.12.2012 17:20, Thomas Petazzoni kirjoitti:
>> Dear Stefan Fr?berg,
>>
>> On Sun, 23 Dec 2012 16:04:16 +0200, Stefan Fr?berg wrote:
>>
>>> That mesa3d updating beyond 7.10.3 (that I have here) seems especially
>>> interesting challenge.
>> Do you have more details about the issues involved in bumping mesa3d
>> beyond 7.10.3 ?
>>
>> Thomas
> Well, if you try to bump it to 8.0.5 version, it will abort at some point.
>
> It borks at the time it tries to compile glsl.
>
> It tries to build helper program (builtin_compiler) with system python
> (shouldn't that be HOST_DIR/usr/bin/python ???)
> and then it crashes.
>
> I have included here the actual screenshot of the situation.
>
> Regards
> Stefan

Update:
The situation starts even earlier than 8.0.5. Right at version 7.11
And changing system python to buildroot python (MESA3D_CONF_ENV +=
PYTHON2= $(HOST_DIR)/usr/bin/python)
didn't change anything.

Regards
Stefan

  reply	other threads:[~2012-12-27 19:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-22 23:51 [Buildroot] [PATCH] new package: libpciaccess Stefan Fröberg
2012-12-23  9:15 ` Peter Korsgaard
2012-12-23 12:29   ` Stefan Fröberg
2012-12-23 13:58     ` Peter Korsgaard
2012-12-23 14:04       ` Stefan Fröberg
2012-12-23 15:20         ` Thomas Petazzoni
2012-12-27 18:24           ` Stefan Fröberg
2012-12-27 19:08             ` Stefan Fröberg [this message]
2012-12-27 20:43               ` Stefan Fröberg

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=50DC9CCB.8060304@petroprogram.com \
    --to=stefan.froberg@petroprogram.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