On 04/16/16 09:29 AM, Dmitriy Kuminov wrote:
On 2016-04-16 04:52:23 +0000, KO Myung-Hun said:
diff --git a/configure b/configure
index ff80aee..36a23f4 100755
--- a/configure
+++ b/configure
@@ -4716,7 +4716,6 @@ case $target_os in
;;
os/2*)
strip="lxlite -CS"
- ln_s="cp -f"
Please do not remove this. Copying is more compatible than a symbolic
link on OS/2.
"More compatible" is a too general allegation. In this particular case
(FFmpeg) LN_S is only used to create 'avcodec.dll` from `avcode56.dll`
and alike which is completely unneeded on OS/2 (so symlinking doesn't
harm but saves some time & disk space). And more over, symlinks work
well in most cases in a proper OS/2 environment these days. So I think
they should be generally enabled unless there is a specific case when
they introduce a real incompatibility. FFmpeg is not such a case.
Actually I now get this at the beginning of the configure run, using a
ramfs.ifs volume for $TMPDIR,
[K:\usr\local\src\ffmpeg.obj]sh ../ffmpeg/configure --enable-gpl
--disable-doc --samples=/usr/local/share/fate-suite --cpu=i686
--extra-libs=-lpoll --prefix='r:/tmp/ffmpeg' --disable-static
--enable-shared
ln: failed to create symbolic link `R:/tmp/name_VJhuEZNf': Operation not
supported on socket
I'll have to file a bug at Netlabs
Dave
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
