LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (http://www.linuxquestions.org/questions/linux-software-2/)
-   -   SlackBuild Problem: "configure.in" (http://www.linuxquestions.org/questions/linux-software-2/slackbuild-problem-configure-in-644562/)

gregkedro 05-24-2008 07:18 PM

SlackBuild Problem: "configure.in"
 
Hey, everybody. I'm trying to resolve some dependencies to get ffmeg installed on my Slack 12 system. I have all the SlackBuild scripts for all the files I need, but when I started to run them (I started with faac), I get an error I've not seen before. I've poked around, but I'm really stumped on how to get it fixed.

When I run ./faac.SlackBuild I end up with these lines (note the error in the configure.in file):

Code:

configure.in:11: warning: underquoted definition of MY_DEFINE
configure.in:11:  run info '(automake)Extending aclocal'
configure.in:11:  or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
configure.in:17: warning: macro `AM_PROG_LIBTOOL' not found in library
configure.in:4: installing `./install-sh'
configure.in:4: installing `./missing'
common/mp4v2/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined
common/mp4v2/Makefile.am:5:  The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
common/mp4v2/Makefile.am:5:  to `configure.in' and run `aclocal' and `autoconf' again.
common/mp4v2/Makefile.am:5:  If `AC_PROG_LIBTOOL' is in `configure.in', make sure
common/mp4v2/Makefile.am:5:  its definition is in aclocal's search path.
common/mp4v2/Makefile.am: installing `./depcomp'
libfaac/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined
libfaac/Makefile.am:1:  The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
libfaac/Makefile.am:1:  to `configure.in' and run `aclocal' and `autoconf' again.
libfaac/Makefile.am:1:  If `AC_PROG_LIBTOOL' is in `configure.in', make sure
libfaac/Makefile.am:1:  its definition is in aclocal's search path.
configure.in:17: error: possibly undefined macro: AM_PROG_LIBTOOL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.

I did a slocate for configure.in, because it looked to me like a file called by automake or something like that (I'm no nerd, sorry...). There are a lot of configure.in files in various places on my system.

This looks like a real simple fix (adding AC_PROG_LIBTOOL to configure.in), but I have no idea where to go to fix it. Could someone lend a hand?

Thanks.

Greg

Bruce Hill 05-25-2008 02:02 AM

Save yourself some hassle and get ffmpeg from Alien Bob's repository.

gregkedro 05-25-2008 07:51 AM

Quote:

Originally Posted by Bruce Hill (Post 3163922)
Save yourself some hassle and get ffmpeg from Alien Bob's repository.

Okay... but, will that resolve all the dependecies of ffmpeg?
1. lame (this I have already installed)
2. faac
3. faad2
4. xvidcore
5. a52dec
6. x264

That's what I'm concerned about. I haven't gotten close to actually installing (or trying to install) ffmpeg because of my "laundry list" of dependencies I need to solve first, but can't because of this "configure.in" problem. And it's not just with faac, I get the error on faad2, also. Haven't tried the others.

Greg

Bruce Hill 05-25-2008 07:55 AM

Did you look at his SlackBuild script?
Code:

# Support libraries:
A52=0.7.4
AMRNB=7.0.0.0
AMRWB=7.0.0.2
DC1394=1.2.2
DIRAC=0.9.1
FAAC=1.26
FAAD2=2.6.1
FFMPEG=r12291
GSM=1.0.12
LAME=3.97
RAW1394=1.3.0
X264=20080302-2245
XVID=1.1.3

From your question I assume not ...

gregkedro 05-25-2008 08:07 AM

Quote:

Originally Posted by Bruce Hill (Post 3164062)
Did you look at his SlackBuild script?

No I did not. Howevery, even if I had... I'd still need some help. That seems like the "laundry list" of dependencies I'm trying to resolve. Is it? Or is it a list of dependencies that Bob has already built into his package?

Sorry, like I said, though I've used Slack since 9.1, I'm no nerd and sometimes I just plain get lost in the details. Thanks for taking the time to help me out, though. It's greatly appreciated.

Greg

Bruce Hill 05-25-2008 08:14 AM

Those are included in his SlackBuild. Take a look at his script and
you'll see how nicely he packages it. I haven't found anyone who does
as good a job with SlackBuild scripts as Eric. Just install his ffmpeg
Slack package and you'll have all those dependencies in your system.

gregkedro 05-25-2008 08:26 AM

Great! Thanks, Bruce!

~Greg

Bruce Hill 05-25-2008 08:32 AM

You might want to get more packages from Eric's repository.
Also check out the "restricted packages" link.

Hope you get everything you need installed and solved.

gregkedro 05-26-2008 07:37 AM

I had to work most of the day yesterday, so I haven't gotten back to this until now. I ran the script, it downloaded all dependencies, etc. etc. After running the ffmpeg.SlackBuild script, I get much the same error as before:

Code:

**  faac ...
**
configure.in:11: warning: underquoted definition of MY_DEFINE
configure.in:11:  run info '(automake)Extending aclocal'
configure.in:11:  or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
configure.in:17: warning: macro `AM_PROG_LIBTOOL' not found in library
configure.in:4: installing `./install-sh'
configure.in:4: installing `./missing'
common/mp4v2/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined
common/mp4v2/Makefile.am:5:  The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
common/mp4v2/Makefile.am:5:  to `configure.in' and run `aclocal' and `autoconf' again.
common/mp4v2/Makefile.am:5:  If `AC_PROG_LIBTOOL' is in `configure.in', make sure
common/mp4v2/Makefile.am:5:  its definition is in aclocal's search path.
common/mp4v2/Makefile.am: installing `./depcomp'
libfaac/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined
libfaac/Makefile.am:1:  The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
libfaac/Makefile.am:1:  to `configure.in' and run `aclocal' and `autoconf' again.
libfaac/Makefile.am:1:  If `AC_PROG_LIBTOOL' is in `configure.in', make sure
libfaac/Makefile.am:1:  its definition is in aclocal's search path.
configure.in:17: error: possibly undefined macro: AM_PROG_LIBTOOL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.

I have a standard Slack 12.0 install. I don't know why my autoconf would be hosed. ??

~Greg

Bruce Hill 05-26-2008 08:29 AM

Three issues here ...

1 - not a programmer
2 - don't even know bash well
3 - mentally exhausted.

However, may I ask? Did you try just installing the ffmpeg package that Eric has in his repository?

P.S. There is also his restricted SlackBuilds. This is the ffmpeg I install...

gregkedro 05-26-2008 09:04 AM

Hey, Bruce. No, I didn't just try to install the package Eric had on the site. It did cross my mind, but when something breaks or doesn't work like it should, I get mildly anal about fixing it and making it work right.

I just ran Eric's SlackBuild script on another machine that has a very similar Slack 12.0 install, and it ran flawlessly. So, it made me think I've hosed something on this (my work) machine. I've removed and re-installed the following packages, but it still isn't solving my configure.in problem:

1. autoconf-2.61-noarch-1.tgz
2. automake-1.9.6-noarch-1.tgz
3. libtool-1.5.24-i486-1.tgz
4. m4-1.4.9-i486-1.tgz
5. make-3.81-i486-1.tgz

Frankly, I think it's automake that's causing the problem, and I thought reinstalling the package would take care of things, but it didn't. So, I'll keep poking around for it... I'd hate to have to upgrade to Slack 12.1 just to fix this, but it may be the excuse I need to get Slack 12.1 running.

Thanks for the help. Don't worry about knocking your brains out over this. Maybe someone else will pick up on the thread and pitch in some thoughts on how to make this work.

Greg

gregkedro 05-26-2008 09:30 AM

Oh, yeah... Let's all join together and say, "Stupid!" ... I think I found the problem. I had a file in my /tmp folder called automake-1.10.1.tar.bz2 and a directory by the name of automake-1.10.1. Apparently at some time in the past (I have no idea WHY I would have done this) I tried to "upgrade" my automake from the Slack 12 automake-1.9.6-noarch-1.tgz to this one, but I didn't use the Slack package to do it (again: I have no idea why). I dide a "make uninstall" in the automake.10 subdir and it cleaned out some junk from I don't know where. I ran Eric's SlackBuild script again, and it has apparently worked.

I tried to watch for automake errors while the script was running, but... I have no idea.

This kinda leaves me with one question for anyone who knows about this stuff: Should I re-install my automake-1.9 package?

I don't know if any aclocal stuff was hosed with my foobar of trying to install automake-1.10. If so, would a re-install of 1.9 fix things? Should I delete the /usr/share/aclocal directory and then re-install automake-1.9 to get a "clean" aclocal?

I'm kinda grasping at straws here to figure out how to clean this mess up. Or... maybe it's already cleaned up by just doing the make uninstall of the automake-1.10.

Man... what a bonehead. And I know (!) better than to do something like that...

Greg


All times are GMT -5. The time now is 02:51 PM.