From: Mike M. <mel...@pc...> - 2002-10-30 03:56:20
|
Hi team, I am still having lots of trouble with xine's build system and it is really wearing me out. Representative example: I add a new demuxer. So I create the demuxer and modify src/demuxers/Makefile.am. Then I run 'make' inside src/demuxers. The build system should rebuild the Makefile for just that directory and then build the new module I just added. But that does not happen. Instead, the build system spits out this message: [melanson@x-wing demuxers]$ make cd ../.. && \ /bin/sh /home/melanson/projects/xine/xine-lib/missing --run automake-1.6 --gnu src/demuxers/Makefile Can't locate Automake/Struct.pm in @INC (@INC contains: /usr/share/automake-1.6 /opt/perl-modules/lib/site_perl /usr/lib/perl5/5.6.1/i586-linux /usr/lib/perl5/5.6.1 /usr/lib/perl5/site_perl/5.6.1/i586-linux /usr/lib/perl5/site_perl/5.6.1 /usr/lib/perl5/site_perl .) at /usr/bin/automake-1.6 line 39. BEGIN failed--compilation aborted at /usr/bin/automake-1.6 line 39. WARNING: `automake-1.6' is missing on your system. You should only need it if you modified `Makefile.am', `acinclude.m4' or `configure.ac'. You might want to install the `Automake' and `Perl' packages. Grab them from any GNU archive site. cd ../.. && /bin/sh ./config.status src/demuxers/Makefile depfiles config.status: creating src/demuxers/Makefile config.status: executing depfiles commands and quits. I should note that I got so fed up with the conflicting auto* tool problems that I had awhile ago that I whacked all of the autoconf, automake, aclocal, and libtool directories under /usr/share and /usr/local/share and reinstalled select versions of the tools: automake 1.6.3 autoconf 2.5.4 libtool 1.4.2 In order to solve the problem, I always have to back out to the top level and re-run './cvscompile.sh' and rebuild all the Makefiles. The next build problem is much more obnoxious. It started by poking around in some directory and changing a file. I typed 'make' in that directory. The plugin appeared to rebuild. Then I typed 'make install' and the plugin directory ended up with a brand new file dated /now/. Yet none of the changes that I made were in the code. Yes, I was modifying the right file and I verified this by making deliberate errors in the source and attempting to recompile. But I could even search for new strings added to the source but they would not appear in the compiled plugin. Same solution as above: As long as I run './cvscompile.sh' enough times, the problem goes away. But I want to know why this is happening. Right now, I am not really motivated to do any development because I do not know when I will have to fight with the build system again. Any chance of fixing either A) my system, or B) the xine build system? Thanks... -- -Mike Melanson |
From: Stephen T. <st...@sb...> - 2002-10-30 04:47:18
|
I can understand how frustrating this can be. Work with me. Let us tackle one problem at a time. I will let you pick it. Give me what you did, errors or warnings received. You can trap the entire contents of the result of cvscompile.sh and the config.log from running configure. Give me an example that I can try to reproduce. Stephen On Tue, 2002-10-29 at 21:47, Mike Melanson wrote: > Hi team, > I am still having lots of trouble with xine's build system and it > is really wearing me out. Representative example: I add a new demuxer. So > I create the demuxer and modify src/demuxers/Makefile.am. Then I run > 'make' inside src/demuxers. The build system should rebuild the Makefile > for just that directory and then build the new module I just added. But > that does not happen. Instead, the build system spits out this message: >=20 > [melanson@x-wing demuxers]$ make > cd ../.. && \ > /bin/sh /home/melanson/projects/xine/xine-lib/missing --run automake-1.= 6 > --gnu src/demuxers/Makefile > Can't locate Automake/Struct.pm in @INC (@INC contains: > /usr/share/automake-1.6 /opt/perl-modules/lib/site_perl > /usr/lib/perl5/5.6.1/i586-linux /usr/lib/perl5/5.6.1 > /usr/lib/perl5/site_perl/5.6.1/i586-linux /usr/lib/perl5/site_perl/5.6.1 > /usr/lib/perl5/site_perl .) at /usr/bin/automake-1.6 line 39. > BEGIN failed--compilation aborted at /usr/bin/automake-1.6 line 39. > WARNING: `automake-1.6' is missing on your system. You should only need > it if > you modified `Makefile.am', `acinclude.m4' or `configure.ac'. > You might want to install the `Automake' and `Perl' packages. > Grab them from any GNU archive site. > cd ../.. && /bin/sh ./config.status src/demuxers/Makefile depfiles > config.status: creating src/demuxers/Makefile > config.status: executing depfiles commands >=20 > and quits. I should note that I got so fed up with the conflicting auto* > tool problems that I had awhile ago that I whacked all of the autoconf, > automake, aclocal, and libtool directories under /usr/share and > /usr/local/share and reinstalled select versions of the tools: >=20 > automake 1.6.3 > autoconf 2.5.4 > libtool 1.4.2 >=20 > In order to solve the problem, I always have to back out to the top level > and re-run './cvscompile.sh' and rebuild all the Makefiles. >=20 > The next build problem is much more obnoxious. It started by > poking around in some directory and changing a file. I typed 'make' in > that directory. The plugin appeared to rebuild. Then I typed 'make > install' and the plugin directory ended up with a brand new file dated > /now/. Yet none of the changes that I made were in the code. Yes, I was > modifying the right file and I verified this by making deliberate errors > in the source and attempting to recompile. But I could even search for ne= w > strings added to the source but they would not appear in the compiled > plugin. >=20 > Same solution as above: As long as I run './cvscompile.sh' enough > times, the problem goes away. But I want to know why this is happening. > Right now, I am not really motivated to do any development because I do > not know when I will have to fight with the build system again. >=20 > Any chance of fixing either A) my system, or B) the xine build > system? Thanks... > -- > -Mike Melanson >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > xine-devel mailing list > xin...@li... > https://lists.sourceforge.net/lists/listinfo/xine-devel |
From: Mike M. <mel...@pc...> - 2002-10-31 02:08:42
|
On 29 Oct 2002, Stephen Torri wrote: > I can understand how frustrating this can be. Work with me. Let us > tackle one problem at a time. I will let you pick it. Give me what you > did, errors or warnings received. You can trap the entire contents of > the result of cvscompile.sh and the config.log from running configure. > > Give me an example that I can try to reproduce. Okay, here is what I just did: I took a break from everything xine for 24 hours and then looked at the problem again. My first step was to start over and get rid of anything on my system remotely related to autoconf, automake, aclocal, and libtool. All binaries, scripts, and share directories. Then I reinstalled ac2.54, am1.6.3, and lt1.4.2. One last thing I did was create a symbolic link from /usr/share/autoconf -> /usr/local/share/autoconf. This is because I discovered that running the autom4te program threw an error about not finding something in a path that included the first directory. Anyway, the upshot is that I can 'touch' a Makefile.am and trust that it will rebuild the Makefile. So I am happy about that. The other bug is much more subtle. I am going back to work on the WMA support in libffmpeg to see what happens from here. Thanks... -- -Mike Melanson |
From: Stephen T. <st...@sb...> - 2002-10-31 02:25:18
|
On Wed, 2002-10-30 at 20:06, Mike Melanson wrote: > Okay, here is what I just did: I took a break from everything xine > for 24 hours and then looked at the problem again. A good suggestion. =20 > My first step was to start over and get rid of anything on my > system remotely related to autoconf, automake, aclocal, and libtool. All > binaries, scripts, and share directories. Then I reinstalled ac2.54, > am1.6.3, and lt1.4.2. One last thing I did was create a symbolic link fro= m > /usr/share/autoconf -> /usr/local/share/autoconf. This is because I > discovered that running the autom4te program threw an error about not > finding something in a path that included the first directory. >=20 > Anyway, the upshot is that I can 'touch' a Makefile.am and trust > that it will rebuild the Makefile. So I am happy about that. The other bu= g > is much more subtle. I am going back to work on the WMA support in > libffmpeg to see what happens from here. What distribution and version are you using? Stephen |
From: Mike M. <mel...@pc...> - 2002-10-31 02:42:43
|
On 30 Oct 2002, Stephen Torri wrote: > What distribution and version are you using? Linux From Scratch v3.3. This version recommends installing ac2.53, am1.6, and lt1.4.2. But with all these build system variations, I have had to upgrade/downgrade the versions and thus conflicts are created. Also, how many more times will the installation process change? Everytime it does, it breaks my 30+ custom installation scripts. And that really unnerves me. Thanks... -- -Mike Melanson |
From: Stephen T. <st...@sb...> - 2002-10-31 02:49:12
|
On Wed, 2002-10-30 at 20:40, Mike Melanson wrote: > On 30 Oct 2002, Stephen Torri wrote: >=20 > > What distribution and version are you using? >=20 > Linux From Scratch v3.3. This version recommends installing > ac2.53, am1.6, and lt1.4.2. But with all these build system variations, I > have had to upgrade/downgrade the versions and thus conflicts are created= . Ok. This is good to know. > Also, how many more times will the installation process change? > Everytime it does, it breaks my 30+ custom installation scripts. And that > really unnerves me. As far as I know we will stay with these versions for a while. I just want to move us to 2.53 on autoconf because 2.13 was no longer supported. Stephen |