On 05/27/11 11:55 am, Diego Biurrun wrote:
On Thu, May 26, 2011 at 11:08:16PM -0700, Dave Yeo wrote:
On 05/26/11 05:53 am, Diego Biurrun wrote:
Libav should now compile out-of-the-box on OS/2 and the
information contained in the linked page is badly outdated.
It compiles out of the box with the correct shell ((pdk)sh). Unluckily
eCS ships with ash which has a bug where $PWD is not initially set. This
results in everything going smoothly till the end when linking
ffmpeg.exe fails with 39 missing symbols due to bad -L options.
Does adding
PWD=$(pwd)
to the beginning of configure fix the issue?
Yes, doing
--- a/configure
+++ b/configure
@@ -14,6 +14,7 @@ export LC_ALL
# make sure we are running under a compatible shell
# try to make this part work with most shells
+PWD=$(pwd)
try_exec(){
echo "Trying shell $1"
type "$1" > /dev/null 2>&1 && exec "$@"
allows the build to finish though configure spits out
"YASM not found" at one point, pretty minor.
I also do get errors such as
Can't read init file I:/usr/src/libav/doc/t2h.init
and the HTML files are broken. I just quickly hacked texi2html v5 to
work here so that is probably the problem.
Quite a few projects fail when building documentation and there is a
good chance that people don't have a new enough texi2html anyways.
Documentation is cross platform and can be downloaded or the raw texi
files read.
[...]
--- doc/texi2pod.pl (revision 10843)
+++ doc/texi2pod.pl (working copy)
@@ -1,4 +1,6 @@
-#! /usr/bin/perl -w
+#!perl
+ eval 'exec perl -wS $0 ${1+"$@"}'
+ if 0;
Does replacing the first line with
#!/usr/bin/env perl -w
work? That is something I could apply directly to Libav.
I can't reproduce the error right now. I'm pretty sure I've tested this
before with negative results. I think best if failure to build the
documentation only fail with something like error 127 so not a show
stopper if someone wants to run make test etc.
Patch OK with the PWD=$(pwd) added to configure.
Thanks
Dave
ps OK to change my FATE configuration to use GCC 4.5.2 as that is the
currently shipping GCC?
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
