Menu

#85 Problem configuring glame

important
closed-wont-fix
6
2003-03-26
2002-04-16
Pierre
No

Hi,

I try to configure glame-0.6.2 and i got this :

[...]
configure: configuring in libltdl
configure: running /bin/sh './configure'
--prefix=/usr/local '--enable-shared'
'--enable-ladspa' 'CC=gcc' 'CFLAGS=-O3 -march=i686'
--enable-ltdl-convenience --cache-file=/dev/null --srcdir=.
configure: warning: CC=gcc: invalid host type
configure: warning: CFLAGS=-O3 -march=i686: invalid
host type
configure: error: can only configure for one host and
one target at a time
configure: error: /bin/sh './configure' failed for libltdl

It would be great if you could help me with this !

Best regards,

Pierre.

Discussion

1 2 > >> (Page 1 of 2)
  • Richard Guenther

    • assigned_to: nobody --> nold
     
  • Richard Guenther

    Logged In: YES
    user_id=7575

    You didnt supply the commandline for you configure command,
    but I suspect you did

    > ./configure CC=gcc

    or the like which is incorrect (configure thinks, CC=gcc is
    your host type override). Do

    > env CC=gcc ./configure

    instead, if you need to override CC.

     
  • Alexander Ehlert

    Logged In: YES
    user_id=7009

    Or could it just be that you didn't install the libltdl
    developer package?

     
  • Daniel Kobras

    Daniel Kobras - 2002-04-16

    Logged In: YES
    user_id=7832

    This is major suckage with Glame requiring autoconf 2.5, and
    libltdl designed for autoconf 2.13. The distributed
    configure script is the best I could do to at least let it
    compile with default options. If you want to override
    several options, make sure you have a version of libltdl
    installed in a global directory like /usr/lib, or
    /usr/local/lib, apply the patch attached to this bug report,
    and run autoconf (version 2.5 or higher!). The resulting
    configure script doesn't build its own libltdl any more and
    works fine with arbitrary overrides.

     
  • Daniel Kobras

    Daniel Kobras - 2002-04-16
     
  • Likai Liu

    Likai Liu - 2002-04-16

    Logged In: YES
    user_id=325449

    try to run automake && autoconf in both the distribution
    directory and the libltdl subdirectory. this solves the problem.

     
  • Pierre

    Pierre - 2002-04-16

    Logged In: YES
    user_id=512388

    >You didnt supply the commandline for you configure command,
    >but I suspect you did
    >
    >> ./configure CC=gcc
    >
    >or the like which is incorrect (configure thinks, CC=gcc is
    >your host type override). Do
    >
    >> env CC=gcc ./configure
    >
    >instead, if you need to override CC.

    No I only did ./configure --enable-shared --enable-ladspa
    it's the configure that recalls itself like this.

     
  • Pierre

    Pierre - 2002-04-16

    Logged In: YES
    user_id=512388

    >Or could it just be that you didn't install the libltdl
    >developer package?

    libltdl comes with libtool isn't it ?
    and i have the latest libtool installed.

     
  • Pierre

    Pierre - 2002-04-16

    Logged In: YES
    user_id=512388

    >This is major suckage with Glame requiring autoconf 2.5,
    >and libltdl designed for autoconf 2.13.

    I have autoconf 2.53 and libltdl from libtool 1.4.2

    >The distributed configure script is the best I could do to
    >at least let it compile with default options. If you want
    >to override several options, make sure you have a version
    >of libltdl installed in a global directory like /usr/lib, >
    >or /usr/local/lib,

    Yes I have :

    # ls -la /usr/local/lib/libltd*
    -rw-r--r-- 1 root root 81392 Mar 17 20:13
    /usr/local/lib/libltdl.a-rwxr-xr-x 1 root root
    710 Mar 17 20:13 /usr/local/lib/libltdl.la*
    lrwxrwxrwx 1 root root 16 Mar 17 20:13
    /usr/local/lib/libltdl.so -> libltdl.so.3.1.0*
    lrwxrwxrwx 1 root root 16 Mar 17 20:13
    /usr/local/lib/libltdl.so.3 -> libltdl.so.3.1.0*
    -rwxr-xr-x 1 root root 79096 Mar 17 20:13
    /usr/local/lib/libltdl.so.3.1.0*

    > apply the patch attached to this bug report,and run
    >autoconf (version 2.5 or higher!). The resulting configure
    >script doesn't build its own libltdl any more and
    >works fine with arbitrary overrides.

    Ok i have applied the patch, and rerun autoconf.
    But the problem still persists :/

     
  • Pierre

    Pierre - 2002-04-16

    Logged In: YES
    user_id=512388

    >try to run automake && autoconf in both the distribution
    >directory and the libltdl subdirectory. this solves the
    >problem.

    Ok this solution works, thank you.

     
  • Pierre

    Pierre - 2002-04-16

    Logged In: YES
    user_id=512388

    Now i got another problem :

    # gmake
    cd . && /bin/sh ./config.status config.h
    config.status: creating config.h
    config.status: config.h is unchanged
    gmake all-recursive
    gmake[1]: Entering directory `/tmp/glame-0.6.2'
    Making all in libltdl
    gmake[2]: Entering directory `/tmp/glame-0.6.2/libltdl'
    gmake all-am
    gmake[3]: Entering directory `/tmp/glame-0.6.2/libltdl'
    gmake[3]: Nothing to be done for `all-am'.
    gmake[3]: Leaving directory `/tmp/glame-0.6.2/libltdl'
    gmake[2]: Leaving directory `/tmp/glame-0.6.2/libltdl'
    Making all in macros
    gmake[2]: Entering directory `/tmp/glame-0.6.2/macros'
    gmake[2]: Nothing to be done for `all'.
    gmake[2]: Leaving directory `/tmp/glame-0.6.2/macros'
    Making all in src
    gmake[2]: Entering directory `/tmp/glame-0.6.2/src'
    Makefile:243: *** missing separator. Stop.
    gmake[2]: Leaving directory `/tmp/glame-0.6.2/src'
    gmake[1]: *** [all-recursive] Error 1
    gmake[1]: Leaving directory `/tmp/glame-0.6.2'
    gmake: *** [all] Error 2

     
  • Likai Liu

    Likai Liu - 2002-04-16

    Logged In: YES
    user_id=325449

    Make sure you extract a fresh copy of the source tree
    without the previously posted patch, and try again ;-). My
    autoconf is 2.53 and automake is 1.6, and both are correctly
    listed in `which autoconf` or `which automake` output. I use
    the these to generate configure script for both the
    distribution and the libltdl directories.

    Hope this helps.

     
  • Richard Guenther

    Logged In: YES
    user_id=7575

    I've seen the "missing separator" error only on non-Linux
    machines while _not_ using GNU make _and_ using a not
    pristine tarball. This is because of the dependency
    regeneration rules from automake need GNU make and are only
    omitted in the tarball generated with make dist. If you run
    autoconf/automake again, they will re-appear.

    But of course, you seem to use GNU make (is it recent
    enough?). Can you tell more about the system you're trying
    to compile glame on?

     
  • Pierre

    Pierre - 2002-04-16

    Logged In: YES
    user_id=512388

    >Make sure you extract a fresh copy of the source tree
    >without the previously posted patch, and try again ;-).

    It's what I have done

    >My autoconf is 2.53 and automake is 1.6, and both are >
    >correctly listed in `which autoconf` or `which automake`
    >output.

    I have autoconf-2.53 and automake-1.6.1

    >I use these to generate configure script for both the
    >distribution and the libltdl directories.

    I ran automake and autoconf in these directories too,
    because otherwise the configure don't succeed as I have
    reported. They output some warnings but i don't know if it's
    important.

    >Hope this helps.

    No, always the same error with "Makefile:243: *** missing
    separator. Stop."...

     
  • Pierre

    Pierre - 2002-04-16

    Logged In: YES
    user_id=512388

    >I've seen the "missing separator" error only on
    >non-Linux machines while _not_ using GNU make _and_ using a
    >not pristine tarball. This is because of the dependency
    >regeneration rules from automake need GNU make and are only
    >omitted in the tarball generated with make dist. If you run
    >autoconf/automake again, they will re-appear.

    It's what I have done, but it's the only solution to make
    configure works

    >But of course, you seem to use GNU make (is it recent
    >enough?). Can you tell more about the system you're trying
    >to compile glame on?

    Yes I use gnu make 3.79.1, and my system is a linux
    slackware 8.0

     
  • Likai Liu

    Likai Liu - 2002-04-16

    Logged In: YES
    user_id=325449

    There might be a perverse possibility that you not only need
    to run automake && autoconf, but a whole aclocal && automake
    && autoconf. Again, I can only guess because I can't see
    what that offending line in Makefile causes the missing
    separator.

     
  • Pierre

    Pierre - 2002-04-16

    Logged In: YES
    user_id=512388

    >There might be a perverse possibility that you not only need
    >to run automake && autoconf, but a whole aclocal &&
    >automake && autoconf. Again, I can only guess because I
    can't >see what that offending line in Makefile causes the
    missing
    >separator.

    I have tried this, but i got the same error.

     
  • Richard Guenther

    Logged In: YES
    user_id=7575

    I'm closing this for now, as 0.6.3 is out. Please re-open,
    if the bug is still there in 0.6.3.

    Thanks, Richard.

     
  • Richard Guenther

    • status: open --> closed-out-of-date
     
  • Pierre

    Pierre - 2002-06-06
    • status: closed-out-of-date --> open-out-of-date
     
  • Pierre

    Pierre - 2002-06-06

    Logged In: YES
    user_id=512388

    With 0.6.3 I have the same problem I had first, which is
    reported above.

     
  • Pierre

    Pierre - 2003-03-25

    Logged In: YES
    user_id=512388

    Same problem with 0.6.4

     
  • Pierre

    Pierre - 2003-03-25
    • priority: 5 --> 6
     
  • Richard Guenther

    Logged In: YES
    user_id=7575

    If you're at it again, can you try

    http://www.tat.physik.uni-tuebingen.de/~rguenth/glame-0.7.1pre1.tar.gz

    (which now uses autoconf 2.5 and automake 1.6 (or 1.7?))

    Thanks,

    Richard.

     
  • Pierre

    Pierre - 2003-03-26

    Logged In: YES
    user_id=512388

    this is now working ! :)
    no more error with the configure.
    great !
    thank you.

     
1 2 > >> (Page 1 of 2)

Log in to post a comment.