Menu
▾
▴
libvisual-devel
|
From: Duilio J. P. <dp...@fc...> - 2004-06-19 23:47:28
|
El s=C3=A1b, 19 de 06 de 2004 a las 17:14, Dennis Smit escribi=C3=B3: > Heya! >=20 > I'm still having problems with auto*, I installed automake-1.8 and when > running ./autogen.sh it gives: >=20 > :/usr/src/libvis-duilo/libvisual-xmms-0.1.5# ./autogen.sh > autoreconf: Entering directory `.' > autoreconf: configure.ac: not using Gettext > autoreconf: running: aclocal --output=3Daclocal.m4t > autoreconf: `aclocal.m4' is unchanged > autoreconf: configure.ac: tracing > configure.ac:52: warning: AC_ARG_PROGRAM was called before > AC_CANONICAL_TARGET > autoconf/general.m4:1657: AC_CANONICAL_TARGET is expanded from... > configure.ac:52: AC_CANONICAL_TARGET is required by... > aclocal.m4:7426: AM_PATH_SDL is expanded from... > configure.ac:52: the top level > autoreconf: running: libtoolize --force > autoreconf: running: /opt/gtk2/bin/autoconf --force > configure.ac:52: warning: AC_ARG_PROGRAM was called before > AC_CANONICAL_TARGET > autoconf/general.m4:1657: AC_CANONICAL_TARGET is expanded from... > configure.ac:52: AC_CANONICAL_TARGET is required by... > aclocal.m4:7426: AM_PATH_SDL is expanded from... > configure.ac:52: the top level > autoreconf: running: /opt/gtk2/bin/autoheader --force > configure.ac:52: warning: AC_ARG_PROGRAM was called before > AC_CANONICAL_TARGET > autoconf/general.m4:1657: AC_CANONICAL_TARGET is expanded from... > configure.ac:52: AC_CANONICAL_TARGET is required by... > aclocal.m4:7426: AM_PATH_SDL is expanded from... > configure.ac:52: the top level > autoreconf: running: automake --add-missing --force-missing > configure.ac:52: warning: AC_ARG_PROGRAM was called before > AC_CANONICAL_TARGET > autoconf/general.m4:1657: AC_CANONICAL_TARGET is expanded from... > configure.ac:52: AC_CANONICAL_TARGET is required by... > aclocal.m4:7426: AM_PATH_SDL is expanded from... > configure.ac:52: the top level > configure.ac:5: version mismatch. This is Automake 1.8.5, > configure.ac:5: but the definition used by this AM_INIT_AUTOMAKE > configure.ac:5: comes from Automake 1.4-p6. You should recreate > configure.ac:5: aclocal.m4 with aclocal and run automake again. > /usr/share/automake-1.8/am/depend2.am: am__fastdepCC does not appear in > AM_CONDITIONAL > /usr/share/automake-1.8/am/depend2.am: AMDEP does not appear in > AM_CONDITIONAL > autoreconf: automake failed with exit status: 63 >=20 >=20 > I really appreciate your help btw!! thanks a lot >=20 > Cheers, > Dennis >=20 Don't worry about the warnings in regard of AC_CANONICAL_TARGET and AC_ARG_PROGRAM, this is because AM_PATH_SDL macro is very old. We cannot (must not) change it, only Lantinga. The error is because, like you see, aclocal.m4 is unchanged. These M4 macros must be recreated by automake 1.8. Just remove aclocal.m4, and run again autogen.sh. If the script don't=20 rebuild the file, run aclocal first. The aclocal.m4 file must not be submitted to the CVS repository. Duilio. |
|
From: Dennis S. <sy...@yo...> - 2004-06-20 00:54:58
|
On Sat, 2004-06-19 at 20:50 -0300, Duilio Javier Protti wrote: Ok great, This works like a charm, is it better to use symlinks for programs like depcomp, install-sh etc etc ? It would be superB if you could also port both libvisual-plugins to automake-1.8, when that is there i'll fix that what i've screwed up (doh doh doh) and then check the right files into CVS (and ofcourse exclude that what is auto generated) I will also move the current ChangeLog to NEWS and then we can use the ChangeLog as a real per commit base ChangeLog. When that is done, I'll do a new release and we can start hacking on new exciting stuff! Thanks a lot, Dennis > Don't worry about the warnings in regard of AC_CANONICAL_TARGET > and AC_ARG_PROGRAM, this is because AM_PATH_SDL macro is very > old. We cannot (must not) change it, only Lantinga. > > The error is because, like you see, aclocal.m4 is unchanged. > These M4 macros must be recreated by automake 1.8. Just remove > aclocal.m4, and run again autogen.sh. If the script don't > rebuild the file, run aclocal first. > > The aclocal.m4 file must not be submitted to the CVS repository. > > > Duilio. |
|
From: Duilio J. P. <dp...@fc...> - 2004-06-20 02:17:24
|
> Ok great, This works like a charm, is it better to use symlinks > for programs like depcomp, install-sh etc etc ? symlinks are better to save some disk space, and to point to the last version. > It would be superB if you could also port both libvisual-plugins > to automake-1.8, I have been working on that. However, due to the broken distro (all the headers are missing), I cannot full-test the building process. I will send you the updated package and you must copy the headers and test it. > I will also move the current ChangeLog to NEWS and then we can use > the ChangeLog as a real per commit base ChangeLog. mhmm... I think the current ChangeLog is right for CVS, and NEWS file must kept info on a per-release basis. Duilio. |
|
From: Dennis S. <sy...@yo...> - 2004-06-20 10:21:43
|
On Sat, 2004-06-19 at 23:20 -0300, Duilio Javier Protti wrote: > > Ok great, This works like a charm, is it better to use symlinks > > for programs like depcomp, install-sh etc etc ? > > symlinks are better to save some disk space, and to point to the > last version. Isn't it safer to not use symlinks for the final package ? > > It would be superB if you could also port both libvisual-plugins > > to automake-1.8, > > I have been working on that. However, due to the broken distro > (all the headers are missing), I cannot full-test the building > process. I will send you the updated package and you must > copy the headers and test it. To include the headers next time in dist I should add them to the sources right ? > > I will also move the current ChangeLog to NEWS and then we can use > > the ChangeLog as a real per commit base ChangeLog. > > mhmm... I think the current ChangeLog is right for CVS, > and NEWS file must kept info on a per-release basis. Yep. I'll try to get libvisual into sf.net cvs today and when everything is fixed dist wise, we'll be doing a new release to fix my previous major screw up... Do you agree with this ? Cheers, Dennis |
|
From: Duilio J. P. <dp...@fc...> - 2004-06-20 14:01:04
|
> Isn't it safer to not use symlinks for the final package ? The 'dist' target will not copy the symlinks, but the files which are pointed by the symlinks > To include the headers next time in dist I should add them to the > sources right ? Yes. That will cause also that when you modify some header, 'make' will detect that and will rebuild targets that depend on that header. Duilio. |
|
From: Dennis S. <sy...@yo...> - 2004-06-20 14:10:40
|
On Sun, 2004-06-20 at 11:03 -0300, Duilio Javier Protti wrote: > > Isn't it safer to not use symlinks for the final package ? > The 'dist' target will not copy the symlinks, but the > files which are pointed by the symlinks > > > To include the headers next time in dist I should add them to the > > sources right ? > Yes. That will cause also that when you modify some header, > 'make' will detect that and will rebuild targets that depend > on that header. Oooh was this supported by automake 1.4 as well ? sounds good and I will be fixing that, however I've mailed you a few issues, could you take a look at it ? |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X