2015-10-25 4 views
0

Я настраиваю IcedTea 2.6.2 для сборки OpenJDK с помощью ZeroShark. Для того, чтобы IcedTea я установил следующие пакеты зависимостей:Конфигурация IcedTea 2.6.2: «llvm-config: ошибка: компоненты указаны, но не используются»

sudo apt-get install zip gawk xsltproc libjpeg8-dev libgif-dev libpng12-dev liblcms2-dev libgtk2.0-dev cups libcups2-dev libc6-dev libattr1-dev libalsa-ocaml-dev libsctp-dev libXtst-dev libffi-dev llvm-3.6-dev 

Настройка IcedTea, прежде чем сделать:

./configure --enable-zero --enable-shark --with-rhino=no 

Но я застрял на этом шаге. Ниже приведен вывод конфигурации:

checking for llvm-config... /usr/bin/llvm-config 
llvm-config: error: components given, but unused 

usage: llvm-config <OPTION>... [<COMPONENT>...] 

Get various configuration information needed to compile programs which use 
LLVM. Typically called from 'configure' scripts. Examples: 
    llvm-config --cxxflags 
    llvm-config --ldflags 
    llvm-config --libs engine bcreader scalaropts 

Options: 
    --version   Print LLVM version. 
    --prefix   Print the installation prefix. 
    --src-root  Print the source root LLVM was built from. 
    --obj-root  Print the object root used to build LLVM. 
    --bindir   Directory containing LLVM executables. 
    --includedir  Directory containing LLVM headers. 
    --libdir   Directory containing LLVM libraries. 
    --cppflags  C preprocessor flags for files that include LLVM headers. 
    --cflags   C compiler flags for files that include LLVM headers. 
    --cxxflags  C++ compiler flags for files that include LLVM headers. 
    --ldflags   Print Linker flags. 
    --system-libs  System Libraries needed to link against LLVM components. 
    --libs   Libraries needed to link against LLVM components. 
    --libnames  Bare library names for in-tree builds. 
    --libfiles  Fully qualified library filenames for makefile depends. 
    --components  List of all possible components. 
    --targets-built List of all targets currently built. 
    --host-target  Target triple used to configure LLVM. 
    --build-mode  Print build mode of LLVM tree (e.g. Debug or Release). 
    --assertion-mode Print assertion mode of LLVM tree (ON or OFF). 
Typical components: 
    all    All LLVM libraries (default). 
    engine   Either a native JIT or a bitcode interpreter. 
llvm-config: error: components given, but unused 

usage: llvm-config <OPTION>... [<COMPONENT>...] 

Get various configuration information needed to compile programs which use 
LLVM. Typically called from 'configure' scripts. Examples: 
    llvm-config --cxxflags 
    llvm-config --ldflags 
    llvm-config --libs engine bcreader scalaropts 

Options: 
    --version   Print LLVM version. 
    --prefix   Print the installation prefix. 
    --src-root  Print the source root LLVM was built from. 
    --obj-root  Print the object root used to build LLVM. 
    --bindir   Directory containing LLVM executables. 
    --includedir  Directory containing LLVM headers. 
    --libdir   Directory containing LLVM libraries. 
    --cppflags  C preprocessor flags for files that include LLVM headers. 
    --cflags   C compiler flags for files that include LLVM headers. 
    --cxxflags  C++ compiler flags for files that include LLVM headers. 
    --ldflags   Print Linker flags. 
    --system-libs  System Libraries needed to link against LLVM components. 
    --libs   Libraries needed to link against LLVM components. 
    --libnames  Bare library names for in-tree builds. 
    --libfiles  Fully qualified library filenames for makefile depends. 
    --components  List of all possible components. 
    --targets-built List of all targets currently built. 
    --host-target  Target triple used to configure LLVM. 
    --build-mode  Print build mode of LLVM tree (e.g. Debug or Release). 
    --assertion-mode Print assertion mode of LLVM tree (ON or OFF). 
Typical components: 
    all    All LLVM libraries (default). 
    engine   Either a native JIT or a bitcode interpreter. 
checking for LLVMGetNextInstruction in -lLLVM-3.5.0... yes 
checking that generated files are newer than configure... done 
configure: creating ./config.status 
config.status: creating Makefile 
config.status: creating hotspot.map 
config.status: creating fsg.sh 
config.status: creating jconsole.desktop 
config.status: creating policytool.desktop 
config.status: creating nss.cfg 
config.status: creating linux.fontconfig.Gentoo.properties 
config.status: creating javac 
config.status: creating javap 
config.status: creating javah 
config.status: creating tz.properties 
config.status: creating pax-mark-vm 
config.status: creating remove-intree-libraries.sh 
config.status: creating tapset/hotspot.stp 
config.status: creating tapset/hotspot_jni.stp 
config.status: creating tapset/jstack.stp 
config.status: creating tapset/hotspot_gc.stp 
config.status: executing depfiles commands 

Я использую X86_64 ubuntu. Любая помощь будет принята с благодарностью.

Спасибо

ответ

0

Вы должны использовать очень конкретную версию LLVM для того, чтобы использовать Shark. IIRC, это что-то вроде 3.4 или аналогичной (старой) версии.

+0

Я уже пробовал LLVM 3.4 и переключился на старый IcedTea-2.5.6, но не смог решить проблему. Знание того, как проверяется llvm, может, вероятно, рассказать нам о причине проблемы. Я прочитал скрипт configure, но все еще не могу понять. –

 Смежные вопросы

  • Нет связанных вопросов^_^