Hi,
> On Tue, 26 Mar 2002, Paul Davis wrote:
>
>
>>I suggest you buy the O'Reilly book on autoconf/automake and read it
>>*carefully*. It contains far more information than you will get from
>>this or any other mailing list.
>
>
> Would you happen to have an exact title or ISBN number for this
On Tue, Mar 26, 2002 at 09:10:57PM +0200, Juhana Sadeharju wrote:
> Hello.
>
> Are there any software which can generate Configure.in/Makefile.in etc.
> files automatically? I tried the auto* programs but I got nothing which
> could ever compile. I could not understand what was missing in config
On Tue, 26 Mar 2002, Paul Davis wrote:
> I suggest you buy the O'Reilly book on autoconf/automake and read it
> *carefully*. It contains far more information than you will get from
> this or any other mailing list.
Would you happen to have an exact title or ISBN number for this? I can
find no s
On Tue, 26 Mar 2002, Juhana Sadeharju wrote:
> Hello.
>
> Are there any software which can generate Configure.in/Makefile.in etc.
> files automatically?
autoproject, google for it. or do like other auto* beginners and just
copy some other simple project's setup.
> Is there anything which could
On Tue, 26 Mar 2002 21:10:57 +0200
Juhana Sadeharju <[EMAIL PROTECTED]> wrote:
> Hello.
>
> Are there any software which can generate Configure.in/Makefile.in etc.
If you use automake, you don't need to write Makefile.in but rather
Makefile.am which is far simpler.
The configure.in is relativ
>Are there any software which can generate Configure.in/Makefile.in etc.
>files automatically? I tried the auto* programs but I got nothing which
>could ever compile. I could not understand what was missing in configure.in.
>It actually would had been easier to write Makefile manually... but I'm
>
Hi,
I think kdevelop can do something similar.
/Robert
Juhana Sadeharju wrote:
>Hello.
>
>Are there any software which can generate Configure.in/Makefile.in etc.
>files automatically? I tried the auto* programs but I got nothing which
>could ever compile. I could not understand what was missi
Hello.
Are there any software which can generate Configure.in/Makefile.in etc.
files automatically? I tried the auto* programs but I got nothing which
could ever compile. I could not understand what was missing in configure.in.
It actually would had been easier to write Makefile manually... but I
On Mon, 25 Mar 2002, Fred Gleason wrote:
> On Mon, 25 Mar 2002, Paul Davis wrote:
>
> > such users should not be installing software that is only available
> > from CVS.
>
> Hmm. I think I see your point, but I wonder if you've considered all the
> broader picture. I'm getting set to start po
>Hmm. I think I see your point, but I wonder if you've considered all the
>broader picture. I'm getting set to start porting some of my stuff over
>to Jack in the next week or so. I'm not particularly interested in the
>internals of how it works (except insofar as that may drive the design of
>
On Mon, 25 Mar 2002, Paul Davis wrote:
> such users should not be installing software that is only available
> from CVS.
Hmm. I think I see your point, but I wonder if you've considered all the
broader picture. I'm getting set to start porting some of my stuff over
to Jack in the next week or
>I think it just depends on the audience you're trying to reach.
>Configure scripts make things a bit easier (especially with CVS only
>software), and if you can make things a bit easier, you might reach a
>wider audience than you normally would have. Not everybody (even
>Linux enthusiasts/users)
>After installing libtool 1.4.8 via tarball and running autogen-sh, I
>get:
>
>[root@friday jack]# ./autogen.sh
>You should add the contents of `/usr/local/share/aclocal/libtool.m4'
>to `aclocal.m4'.
this is an extremely misleading message. it arises from one the early
steps carried out by autoge
On Mon, 25 Mar 2002 09:45:04 +0100, Oliver Sampson
<[EMAIL PROTECTED]> wrote:
>On Sun, 24 Mar 2002 09:54:23 -0500, Andy Wingo <[EMAIL PROTECTED]>
>wrote:
>
>>
>>that said, the errors you're getting with running autogen are probably
>>due to a missing libtool-dev package.
>
>This is more along the
On Sun, 24 Mar 2002 10:11:36 -0500, Paul Davis <[EMAIL PROTECTED]> wrote:
>>On Sun, 24 Mar 2002 09:23:04 +0100
>>Oliver Sampson <[EMAIL PROTECTED]> wrote:
>>
>>> [olsam@friday jack]$ autoconf
>>
>>Why are you runing autoconf?
>>
>>Did you read the installation instructions in the INSTALL file?
On Sun, 24 Mar 2002 09:54:23 -0500, Andy Wingo <[EMAIL PROTECTED]>
wrote:
>
>that said, the errors you're getting with running autogen are probably
>due to a missing libtool-dev package.
This is more along the lines to what I was thinking. I've found a
libtool and a libtool-libs rpms, but the g
On Sun, 24 Mar 2002, Junichi Uekawa wrote:
> Oliver Sampson <[EMAIL PROTECTED]> cum veritate scripsit:
>
> > For example when trying to install JACK (which I'll need for ardour) I
> > get:
> >
> > [olsam@friday jack]$ autoconf
> > configure.in:24: error: possibly undefined macro: AM_INIT_AUTOMA
>On Sun, 24 Mar 2002 09:23:04 +0100
>Oliver Sampson <[EMAIL PROTECTED]> wrote:
>
>> [olsam@friday jack]$ autoconf
>
>Why are you runing autoconf?
>
>Did you read the installation instructions in the INSTALL file?
>
>Only package manitainers need to run autoconf etc. You should be running
>the co
> On Sun, 24 Mar 2002 09:23:04 +0100
> Oliver Sampson <[EMAIL PROTECTED]> wrote:
>
> > [olsam@friday jack]$ autoconf
>
> Why are you runing autoconf?
Older versions of ardour might have required users to run autoconf,
IIRC. (Did you get the ardour tarball? It's way out of date - get the
CVS
On Sun, 24 Mar 2002, Erik de Castro Lopo wrote:
> On Sun, 24 Mar 2002 09:23:04 +0100
> Oliver Sampson <[EMAIL PROTECTED]> wrote:
>
> > [olsam@friday jack]$ autoconf
>
> Why are you runing autoconf?
>
> Did you read the installation instructions in the INSTALL file?
>
> Only package manitain
Oliver Sampson <[EMAIL PROTECTED]> cum veritate scripsit:
> For example when trying to install JACK (which I'll need for ardour) I
> get:
>
> [olsam@friday jack]$ autoconf
> configure.in:24: error: possibly undefined macro: AM_INIT_AUTOMAKE
> configure.in:46: error: possibly undefined macro: AC_
On Sun, 24 Mar 2002 09:23:04 +0100
Oliver Sampson <[EMAIL PROTECTED]> wrote:
> [olsam@friday jack]$ autoconf
Why are you runing autoconf?
Did you read the installation instructions in the INSTALL file?
Only package manitainers need to run autoconf etc. You should be running
the configure scr
Howdy,
I think this is the right list to post to:
I"m trying to get some audio software up and running on my Linux
machine. My Linux machine is a RH7.0 with lots of 7.2 and even newer
packages on it. I've used both a combination of RPMs (when
convenient) and tarball installations.
Right now,
23 matches
Mail list logo
