On Wed, 2003-07-02 at 05:16, Alexander Rawass wrote: > Ah - you're using the avifile.spec file to build it.
Correct. That's what it's there for.... > I never had a look at it before ;-) If you aren't trying to package it, you don't need it. > I *think* that editing the spec file and doing > %define prefix /opt/wherever Yup, that's what SHOULD work. > should work. It doesn't. Hence my bringing up the fact that the spec file distributed with the sources is subtly broken. > The point is - if you're building a rpm, the rpm build process does the whole > compiling/installing/etc by itself, depending on the values in that spec > file. Correct. > So you have to edit the spec file an run > rpm --rebuild avifile.spec (or so) Correct, this is what I have been doing all along. The issue is that the distributed spec file itself does not obey it's own settings. And it has internal conflicts over which parts listen to the settings and which parts don't. If it ignored the settings entirely, it would build an RPM (albeit with wrong paths); if it used all the settings, it would build an RPM (with correct paths). It does neither, it aborts with an error... :-( > Try it, and tell us if it works ;-) Been doing that all along, and that's why I'm telling you that it ain't working! Part of the distribution itself, is not acting as it should. I now have a build that looks like it works. I'll check it out this morning, then diff the .spec I'm using and the .spec generated by configure. I'll then try to modify the .spec.in file to cause configure to generate the right things, and then mail you guys the patches to the .spec.in file. Regards, Bevis. _______________________________________________ Avifile mailing list [EMAIL PROTECTED] http://prak.org/mailman/listinfo/avifile
