On 2016-04-16 17:24:12 +0000, Dave Yeo said:
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
Hmm, interesting use case. I bet this is because ramfs.ifs has some
problems with EAs (which are needed for proper symlink support on
OS/2). Looks like a ramfs.ifs bug to me.
And yes, it seems that the master branch uses ln_s not only in DLL
creation but also to symlink to src in the shadow build tree (I was
checking against the 2.8 branch before where it was not used). It,
however, contains a fallback code that should cover the failure in your
case (if I read it right). So I still think we should remove ln_s
redefinition via cp on OS/2 in FFmpeg. In case of a proper IFS (I have
JFS here but HPFS is also fine) symlinking src works like a charm
(performed a full build).
--
Kind regards,
Dmitriy Kuminov
CPO of bww bitwise works GmbH
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
