install_deps.sh does not actually download corresponding CLANG sources for LLVM versions 3.3, 3.4.1, 3.4.2 #40871

Closed
opened 2014-06-29 14:35:27 +02:00 by Simon Repp · 5 comments

Fighting with building Blender on Fedora 20 (http://stackoverflow.com/questions/24327680/building-blender-on-fedora-20-osl-compilation-failing-due-to-llvm-clang-mismat) I discovered the following:

Within install_deps.sh the corresponding CLANG sources for any respective LLVM version are obtained through the following logic:


- ver-llvm=x.x.x (optionally as a shell parameter, otherwise defaults to values below)
LLVM_VERSION="3.3"
LLVM_VERSION_MIN="3.3"
...
LLVM_CLANG_SOURCE="http://llvm.org/releases/$LLVM_VERSION/clang-$LLVM_VERSION.src.tar.gz"
...
wget -c $LLVM_CLANG_SOURCE -O "$_src_clang.tar.gz"

This was probably introduced somewhere around the release of LLVM 3.0, where this url naming scheme first shows up (See http://llvm.org/releases/download.html), but for whatever reasons, versions 3.3, 3.4.1 and 3.4.2 use a different naming scheme (cfe-x.x.x.src.tar.gz instead of clang-x.x.x.src.tar.gz), thus everyone who runs install_deps.sh for these LLVM versions (and by default most people should in fact be running it for 3.3) obtains no CLANG at all (a 0 byte file is downloaded in these error cases, compilation silently does not occur, no errors whatsoever as far as i have seen), and the success of the build process depends fully on another CLANG being present on system level.

Writing a fix isn't really the problem here, but as there are multiple ways we could deal with this, especially how to handle the uncertainty on the naming scheme for future CLANG releases, I thought I'd bring it up for review and discussion first.

Fighting with building Blender on Fedora 20 (http://stackoverflow.com/questions/24327680/building-blender-on-fedora-20-osl-compilation-failing-due-to-llvm-clang-mismat) I discovered the following: Within `install_deps.sh` the corresponding CLANG sources for any respective LLVM version are obtained through the following logic: ``` ``` - ver-llvm=x.x.x (optionally as a shell parameter, otherwise defaults to values below) ``` LLVM_VERSION="3.3" LLVM_VERSION_MIN="3.3" ... LLVM_CLANG_SOURCE="http://llvm.org/releases/$LLVM_VERSION/clang-$LLVM_VERSION.src.tar.gz" ... wget -c $LLVM_CLANG_SOURCE -O "$_src_clang.tar.gz" ``` This was probably introduced somewhere around the release of LLVM 3.0, where this url naming scheme first shows up (See http://llvm.org/releases/download.html), but for whatever reasons, versions 3.3, 3.4.1 and 3.4.2 use a different naming scheme (cfe-x.x.x.src.tar.gz instead of clang-x.x.x.src.tar.gz), thus everyone who runs `install_deps.sh` for these LLVM versions (and by default most people should in fact be running it for 3.3) obtains no CLANG at all (a 0 byte file is downloaded in these error cases, compilation silently does not occur, no errors whatsoever as far as i have seen), and the success of the build process depends fully on another CLANG being present on system level. Writing a fix isn't really the problem here, but as there are multiple ways we could deal with this, especially how to handle the uncertainty on the naming scheme for future CLANG releases, I thought I'd bring it up for review and discussion first.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @simonrepp

Added subscriber: @simonrepp

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2014-06-29 17:34:39 +02:00

Please do not make bug reports about building issues, those do not belong here (best is to use IRC, or ML).

That said, I’ll investigate the issue and fix it asap.

Please do not make bug reports about building issues, those do not belong here (best is to use IRC, or ML). That said, I’ll investigate the issue and fix it asap.
Author

Thanks for looking into it!

Just for the record: I even went on IRC to clarify if this was the right place to report the bug (and got green light from Lukas Tönne, which sufficed for me), but yeah, everyone is entitled to their own opinion of course, and this is kind of a corner case (being a building issue that's not related not to the user's system, but to the code in blender's git repo!) :)

Thanks for looking into it! Just for the record: I even went on IRC to clarify if this was the right place to report the bug (and got green light from Lukas Tönne, which sufficed for me), but yeah, everyone is entitled to their own opinion of course, and this is kind of a corner case (being a building issue that's not related not to the user's system, but to the code in blender's git repo!) :)
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#40871
No description provided.