Hi,
- Mail original -
Intel compiler xilink will also output the information from the
underlying
Microsoft linker. A result is that both the Intel info header and the
Microsoft info header are output. This means that currently the Intel
linker will get detected as the msvc linker
On Thu, Nov 20, 2014 at 09:40:03AM +0100, Benoit Fouet wrote:
Hi,
- Mail original -
Intel compiler xilink will also output the information from the
underlying
Microsoft linker. A result is that both the Intel info header and the
Microsoft info header are output. This means that
On 11/20/2014 8:40 AM, Benoit Fouet wrote:
LGTM
http://fate.ffmpeg.org/report.cgi?time=20141120142015slot=i686-windows-icl
- Derek
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 21 November 2014 01:23, Derek Buitenhuis derek.buitenh...@gmail.com
wrote:
On 11/20/2014 8:40 AM, Benoit Fouet wrote:
LGTM
http://fate.ffmpeg.org/report.cgi?time=20141120142015slot=i686-windows-icl
- Derek
Works fine with lto, but apparently one shouldnt assume the existing code
is
On Fri, Nov 21, 2014 at 06:03:36AM +1100, Matt Oliver wrote:
On 21 November 2014 02:28, Matt Oliver protogo...@gmail.com wrote:
On 21 November 2014 01:23, Derek Buitenhuis derek.buitenh...@gmail.com
wrote:
On 11/20/2014 8:40 AM, Benoit Fouet wrote:
LGTM
Intel compiler xilink will also output the information from the underlying
Microsoft linker. A result is that both the Intel info header and the
Microsoft info header are output. This means that currently the Intel
linker will get detected as the msvc linker incorrectly as configure checks
for the
