[Clfs-dev] configure: error: compiler support for visibility attribute is required

[Pierre Lorenzon]

Hi Gilles, 

Thanks for your answer.


From: g.esp at free.fr
Subject: Re: [Clfs-dev] configure: error: compiler support for visibility attribute is required
Date: Thu, 20 Dec 2012 14:24:49 +0100 (CET)

> 
> 
> ----- Mail original -----
>> De: "Pierre Lorenzon" <devel at pollock-nageoire.net>
>> À: clfs-dev at lists.cross-lfs.org, berzerkula at cox.net
>> Envoyé: Jeudi 20 Décembre 2012 10:51:46
>> Objet: Re: [Clfs-dev] configure: error: compiler support for visibility attribute is required
>> 
> ...
> Could you post the configure snippet from lines 21050 to 21077?


  Here it is but in fact it is between line 20987 and 21058
  that looked more relevant to me. Sorry if this initiative is
  a mistake !

  >>>  -- gcc/configure 

# Identify the linker which will work hand-in-glove with the newly
# built GCC, so that we can examine its features.  This is the linker
# which will be driven by the driver program.
#
# If build != host, and we aren't building gas in-tree, we identify a
# build->target linker and hope that it will have the same features
# as the host->target linker we'll be using.
gcc_cv_gld_major_version=
gcc_cv_gld_minor_version=
gcc_cv_ld_gld_srcdir=`echo $srcdir | sed -e 's,/gcc$,,'`/ld
gcc_cv_ld_bfd_srcdir=`echo $srcdir | sed -e 's,/gcc$,,'`/bfd

if test "${gcc_cv_ld+set}" = set; then :

else

if test -x "$DEFAULT_LINKER"; then
	gcc_cv_ld="$DEFAULT_LINKER"
elif test -f $gcc_cv_ld_gld_srcdir/configure.in \
     && test -f ../ld/Makefile \
     && test x$build = x$host; then
	gcc_cv_ld=../ld/ld-new$build_exeext
elif test -x collect-ld$build_exeext; then
	# Build using linker in the current directory.
	gcc_cv_ld=./collect-ld$build_exeext
elif ( set dummy $LD_FOR_TARGET; test -x $2 ); then
        gcc_cv_ld="$LD_FOR_TARGET"
else
        # Extract the first word of "$LD_FOR_TARGET", so it can be a program name with args.
set dummy $LD_FOR_TARGET; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if test "${ac_cv_path_gcc_cv_ld+set}" = set; then :
  $as_echo_n "(cached) " >&6
else
  case $gcc_cv_ld in
  [\\/]* | ?:[\\/]*)
  ac_cv_path_gcc_cv_ld="$gcc_cv_ld" # Let the user override the test with a path.
  ;;
  *)
  as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
  IFS=$as_save_IFS
  test -z "$as_dir" && as_dir=.
    for ac_exec_ext in '' $ac_executable_extensions; do
  if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x "$as_dir/$ac_word$ac_exec_ext"; }; then
    ac_cv_path_gcc_cv_ld="$as_dir/$ac_word$ac_exec_ext"
    $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
    break 2
  fi
done
  done
IFS=$as_save_IFS

  ;;
esac
fi
gcc_cv_ld=$ac_cv_path_gcc_cv_ld
if test -n "$gcc_cv_ld"; then
  { $as_echo "$as_me:${as_lineno-$LINENO}: result: $gcc_cv_ld" >&5
$as_echo "$gcc_cv_ld" >&6; }
else
  { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi


fi
fi



>>>  -- End gcc/configure 


> And result of 
> find /cross-tools -name x86_64-unknown-linux-gnu-ld

  Oops it returns nothing what does that mean ?  But the
  following : 

  >>> -- find

[devel at jabberwocky ~]$ find /cross-tools/ -name
"*x86_64-unknown-linux-gnu-ld*"
/cross-tools/share/man/man1/x86_64-unknown-linux-gnu-ld.1
/cross-tools/bin/x86_64-unknown-linux-gnu-ld
/cross-tools/bin/x86_64-unknown-linux-gnu-ld.bfd
[devel at jabberwocky ~]$

  >>>  -- End find 

       looks correct to me. Replacing ld by as :

       >>>  -- find 

[devel at jabberwocky ~]$ find /cross-tools/ -name "*x86_64-unknown-linux-gnu-as*"
/cross-tools/share/man/man1/x86_64-unknown-linux-gnu-as.1
/cross-tools/bin/x86_64-unknown-linux-gnu-as
[devel at jabberwocky ~]$	

		          >>>  -- End find 

 Which is very similar. So I cannot understand why configure
 detects as and not ld. I must confess that I did not study in
 all details the configure portion relative to ld and compare
 it with that relative to as. That was the next thing I wanted
 to do to try to understand something.


 Regards

 Pierre

>
> Gilles
> _______________________________________________
> Clfs-dev mailing list
> Clfs-dev at lists.cross-lfs.org
> http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org