Bug 2003 - RFE: Update xc/extras/Mesa/ to Mesa 6.2
Summary: RFE: Update xc/extras/Mesa/ to Mesa 6.2
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Ext/GLX (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-02 20:37 UTC by Roland Mainz
Modified: 2004-12-13 22:56 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments
[FIXED_X11R68x] probable-6.2.1-update.patch.gz (1.53 MB, application/x-gzip)
2004-12-12 23:25 UTC, Adam Jackson
roland.mainz: 6.8-branch+
Details

Description Roland Mainz 2004-12-02 20:37:04 UTC
RFE: Please update xc/extras/Mesa/ to Mesa 6.2.
Comment 1 Adam Jackson 2004-12-12 23:25:13 UTC
Created attachment 1535 [details]
[FIXED_X11R68x] probable-6.2.1-update.patch.gz

i believe, if you were to import 6.2.1 into Xorg, that the diff between the
last 6.1 import and the resulting MESA branch head would look like this.  i'll
do the import against the live tree in the morning, when i'm not so groggy.

rather than applying this patch, there should be a proper import, and then the
MESA-6_2_1-2004121X tagged files should also be tagged XORG-6_8_2 at release. 
something like:

cvs -d[...]/cvs/xorg rtag -r MESA-6_2_1-2004121X XORG-6_8_2 xc/extras/Mesa
Comment 2 Adam Jackson 2004-12-12 23:26:38 UTC
Comment on attachment 1535 [details]
[FIXED_X11R68x] probable-6.2.1-update.patch.gz

nominating Mesa 6.2.1 for inclusion; this patch represents the changes that
would be applied.
Comment 3 Eric Anholt 2004-12-13 01:08:52 UTC
The normal procedure for this would be something along these lines (minus
spelling errors, etc.):
Do import as normal for HEAD
  cd /usr/src
  cvs -d(xorg) co xc
  cd /usr/src
  cvs -d(mesa) co -rmesa-6_2-branch Mesa
  cd Mesa
  rm -rf `cat /usr/src/xc/extras/Mesa/XOrg-Xlist`
  cvs -d(xorg) import xc/extras/Mesa MESA MESA-6_2-20041213
  cd xc/extras/Mesa
  cvs up -jMESA:yesterday -jMESA
  (resolve conflicts)
  cvs ci -m "resolve conflicts from MESA-6_2-20041213 import"
  (Build & test)
Update 6_8 branch:
  cd /usr/src/xc
  cvs up -Pd -rXORG-6_8-branch
  cd xc/extras/Mesa
  cvs up -jMESA
  (resolve conflicts)
  (Build & test)
  cvs ci -m "Merge MESA-6_2-20041213 to 6.8"
Release 6.8.

Now, hopefully we'll have 6.2.1 instead of a snapshot of 6.2, but this is the
general idea, I think.  I'm not 100% sure on the arguments for cvs up -jMESA,
having not done it, but I guess my point is that tagging is not what we want
here.  And don't forget the XOrg-Xlist step, which I don't think I'd mentioned
before.
Comment 4 Adam Jackson 2004-12-13 07:37:31 UTC
(In reply to comment #3)
> The normal procedure for this would be something along these lines (minus
> spelling errors, etc.):
> Do import as normal for HEAD
>   cd /usr/src
>   cvs -d(xorg) co xc
>   cd /usr/src
>   cvs -d(mesa) co -rmesa-6_2-branch Mesa

Shouldn't this be "co -r MESA-6_2_1"? ie not the tip of the branch but the
release snapshot.  6.2.1 has been tagged.

>   cd Mesa
>   rm -rf `cat /usr/src/xc/extras/Mesa/XOrg-Xlist`
>   cvs -d(xorg) import xc/extras/Mesa MESA MESA-6_2-20041213
>   cd xc/extras/Mesa
>   cvs up -jMESA:yesterday -jMESA
>   (resolve conflicts)
>   cvs ci -m "resolve conflicts from MESA-6_2-20041213 import"
>   (Build & test)
> Update 6_8 branch:
>   cd /usr/src/xc
>   cvs up -Pd -rXORG-6_8-branch
>   cd xc/extras/Mesa
>   cvs up -jMESA
>   (resolve conflicts)
>   (Build & test)
>   cvs ci -m "Merge MESA-6_2-20041213 to 6.8"
> Release 6.8.

Okay, that makes sense.

> Now, hopefully we'll have 6.2.1 instead of a snapshot of 6.2, but this is the
> general idea, I think.  I'm not 100% sure on the arguments for cvs up -jMESA,
> having not done it, but I guess my point is that tagging is not what we want
> here.  And don't forget the XOrg-Xlist step, which I don't think I'd mentioned
> before.

I don't remember you mentioning it, thanks.
Comment 6 Roland Mainz 2004-12-14 11:46:13 UTC
Comment on attachment 1535 [details]
[FIXED_X11R68x] probable-6.2.1-update.patch.gz

Approval for X11R6.8.x stable branch granted in the 2004-12-13
release-wranglers phone call.

ajax: I'll talk to you later today about the commit details...
Comment 7 Roland Mainz 2004-12-14 14:50:55 UTC
It seems the Mesa upgrade to Mesa 6.2 was incomplete - trying to build
it on SuSE 8.2 results in the following compillation error:
-- snip --
rm -f program.h
ln -s ../../../../extras/Mesa/src/mesa/shader/program.h program.h
make[5]: *** No rule to make target
`../../../../extras/Mesa/src/mesa/shader/shaderobjects.c', needed by
Stop.
make[5]: Leaving directory
`/home/gismobile/projects/xorg/work005/xc/lib/GL/mesa/shader'
make[4]: *** [includes] Error 2
make[4]: Leaving directory
`/home/gismobile/projects/xorg/work005/xc/lib/GL/mesa'
make[3]: *** [includes] Error 2
make[3]: Leaving directory
`/home/gismobile/projects/xorg/work005/xc/lib/GL'
make[2]: *** [includes] Error 2
make[2]: Leaving directory
`/home/gismobile/projects/xorg/work005/xc/lib'
make[1]: *** [includes] Error 2
make[1]: Leaving directory `/home/gismobile/projects/xorg/work005/xc'
make: *** [World] Error 2
-- snip --
Comment 8 Adam Jackson 2004-12-14 17:56:29 UTC
Mesa 6.2.1 merged to both HEAD and 6.8 branch, closing.

sorry about that shaderobjects bug, should be fixed.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.