[Flac-dev] 1.0 candidate checked in

[collver at linuxfreemail.com]

On Thu, Jul 19, 2001 at 05:01:07PM -0400, Matt Zimmerman wrote:
> On Thu, Jul 19, 2001 at 04:58:44PM -0400, Matt Zimmerman wrote:
> 
> > On Thu, Jul 19, 2001 at 10:38:14AM -0700, Josh Coalson wrote:
> > 
> > > So, last chance to checkout from CVS and break it!
> > 
> > Also, my libtool doesn't seem to recognize --tag=CC.  What is its purpose?
> > 
> > /bin/sh ../../../libtool --tag=CC --mode=compile \
> >         sh ../../../strip_fPIC.sh nasm -f elf -d OBJ_FORMAT_elf cpu_asm.nasm
> > libtool: unrecognized option `--tag=CC'
> > Try `libtool --help' for more information.
> 
> Once I removed that, it also seems to hate the .nasm extension:
> 
> /bin/sh ../../../libtool --mode=compile \
>         sh ../../../strip_fPIC.sh nasm -f elf -d OBJ_FORMAT_elf cpu_asm.nasm
> libtool: compile: cannot determine name of library object from `cpu_asm.nasm'
> 
> Is there some pressing reason to use libtool to compile these objects, rather
> than just executing nasm?  I seem to recall there being a thread about this,
> but I can't remember what was decided.

After looking around, I can take the blame for some of this:

flac is distributed with a libtool script generated by libtool 1.3.5
apparently libtool 1.3.5 does not understand "--tag=CC" and it does
not require library objects to be generated by libtool.

I want to use a different libtool on my system, version 1.4.  This
version requires "--tag=SOMETHING" and requires library objects to
be generated by libtool.

Maybe it would be a good idea to either (1) undo the patch I sent or
(2) generate flac's libtool script using libtool 1.4.

Both versions recognize .asm but not .nasm.  I recommend renaming the
.nasm files to .asm files.

Ben