On Sat, Sep 24, 2011 at 11:59:48AM +0100, Måns Rullgård wrote:
> Sean McGovern <[email protected]> writes:
> 
> > When using suncc to build, the Solaris linker will mark
> > an executable with each instruction set encountered by
> > the Solaris assembler.  As our libraries contain their own
> > guards for processor-specific code, instead suppress
> > generation of the HWCAPS ELF section on Solaris x86 only.
> > ---
> >  configure |    8 ++++++++
> >  1 files changed, 8 insertions(+), 0 deletions(-)
> 
> enabled_all suncc x86 && ...

ok to push otherwise?

Janne
>From 87a74f478f1c9ff21c2c0101a498506ce6b1d631 Mon Sep 17 00:00:00 2001
From: Sean McGovern <[email protected]>
Date: Sat, 17 Sep 2011 00:36:37 -0400
Subject: [PATCH] configure: disable hardware capabilities ELF section with
 suncc on Solaris x86

When using suncc to build, the Solaris linker will mark
an executable with each instruction set encountered by
the Solaris assembler.  As our libraries contain their own
guards for processor-specific code, instead suppress
generation of the HWCAPS ELF section on Solaris x86 only.

Signed-off-by: Janne Grunau <[email protected]>
---
 configure |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/configure b/configure
index e01d9fd..8440cab 100755
--- a/configure
+++ b/configure
@@ -2370,6 +2370,12 @@ case $target_os in
         enabled x86 && SHFLAGS="-mimpure-text $SHFLAGS"
         network_extralibs="-lsocket -lnsl"
         add_cppflags -D__EXTENSIONS__
+        # When using suncc to build, the Solaris linker will mark
+        # an executable with each instruction set encountered by
+        # the Solaris assembler.  As our libraries contain their own
+        # guards for processor-specific code, instead suppress
+        # generation of the HWCAPS ELF section on Solaris x86 only.
+        enabled_all suncc x86 && echo "hwcap_1 = OVERRIDE;" > mapfile && 
add_ldflags -Wl,-M,mapfile
         nm_opts='-P -g'
         ;;
     netbsd)
-- 
1.7.6.1

_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to