Re: [transcode-devel] (Minor glitch) Poorly phrased complaint from ./configure

2006-12-12 Thread Andrew Church
>> If you'd like to fix it, then by all means >>do so, and we'll incorporate the patches into CVS. > >I'd have already done that if I could, but unfortunately 'autoconf' and >the entire ./configure script thing is a black art to me. To tell the truth, it's pretty close to that for the rest o

Re: [transcode-devel] (Minor glitch) Poorly phrased complaint from ./configure

2006-12-12 Thread Steve Hosgood
Andrew Church wrote: > The organization of the configure script (including issues like this) >has come up before, but it's been lower on the priority list than Francesco >or I have been able to get to. > Quite understandable. > If you'd like to fix it, then by all means >do so, and we'll inc

Re: [transcode-devel] Build problem (recent 1.1.0 CVS)

2006-12-12 Thread Steve Hosgood
Andrew Church wrote: >>I've got a CVS checkout from a week or so ago and compiled it fine >>(eventually). Then I spotted a bug in import of .nuv files, realised >>what it was, and went into import/nuv/import_nuv.c to made a few edits. >> >>I then came back out to the top directory and typed 'mak

Re: [transcode-devel] (Minor glitch) Poorly phrased complaint from ./configure

2006-12-12 Thread Andrew Church
The organization of the configure script (including issues like this) has come up before, but it's been lower on the priority list than Francesco or I have been able to get to. If you'd like to fix it, then by all means do so, and we'll incorporate the patches into CVS. (Though to be honest,

Re: [transcode-devel] Build problem (recent 1.1.0 CVS)

2006-12-12 Thread Andrew Church
>I've got a CVS checkout from a week or so ago and compiled it fine >(eventually). Then I spotted a bug in import of .nuv files, realised >what it was, and went into import/nuv/import_nuv.c to made a few edits. > >I then came back out to the top directory and typed 'make'. 'Make' went >through a

[transcode-devel] (Minor glitch) Poorly phrased complaint from ./configure

2006-12-12 Thread Steve Hosgood
If you try and run ./configure with --enable-nuv then it is a requirement that you specify --enable-lzo to go with it. However, the check for this dependency is made rather late and probably should have been done before the guts of ./configure ran at all. You get the message: configure: error:

[transcode-devel] Build problem (recent 1.1.0 CVS)

2006-12-12 Thread Steve Hosgood
I've got a CVS checkout from a week or so ago and compiled it fine (eventually). Then I spotted a bug in import of .nuv files, realised what it was, and went into import/nuv/import_nuv.c to made a few edits. I then came back out to the top directory and typed 'make'. 'Make' went through all th