OSX Mavericks: Automake and Autoconf issue

Home Forums Forum OSX Mavericks: Automake and Autoconf issue

This topic contains 7 replies, has 2 voices, and was last updated by  Mike 6 years, 4 months ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #1517

    Gordon

    I’ve been trying to build ellcc on Mavericks. My current version of automake was 1-1.4 and there were some error messages regarding it not being able to find automake-1.1.3

    I removed 1-1.4 and installed 1-1.3 from sources – it all tests ok, but now i get the following messages:
    configure.ac:532: the top level
    configure.ac:586: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
    ../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from…
    ../../lib/autoconf/general.m4:2670: _AC_LINK_IFELSE is expanded from…
    ../../lib/autoconf/general.m4:2680: AC_LINK_IFELSE is expanded from…
    configure.ac:586: the top level
    configure.ac:67: error: possibly undefined macro: AM_CONFIG_HEADER
    If this token and others are legitimate, please use m4_pattern_allow.
    See the Autoconf documentation.
    autoreconf: /usr/local/Cellar/autoconf/2.69/bin/autoconf failed with exit status: 1
    make: *** [/Users/gordon/Applications/ellcc/gnu/src/qemu/pixman/configure] Error 1
    make: *** Deleting file `/Users/gordon/Applications/ellcc/gnu/src/qemu/pixman/configure’

    my autoconf version is 2.69:

    gordons-mbp-3:ellcc gordon$ autoconf –version
    autoconf (GNU Autoconf) 2.69
    Copyright (C) 2012 Free Software Foundation, Inc.
    License GPLv3+/Autoconf: GNU GPL version 3 or later
    <http://gnu.org/licenses/gpl.html&gt;, <http://gnu.org/licenses/exceptions.html&gt;
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law.

    Written by David J. MacKenzie and Akim Demaille.

    Any advice would be appreciated on how to get across the line 🙂

    #1518

    Gordon

    Note, when i said “I removed 1-1.4 and installed 1-1.3 from sources – it all tests ok, ” I meant the the installation of automake tested OK… – The build still failed.

    #1519

    rich
    Keymaster

    Hi Gordon,

    You may be able to fix the issue by going into /Users/gordon/Applications/ellcc/gnu/src/qemu/pixman/
    and running “autoreconf”. The GNU configure stuff is kind of a black box to me.
    -Rich

    #1521

    Gordon

    I found that my installation of 1-1.3 did not work properly, so I went back to 1-1.4 with the original error. (make[2]: *** [../../../src/libedit/aclocal.m4] Error 127) – Any ideas or clues as to where I should start digging?

    config.status: executing libtool commands
    make -C libedit-build/arm/linux
    CDPATH=”${ZSH_VERSION+.}:” && cd ../../../src/libedit && /bin/sh /Users/gordon/Applications/ellcc/libecc/src/libedit/missing aclocal-1.13 -I m4
    /Users/gordon/Applications/ellcc/libecc/src/libedit/missing: line 81: aclocal-1.13: command not found
    WARNING: ‘aclocal-1.13’ is missing on your system.
    You should only need it if you modified ‘acinclude.m4’ or
    ‘configure.ac’ or m4 files included by ‘configure.ac’.
    The ‘aclocal’ program is part of the GNU Automake package:
    <http://www.gnu.org/software/automake&gt;
    It also requires GNU Autoconf, GNU m4 and Perl in order to run:
    <http://www.gnu.org/software/autoconf&gt;
    <http://www.gnu.org/software/m4/&gt;
    <http://www.perl.org/&gt;
    make[2]: *** [../../../src/libedit/aclocal.m4] Error 127
    make[1]: *** [arm.libedit.build] Error 2
    make: *** [arm] Error 2

    #1522

    Gordon

    Hi Rich, I ran autoreconf (no arguements?) and got a whole listing that looks like this:

    configure.ac:586: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
    ../../lib/autoconf/lang.m4:197: AC_LANG_CONFTEST is expanded from…
    ../../lib/autoconf/general.m4:2670: _AC_LINK_IFELSE is expanded from…
    ../../lib/autoconf/general.m4:2680: AC_LINK_IFELSE is expanded from…
    configure.ac:586: the top level
    test/Makefile.am:2: warning: ‘INCLUDES’ is the old name for ‘AM_CPPFLAGS’ (or ‘*_CPPFLAGS’)

    Not sure if this is good or bad…

    Anyway, I’ll try to run build again and let you know what happens.

    #1523

    Gordon

    Hi Rich,
    I put a symbolic link in between version aclocal-1.13 and 1.14:
    gordons-mbp-3:bin gordon$ ls -als aclocal*
    8 lrwxr-xr-x 1 gordon admin 37 4 Feb 12:25 aclocal -> ../Cellar/automake/1.14.1/bin/aclocal
    8 lrwxr-xr-x 1 gordon admin 42 4 Feb 16:29 aclocal-1.13 -> ../Cellar/automake/1.14.1/bin/aclocal-1.14
    8 lrwxr-xr-x 1 gordon admin 42 4 Feb 12:25 aclocal-1.14 -> ../Cellar/automake/1.14.1/bin/aclocal-1.14
    This seemed to work better but still had some warnings:

    make -C libedit-build/arm/linux
    CDPATH=”${ZSH_VERSION+.}:” && cd ../../../src/libedit && /bin/sh /Users/gordon/Applications/ellcc/libecc/src/libedit/missing aclocal-1.13 -I m4
    cd ../../../src/libedit && /bin/sh /Users/gordon/Applications/ellcc/libecc/src/libedit/missing automake-1.13 –foreign
    CDPATH=”${ZSH_VERSION+.}:” && cd ../../../src/libedit && /bin/sh /Users/gordon/Applications/ellcc/libecc/src/libedit/missing autoconf
    /bin/sh ./config.status –recheck

    later it still bombed out compiling some examples:

    CCLD libedit.la
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: warning for library: .libs/libedit.a the table of contents is empty (no object file members in the library define global symbols)
    Making all in examples
    CC tc1.o
    CCLD tc1
    tc1.o: In function `main’:
    /Users/gordon/Applications/ellcc/libecc/libedit-build/arm/linux/examples/tc1.c:146: undefined reference to `history_init’
    .
    .
    .
    .
    /Users/gordon/Applications/ellcc/libecc/libedit-build/arm/linux/examples/tc1.c:306: undefined reference to `history_end’
    tc1.o: In function `complete’:
    /Users/gordon/Applications/ellcc/libecc/libedit-build/arm/linux/examples/tc1.c:98: undefined reference to `el_line’
    /Users/gordon/Applications/ellcc/libecc/libedit-build/arm/linux/examples/tc1.c:114: undefined reference to `el_insertstr’
    ecc: error: linker command failed with exit code 1 (use -v to see invocation)
    make[4]: *** [tc1] Error 1
    make[3]: *** [all-recursive] Error 1
    make[2]: *** [all] Error 2
    make[1]: *** [arm.libedit.build] Error 2
    make: *** [arm] Error 2

    I’m not sure it this all stems from some hard reference in the makefile to aclocal-1.13 and me linking it to 1.14, or there are other issues. Can the owner of the Makefile or build script comment or hint at a workaround?

    Gordon.

    #1570

    RobertN

    I just did a build on OS-X 10.9.1 and a had a couple of issues:

    1) Qemu fails to link due to libintl not found. I have gettext installed via home-brew but it only gets used for ‘keg’ builds and it not normally linked into my path. I mod’d “ellcc/gnu/build” to force brew to symlink it in before the make and unlink it after, see the following link for my ‘quick hack’: http://sushihangover.github.io/ellcc-dot-org-build-fix-for-os-x/

    2) The second issue is on the making the “libecc” in the root build shell script. It fails with:
    `
    /Users/administrator/Code/ellcc/libecc/../bin/ecc -std=c99 -nostdinc -ffreestanding -frounding-math -D_XOPEN_SOURCE=700 -I./arch/arm -I./src/internal -I./include -g -pipe -fno-unwind-tables -fno-asynchronous-unwind-tables -Wa,–noexecstack -Werror=implicit-function-declaration -Werror=implicit-int -Werror=pointer-sign -Werror=pointer-arith -Wall -Wno-parentheses -Wno-uninitialized -Wno-missing-braces -Wno-unused-value -Wno-unknown-pragmas -fno-stack-protector -target arm-ellcc-linux-eabi -march=armv7 -mfpu=vfp -mfloat-abi=softfp -no-integrated-as -g -Qunused-arguments -Wno-unneeded-internal-declaration -Wno-cast-align -Wno-incompatible-pointer-types -Wno-string-plus-int -Wno-pointer-sign -Wno-array-bounds -Wno-dangling-else -Wno-int-to-pointer-cast -c -o src/bsd/parsedate.o src/bsd/parsedate.c
    y.tab.c:1409:16: error: implicit declaration of function ‘yylex’ is invalid in
    C99 [-Werror,-Wimplicit-function-declaration]
    yychar = YYLEX;
    ^
    `
    I have not looked into this and not sure if it is a known issue.

    I run the sanity checks and things do not look to bad if you remove the MBlaze failures:
    `
    ********************
    Testing Time: 354.74s
    ********************
    Failing Tests (25):
    LLVM :: BugPoint/crash-narrowfunctiontest.ll
    LLVM :: BugPoint/metadata.ll
    LLVM :: BugPoint/remove_arguments_test.ll
    LLVM :: CodeGen/MBlaze/DbgValueOtherTargets.test
    LLVM :: CodeGen/MBlaze/brind.ll
    LLVM :: CodeGen/MBlaze/callind.ll
    LLVM :: CodeGen/MBlaze/cc.ll
    LLVM :: CodeGen/MBlaze/div.ll
    LLVM :: CodeGen/MBlaze/fpu.ll
    LLVM :: CodeGen/MBlaze/fsl.ll
    LLVM :: CodeGen/MBlaze/imm.ll
    LLVM :: CodeGen/MBlaze/intr.ll
    LLVM :: CodeGen/MBlaze/jumptable.ll
    LLVM :: CodeGen/MBlaze/loop.ll
    LLVM :: CodeGen/MBlaze/mul.ll
    LLVM :: CodeGen/MBlaze/mul64.ll
    LLVM :: CodeGen/MBlaze/select.ll
    LLVM :: CodeGen/MBlaze/shift.ll
    LLVM :: CodeGen/MBlaze/svol.ll
    LLVM :: Feature/load_module.ll
    LLVM :: LTO/cfi_endproc.ll
    LLVM :: LTO/current-section.ll
    LLVM :: LTO/linkonce_odr_func.ll
    LLVM :: LTO/runtime-library.ll
    LLVM :: LTO/triple-init.ll

    Expected Passes : 9649
    Expected Failures : 59
    Unsupported Tests : 35
    Unexpected Failures: 25
    `
    ********************
    Testing Time: 354.74s
    ********************
    Failing Tests (25):
    LLVM :: BugPoint/crash-narrowfunctiontest.ll
    LLVM :: BugPoint/metadata.ll
    LLVM :: BugPoint/remove_arguments_test.ll
    LLVM :: CodeGen/MBlaze/DbgValueOtherTargets.test
    LLVM :: CodeGen/MBlaze/brind.ll
    LLVM :: CodeGen/MBlaze/callind.ll
    LLVM :: CodeGen/MBlaze/cc.ll
    LLVM :: CodeGen/MBlaze/div.ll
    LLVM :: CodeGen/MBlaze/fpu.ll
    LLVM :: CodeGen/MBlaze/fsl.ll
    LLVM :: CodeGen/MBlaze/imm.ll
    LLVM :: CodeGen/MBlaze/intr.ll
    LLVM :: CodeGen/MBlaze/jumptable.ll
    LLVM :: CodeGen/MBlaze/loop.ll
    LLVM :: CodeGen/MBlaze/mul.ll
    LLVM :: CodeGen/MBlaze/mul64.ll
    LLVM :: CodeGen/MBlaze/select.ll
    LLVM :: CodeGen/MBlaze/shift.ll
    LLVM :: CodeGen/MBlaze/svol.ll
    LLVM :: Feature/load_module.ll
    LLVM :: LTO/cfi_endproc.ll
    LLVM :: LTO/current-section.ll
    LLVM :: LTO/linkonce_odr_func.ll
    LLVM :: LTO/runtime-library.ll
    LLVM :: LTO/triple-init.ll

    Expected Passes : 9649
    Expected Failures : 59
    Unsupported Tests : 35
    Unexpected Failures: 25
    `

    clang --version
    Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
    Target: x86_64-apple-darwin13.0.0
    Thread model: posix
    
    
    make --version
    GNU Make 3.81
    Copyright (C) 2006  Free Software Foundation, Inc.
    
    
    automake --version
    automake (GNU automake) 1.14.1
    
    
    autoconf --version
    autoconf (GNU Autoconf) 2.69
    
    
    cmake --version
    cmake version 2.8.12.1
    
    #3851

    Mike

    On current OS X / homebrew, it’s failing with the autofoo-1.14 issue; then after symlinking, libedit’s examples fail with:

    CCLD tc1
    tc1.o: In function `main’:
    /Users/msmith/work/Mike/ellc/ellcc/libecc/libedit-build/arm/linux/examples/tc1.c:146: undefined reference to `history_init’
    /Users/msmith/work/Mike/ellc/ellcc/libecc/libedit-build/arm/linux/examples/tc1.c:148: undefined reference to `history’
    /Users/msmith/work/Mike/ellc/ellcc/libecc/libedit-build/arm/linux/examples/tc1.c:150: undefined reference to `tok_init’
    /Users/msmith/work/Mike/ellc/ellcc/libecc/libedit-build/arm/linux/examples/tc1.c:153: undefined reference to `el_init’

    /Users/msmith/work/Mike/ellc/ellcc/libecc/libedit-build/arm/linux/examples/tc1.c:114: undefined reference to `el_insertstr’
    ecc: error: linker command failed with exit code 1 (use -v to see invocation)
    make[4]: *** [tc1] Error 1
    make[3]: *** [all-recursive] Error 1
    make[2]: *** [all] Error 2
    make[1]: *** [arm.libedit.build] Error 2
    make: *** [arm] Error 2

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.