From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] MesaLib
Date: Thu, 29 Aug 2013 11:03:12 +0200 [thread overview]
Message-ID: <20130829110312.0cea5997@skate> (raw)
In-Reply-To: <521F0A7A.5010906@lucaceresoli.net>
Dear Luca Ceresoli,
On Thu, 29 Aug 2013 10:46:50 +0200, Luca Ceresoli wrote:
> >> Should 7.10.3 be in the repository or is the buildroot source wrong?
> > The sources.buildroot.net mirror is updated only when a Buildroot
> > release is made. The last stable release is currently 2013.05, which
> > was using MesaLib 7.10.1, which explains why it is available from our
> > mirror.
>
> Indeed not:
>
> $ git show 2013.05:package/x11r7/mesa3d/mesa3d.mk | grep VERSION
> MESA3D_VERSION = 7.10.3
> MESA3D_SOURCE = MesaLib-$(MESA3D_VERSION).tar.gz
> MESA3D_SITE = ftp://ftp.freedesktop.org/pub/mesa/$(MESA3D_VERSION)
> $
Doh, you're right. The commit was from June 2012, not June 2013! So
indeed 2013.05 already pointed to 7.10.3. Sorry for the confusion :-(
So indeed, there's something wrong going on with how the mirror is
updated. We've had 7.10.3 since almost a year and it's not in our
mirror.
> But the sources on ftp.freedesktop.org have been moved from pub/mesa/7.10.3/
> topub/mesa/old_versions/7.x/7.10.3/, apparently around Aug 12th, 2013.
> This is unfortunately a recurring bad habit.:(
>
> Has anybody here ever asked the freedesktop guys to refrain from moving
> files around?
I don't think we ever did that for Mesa.
> > The bump to 7.10.3 was done by commit
> > 53cea4462c67a6707bf8dad83fa928262e44fce9 in June 2013, i.e after the
> > 2013.05 release. Since the 2013.08 release hasn't been made yet, I
> > believe Peter has not updated the Buildroot mirror, and therefore it
> > doesn't contain for the moment all the new versions of the tarballs
> > that have been upgraded since 2013.05.
>
> Apparently this was not done for 2013.05, or it didn't work for mesa3d.
> Peter, any idea? Otherwise, can you force the download now to fix this?
>
> Anyway, 7.10.3 that is a pretty old release (~2 years old), there are
> many more
> recent ones. Ryan, you may try to bump version. Releases since 8.0 are
> in the
> "standard" download directory at ftp.freedesktop.org.
Note that Spenser Gilliland is currently reworking the Mesa package
quite significantly. In the recently posted "[Buildroot] [PATCH 4/6]
mesa3d: reorganize, modularize, and bump to version 9.1.6", he bumped
Mesa to a recent version.
> Or, for a quick workaround, you may just change the URL in
> package/x11r7/mesa3d/mesa3d.mk.
Can you cook a patch for mesa3d.mk to fix this for the 2013.08 release
(since Spenser patch will not be part of 2013.08) ?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-08-29 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 23:22 [Buildroot] MesaLib Ryan Wilkins
2013-08-29 8:26 ` Thomas Petazzoni
2013-08-29 8:46 ` Luca Ceresoli
2013-08-29 9:03 ` Thomas Petazzoni [this message]
2013-08-29 13:30 ` Peter Korsgaard
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=20130829110312.0cea5997@skate \
--to=thomas.petazzoni@free-electrons.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 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.