On Saturday, November 2, 2013, Martin Storsjö wrote: > On Sat, 2 Nov 2013, Vittorio Giovara wrote: > > --- >> Hi, I think I was able to remove the -wN flag warning on OSX, but then a >> new error popped out: >> >> YASM libavcodec/x86/h264_deblock_10bit.o >> /Applications/Xcode.app/Contents/Developer/Toolchains/ >> XcodeDefault.xctoolchain/usr/bin/strip: symbols referenced by relocation >> entries that can't be stripped in: libav/libavcodec/x86/h264_ >> deblock_10bit.o >> _ff_pw_4 >> pw_pixel_max >> _ff_pw_2 >> _ff_pw_3 >> > > The thing is simply that the flags for strip are essential. If you can't > use these flags, then you should rather not do strip (here) at all. > > x264 uses the strip flag -x instead of these flags for this same purpose. > I think -x is more widely available, but the -wN '..@*' params is more > exactly what is desired here. So perhaps first try if -wN works, if not > then do -x, if that doesn't, then don't strip at all. > > Ok just what happens if both -wN and -x are supplied? Could they coexist for the stripping operation we do? Also is there any strip version around that does not support -x? Binutils strip has it since 1999. One more question, should I add a configure option that allows to add strip flags from the user? Thank you, Vittorio
// Martin > _______________________________________________ > libav-devel mailing list > [email protected] > https://lists.libav.org/mailman/listinfo/libav-devel > _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
