Bug 414331 – [x11-overlay] mesa-9999 has bad llvm check

• Status: RESOLVED UPSTREAM
• Product: Gentoo Linux

[Description Patrick Lauer 2012-05-02 04:56:53 UTC]

./configure around line 22514:

if test "x$LLVM_VERSION" != "x3.1"; then
                    as_fn_error $? "LLVM 3.1 is required for the r600 llvm compiler." "$LINENO" 5
                fi

llvm-9999 currently claims:
 # llvm-config --version
3.2svn

which leads to:

checking for RADEON... yes
configure: error: LLVM 3.1 is required for the r600 llvm compiler.

!!! Please attach the following file when seeking support:
!!! /chroot/build/portage/media-libs/mesa-9999/work/Mesa-9999/config.log
 * ERROR: media-libs/mesa-9999 failed (configure phase):
 *   econf failed

[Comment 1 Chí-Thanh Christopher Nguyễn 2012-05-02 09:10:43 UTC]

A quick workaround is to build llvm-9999 from the release_31 branch instead of trunk.

[Comment 2 Matt Turner 2012-05-02 15:37:25 UTC]

The plan is to move the backend out of Mesa and into LLVM for the 3.2 release.

[Comment 3 Jason Lamb 2012-05-03 17:14:46 UTC]

Is there some way to build llvm-9999 from the release_31 branch instead of the trunk using the live ebuild, in order to work around this issue?

[Comment 4 Chí-Thanh Christopher Nguyễn 2012-05-03 20:20:31 UTC]

(In reply to comment #3)

Yes, by setting ESVN_REPO_URI=http://llvm.org/svn/llvm-project/llvm/branches/release_31/

[Comment 5 Jason Lamb 2012-05-03 21:28:03 UTC]

(In reply to comment #4)
> (In reply to comment #3)
> 
> Yes, by setting
> ESVN_REPO_URI=http://llvm.org/svn/llvm-project/llvm/branches/release_31/

Sorry. I should have previously stated that I tried that first, and while the correct source was checked out, the emerge failed trying to apply the first patch, llvm-2.6-commandguide-nops.patch.

I imagine this works if llvm is manually installed from svn using the release_31 branch. Otherwise it looks like in order to use the x11 overlay mesa-9999, we need to wait until it's updated for llvm 3.2, as Matt indicated.

Thanks..

[Comment 6 Jason Lamb 2012-05-04 01:01:44 UTC]

(In reply to comment #4)
> (In reply to comment #3)
> 
> Yes, by setting
> ESVN_REPO_URI=http://llvm.org/svn/llvm-project/llvm/branches/release_31/

Please ignore my previous comment, (#5), about not being able to do this. When I tried it previously, I stupidly copied the modified llvm-9999 ebuild to my local overlay without the files directory. Once I did that, and commented out the llvm-3.2-nodoctargz.patch from the llvm-9999.ebuild, llvm svn 3.1 installed, without issue. I was then able to emerge the current x11 overlay mesa-9999 ebuild without issue.

BTW, I don't know if it makes a difference but my llvm-9999 ebuild SVN repo modification included quotes, and did not include the trailing /, (matching the original).

ESVN_REPO_URI="http://llvm.org/svn/llvm-project/llvm/branches/release_31"

Thanks..

[Comment 7 Matt Turner 2013-02-12 03:00:26 UTC]

This has been changed upstream to:

    LLVM_REQUIRED_VERSION_MAJOR="3"
    LLVM_REQUIRED_VERSION_MINOR="2"
    if test "$LLVM_VERSION_INT" -lt "${LLVM_REQUIRED_VERSION_MAJOR}0${LLVM_REQUIRED_VERSION_MINOR}"; then
       ...

so I'm going to mark this as RESOLVED/UPSTREAM. Reopen if you think it's not. (Should be fixed in 9.1_rc1 and 9999).