Menu
▾
▴
qstat-devx
|
From: Steven H. <ki...@mu...> - 2004-11-23 01:21:59
|
Ok call me stupid how's the current CVS version meant to compile?
Wild stab in the dark there some files not been committed somewhere
along the lines ( configure ) ?
Steve / K
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to pos...@mu....
|
|
From: Ludwig N. <l-...@us...> - 2004-11-23 14:19:21
|
Steven Hartland wrote: > Ok call me stupid how's the current CVS version meant to compile? > Wild stab in the dark there some files not been committed somewhere > along the lines ( configure ) ? run ./autogen.sh first cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ PGP Key: FF8135CE |
|
From: Steven H. <ki...@mu...> - 2004-11-23 14:52:51
|
./autogen.sh
+ autoreconf -i
autoreconf: not found
Seems like your relying on something that's pretty none standard.
Steve / K
----- Original Message -----
From: "Ludwig Nussel" <l-...@us...>
>
> run ./autogen.sh first
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to pos...@mu....
|
|
From: Ludwig N. <l-...@us...> - 2004-11-23 16:41:29
|
Steven Hartland wrote: > ./autogen.sh > + autoreconf -i > autoreconf: not found > > Seems like your relying on something that's pretty none standard. autoreconf is part of autoconf. Maybe you have an older version. I've changed autogen.sh to call the tools individually if autoreconf is not available. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ PGP Key: FF8135CE |
|
From: Steven H. <ki...@mu...> - 2004-11-23 17:24:39
|
Nope autoconf doesnt seem to be a standard tool so I'd say we best
avoid it:
steven@besson [steven] autoconf
bash: autoconf: command not found
root@dev1:installs> autoconf
autoconf: Command not found.
root@yoda:qstat2> ./autogen.sh
+ which autoreconf
+ aclocal
aclocal: not found
+ autoconf
autoconf: not found
+ autoheader
autoheader: not found
+ automake
Steve / K
----- Original Message -----
From: "Ludwig Nussel" <l-...@us...>
> Steven Hartland wrote:
>> ./autogen.sh
>> + autoreconf -i
>> autoreconf: not found
>>
>> Seems like your relying on something that's pretty none standard.
>
> autoreconf is part of autoconf. Maybe you have an older version.
> I've changed autogen.sh to call the tools individually if autoreconf
> is not available.
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to pos...@mu....
|
|
From: Ludwig N. <l-...@us...> - 2004-11-23 18:05:42
|
Steven Hartland wrote: > Nope autoconf doesnt seem to be a standard tool so I'd say we best > avoid it: > > steven@besson [steven] autoconf > bash: autoconf: command not found > > root@dev1:installs> autoconf > autoconf: Command not found. > > root@yoda:qstat2> ./autogen.sh > + which autoreconf > + aclocal > aclocal: not found > + autoconf > autoconf: not found > + autoheader > autoheader: not found > + automake automake/autoconf are standard GNU development tools and they are probably just as annoying as useful sometimes. The reasons I want it for are at least, make dist, make distcheck, the standard install target and the automatic dependency rules it generates. When I asked last month the only concern was that it may not work on Windows, therefore I added a simple Makefile.w32 for that. Note that you do not need automake or autoconf if you compile the released version. Only the CVS doesn't contain configure etc since those files are automatically generated. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ PGP Key: FF8135CE |
|
From: Steven H. <ki...@mu...> - 2004-11-23 18:37:13
|
Hmm not had to download said tools for building anything else and I
build almost all things from source which makes me question how
standard it is?
Not sure how helpful it is not being able to compile from CVS
without installing additional tools especially as there is no mention
of it in the docs
Also just installed autoconf and it still fails:
./autogen.sh
+ which autoreconf
+ autoreconf -i
Can't exec "aclocal": No such file or directory at /usr/local/share/autoconf/Autom4te/General.pm line 459.
autoreconf: aclocal failed with exit status: 16777215
pkg_info |grep autoc
autoconf-2.53_1 Automatically configure source code on many Un*x platforms
Seems like a bit to much pain to ask people to go through just to compile
the CVS version when a 10 line Makefile did the job nicely.
Steve / K
----- Original Message -----
From: "Ludwig Nussel" <l-...@us...>
>
> automake/autoconf are standard GNU development tools and they are
> probably just as annoying as useful sometimes. The reasons I want it
> for are at least, make dist, make distcheck, the standard install
> target and the automatic dependency rules it generates. When I asked
> last month the only concern was that it may not work on Windows,
> therefore I added a simple Makefile.w32 for that. Note that you do
> not need automake or autoconf if you compile the released version.
> Only the CVS doesn't contain configure etc since those files are
> automatically generated.
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to pos...@mu....
|
|
From: Steven H. <ki...@mu...> - 2004-11-23 19:05:42
|
Also installing automake still gives errors:
root@yoda:qstat2> ./autogen.sh
+ which autoreconf
+ autoreconf -i
autoreconf: `aclocal.m4' is updated
exec: autom4te --language=autoconf --output=-: not found
configure.ac: 3: `automake requires `AM_CONFIG_HEADER', not `AC_CONFIG_HEADER'
automake: configure.ac: `AM_INIT_AUTOMAKE' must be used
automake: configure.ac: installing `./install-sh'
automake: configure.ac: installing `./mkinstalldirs'
automake: configure.ac: installing `./missing'
automake: Makefile.am: installing `./INSTALL'
automake: Makefile.am: required file `./NEWS' not found
automake: Makefile.am: required file `./README' not found
automake: Makefile.am: installing `./COPYING'
automake: Makefile.am: required file `./AUTHORS' not found
configure.ac: 3: required file `./gnuconfig.h.in' not found
automake: configure.ac: installing `./depcomp'
autoreconf: automake failed with exit status: 1
at /usr/local/bin/autoreconf line 368
pkg_info |grep auto
autoconf-2.53_1 Automatically configure source code on many Un*x platforms
automake-1.5,1 GNU Standards-compliant Makefile generator
This is not convincing me this is a worth while exercise :(
Steve / K
----- Original Message -----
From: "Steven Hartland" <ki...@mu...>
To: "Ludwig Nussel" <l-...@us...>; <qst...@li...>
Sent: Tuesday, November 23, 2004 6:36 PM
Subject: Re: [QStat-devx] Current CVS how to build?
> Hmm not had to download said tools for building anything else and I
> build almost all things from source which makes me question how
> standard it is?
> Not sure how helpful it is not being able to compile from CVS
> without installing additional tools especially as there is no mention
> of it in the docs
>
> Also just installed autoconf and it still fails:
> ./autogen.sh
> + which autoreconf
> + autoreconf -i
> Can't exec "aclocal": No such file or directory at /usr/local/share/autoconf/Autom4te/General.pm line 459.
> autoreconf: aclocal failed with exit status: 16777215
>
> pkg_info |grep autoc
> autoconf-2.53_1 Automatically configure source code on many Un*x platforms
>
> Seems like a bit to much pain to ask people to go through just to compile
> the CVS version when a 10 line Makefile did the job nicely.
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to pos...@mu....
|
|
From: Ludwig N. <l-...@us...> - 2004-11-23 19:42:59
|
Steven Hartland wrote: > Also installing automake still gives errors: > > root@yoda:qstat2> ./autogen.sh > + which autoreconf > + autoreconf -i > autoreconf: `aclocal.m4' is updated > exec: autom4te --language=autoconf --output=-: not found > configure.ac: 3: `automake requires `AM_CONFIG_HEADER', not > `AC_CONFIG_HEADER' > automake: configure.ac: `AM_INIT_AUTOMAKE' must be used > automake: configure.ac: installing `./install-sh' > automake: configure.ac: installing `./mkinstalldirs' > automake: configure.ac: installing `./missing' > automake: Makefile.am: installing `./INSTALL' > automake: Makefile.am: required file `./NEWS' not found > automake: Makefile.am: required file `./README' not found > automake: Makefile.am: installing `./COPYING' > automake: Makefile.am: required file `./AUTHORS' not found > configure.ac: 3: required file `./gnuconfig.h.in' not found > automake: configure.ac: installing `./depcomp' > autoreconf: automake failed with exit status: 1 > at /usr/local/bin/autoreconf line 368 > > pkg_info |grep auto > autoconf-2.53_1 Automatically configure source code on many Un*x > platforms > automake-1.5,1 GNU Standards-compliant Makefile generator > > This is not convincing me this is a worth while exercise :( That's the annoying side of automake. I don't have a system with such an old version so I can't check compatability myself. I've changed AC_CONFIG_HEADER into AM_CONFIG_HEADER, please try again. If automake still complains about required files not found, remove the autoreconf call and add --foreign to automake. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ PGP Key: FF8135CE |
|
From: Steven H. <ki...@mu...> - 2004-11-23 20:03:53
|
Still no joy:
./autogen.sh
+ which autoreconf
+ autoreconf -i
autoreconf: `aclocal.m4' is updated
exec: autom4te --language=autoconf --output=-: not found
automake: configure.ac: `AM_INIT_AUTOMAKE' must be used
automake: Makefile.am: required file `./NEWS' not found
automake: Makefile.am: required file `./README' not found
automake: Makefile.am: required file `./AUTHORS' not found
configure.ac: 3: required file `./gnuconfig.h.in' not found
autoreconf: automake failed with exit status: 1
at /usr/local/bin/autoreconf line 368
Steve / K
----- Original Message -----
From: "Ludwig Nussel" <l-...@us...>
> That's the annoying side of automake. I don't have a system with
> such an old version so I can't check compatability myself. I've
> changed AC_CONFIG_HEADER into AM_CONFIG_HEADER, please try again. If
> automake still complains about required files not found, remove the
> autoreconf call and add --foreign to automake.
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to pos...@mu....
|
|
From: Ludwig N. <lud...@we...> - 2004-11-23 20:24:06
|
Steven Hartland wrote: > Still no joy: > ./autogen.sh > + which autoreconf > + autoreconf -i > autoreconf: `aclocal.m4' is updated > exec: autom4te --language=autoconf --output=-: not found > automake: configure.ac: `AM_INIT_AUTOMAKE' must be used > automake: Makefile.am: required file `./NEWS' not found > automake: Makefile.am: required file `./README' not found > automake: Makefile.am: required file `./AUTHORS' not found > configure.ac: 3: required file `./gnuconfig.h.in' not found > autoreconf: automake failed with exit status: 1 > at /usr/local/bin/autoreconf line 368 gnuconfig.h.in is supposed to be created automatically. Maybe it got confused by previous errors. Try autoreconf -f -i or start with a fresh checkout. cu Ludwig -- (o_ Lud...@we... //\ V_/_ PGP Key ID: FF8135CE |
|
From: Ludwig N. <l-...@us...> - 2004-11-23 19:10:56
|
Steven Hartland wrote: > Hmm not had to download said tools for building anything else and I > build almost all things from source which makes me question how > standard it is? If you ever had to enter ./configure before make you have used it's service. You do not need to autoconf/automake installed as long as you don't modify Makefile.am&friends. > Not sure how helpful it is not being able to compile from CVS > without installing additional tools especially as there is no mention > of it in the docs Well, that's easy to fix. > Also just installed autoconf and it still fails: > ./autogen.sh > + which autoreconf > + autoreconf -i > Can't exec "aclocal": No such file or directory at > /usr/local/share/autoconf/Autom4te/General.pm line 459. > autoreconf: aclocal failed with exit status: 16777215 > > pkg_info |grep autoc > autoconf-2.53_1 Automatically configure source code on many Un*x platforms You also need automake. > Seems like a bit to much pain to ask people to go through just to compile > the CVS version when a 10 line Makefile did the job nicely. It lacked the useful features I mentioned. Ideally people don't compile from CVS. We need to do releases more frequently instead. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ PGP Key: FF8135CE |
|
From: Steve J. <ste...@ya...> - 2004-11-24 01:13:39
|
Yeah, I thought the 10 line makefile was just fine. But the autoconf benefits you list are some what compelling. They aren't enough for me, given the head aches you've encountered; I've got zero patience for unreliable tools. I suggest restoring the simple works-on-most-unixes makefile. The fewer barriers to entry, the more successful QStat will be. Autoconf will be nice for the qstat developers (assuming all the developers can get it working), but we shouldn't expose it to users. Steve --- Ludwig Nussel <l-...@us...> wrote: > Steven Hartland wrote: > > Nope autoconf doesnt seem to be a standard tool so I'd say we best > > avoid it: > > > > steven@besson [steven] autoconf > > bash: autoconf: command not found > > > > root@dev1:installs> autoconf > > autoconf: Command not found. > > > > root@yoda:qstat2> ./autogen.sh > > + which autoreconf > > + aclocal > > aclocal: not found > > + autoconf > > autoconf: not found > > + autoheader > > autoheader: not found > > + automake > > automake/autoconf are standard GNU development tools and they are > probably just as annoying as useful sometimes. The reasons I want it > for are at least, make dist, make distcheck, the standard install > target and the automatic dependency rules it generates. When I asked > last month the only concern was that it may not work on Windows, > therefore I added a simple Makefile.w32 for that. Note that you do > not need automake or autoconf if you compile the released version. > Only the CVS doesn't contain configure etc since those files are > automatically generated. > > cu > Ludwig > > -- > (o_ Ludwig Nussel > //\ > V_/_ PGP Key: FF8135CE > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > QStat-devx mailing list > QSt...@li... > https://lists.sourceforge.net/lists/listinfo/qstat-devx > |
|
From: Ludwig N. <l-...@us...> - 2004-11-24 02:07:42
|
[there is a massive delay of several hours from this list whereas the mails directly addressed to me arrived instantly] Steve Jankowski wrote: > Yeah, I thought the 10 line makefile was just fine. But the autoconf benefits > you list are some what compelling. They aren't enough for me, given the head > aches you've encountered; I've got zero patience for unreliable tools. > > I suggest restoring the simple works-on-most-unixes makefile. The fewer > barriers to entry, the more successful QStat will be. Autoconf will be nice > for the qstat developers (assuming all the developers can get it working), but > we shouldn't expose it to users. Users of release tarballs don't see it. They just run the usual ./configure && make install. The problems with older automake are hopefully fixed now. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ PGP Key: FF8135CE |
|
From: Steve J. <ste...@ya...> - 2004-11-24 07:50:12
|
--- Ludwig Nussel <l-...@us...> wrote: > [there is a massive delay of several hours from this list whereas > the mails directly addressed to me arrived instantly] > > Steve Jankowski wrote: > > Yeah, I thought the 10 line makefile was just fine. But the autoconf > benefits > > you list are some what compelling. They aren't enough for me, given the > head > > aches you've encountered; I've got zero patience for unreliable tools. > > > > I suggest restoring the simple works-on-most-unixes makefile. The fewer > > barriers to entry, the more successful QStat will be. Autoconf will be > nice > > for the qstat developers (assuming all the developers can get it working), > but > > we shouldn't expose it to users. > > Users of release tarballs don't see it. They just run the usual > ./configure && make install. The problems with older automake are > hopefully fixed now. > > cu > Ludwig > But we're not doing releases. And we're not doing beta releases. So use of the current CVS is now serving as a beta test. But we can't get any beta feedback if people can't compile it. Steve |
|
From: Ludwig N. <l-...@us...> - 2004-11-24 12:05:45
|
Steve Jankowski wrote: > > --- Ludwig Nussel <l-...@us...> wrote: > > > [there is a massive delay of several hours from this list whereas > > the mails directly addressed to me arrived instantly] > > > > Steve Jankowski wrote: > > > Yeah, I thought the 10 line makefile was just fine. But the autoconf > > benefits > > > you list are some what compelling. They aren't enough for me, given the > > head > > > aches you've encountered; I've got zero patience for unreliable tools. > > > > > > I suggest restoring the simple works-on-most-unixes makefile. The fewer > > > barriers to entry, the more successful QStat will be. Autoconf will be > > nice > > > for the qstat developers (assuming all the developers can get it working), > > but > > > we shouldn't expose it to users. > > > > Users of release tarballs don't see it. They just run the usual > > ./configure && make install. The problems with older automake are > > hopefully fixed now. > > But we're not doing releases. And we're not doing beta releases. So use of > the current CVS is now serving as a beta test. But we can't get any beta > feedback if people can't compile it. Why not? 2.6 is from August, time for a 2.7 release. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ PGP Key: FF8135CE |
|
From: Steven H. <ki...@mu...> - 2004-11-24 12:45:56
|
----- Original Message -----
From: "Ludwig Nussel" <l-...@us...>
>> But we're not doing releases. And we're not doing beta releases. So use of
>> the current CVS is now serving as a beta test. But we can't get any beta
>> feedback if people can't compile it.
>
> Why not? 2.6 is from August, time for a 2.7 release.
I think what Steve's trying to say is that unless we do interim releases for
each patch applied then we are going to lack important feedback from
people who would usually compile from CVS quite easily. Given it took me
the best part of a day with your help to get it compiling it doesn't bode well.
I suggest what we do is reinstate the old Makefile into the CVS tree but when
we do a release it gets excluded and your new configure based system shipped.
This will then have all benefits that you stated with none of the pitfalls. The
only slight downside is that the old Makefile will need to be maintained but
given its simplicity that shouldn't be a problem.
Steve / K
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to pos...@mu....
|
|
From: Ludwig N. <l-...@us...> - 2004-11-24 17:09:45
|
Steven Hartland wrote: > ----- Original Message ----- > From: "Ludwig Nussel" <l-...@us...> > >>But we're not doing releases. And we're not doing beta releases. So use > >>of > >>the current CVS is now serving as a beta test. But we can't get any beta > >>feedback if people can't compile it. > > > >Why not? 2.6 is from August, time for a 2.7 release. > > I think what Steve's trying to say is that unless we do interim releases for > each patch applied then we are going to lack important feedback from > people who would usually compile from CVS quite easily. Given it took me > the best part of a day with your help to get it compiling it doesn't bode > well. That was an initial hurdle, it's fixed now. > I suggest what we do is reinstate the old Makefile into the CVS > tree but when we do a release it gets excluded and your new We can just as well leave it in then. We need a Makefile for W32 anyways. I'll add it again. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ PGP Key: FF8135CE |
×
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