Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
patches/binutils/2.17a/150-check_ldrunpath_length.patch
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Thu Dec 27 12:45:22 2012 +0100 (2012-12-27)
changeset 3152 b286c7993be5
parent 747 d3e603e7c17c
permissions -rw-r--r--
scripts/addToolsVersion: properly handle .in vs. .in.2

While most components have their version in the .in file, some
have it in the .in.2 (eg. elf2flt).

Currently, to handle this case, we indiscriminately munge both files,
but this is wrong: in the elf2flt case, if we add a binutils version,
we do not want it to be added to elf2flt, and conversely.

So, for each tool, we need to explicitly know what file to munge.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> 
     1 diff -dur binutils-2.17.old/ld/emultempl/elf32.em binutils-2.17/ld/emultempl/elf32.em

     2 --- binutils-2.17.old/ld/emultempl/elf32.em	2006-06-12 15:05:04.000000000 +0200

     3 +++ binutils-2.17/ld/emultempl/elf32.em	2007-05-01 18:26:13.000000000 +0200

     4 @@ -970,6 +970,8 @@

     5  	      && command_line.rpath == NULL)

     6  	    {

     7  	      lib_path = (const char *) getenv ("LD_RUN_PATH");

     8 +	      if ((lib_path) && (strlen (lib_path) == 0))

     9 +		  lib_path = NULL;

    10  	      if (gld${EMULATION_NAME}_search_needed (lib_path, &n,

    11  						      force))

    12  		break;

    13 @@ -1154,6 +1156,8 @@

    14    rpath = command_line.rpath;

    15    if (rpath == NULL)

    16      rpath = (const char *) getenv ("LD_RUN_PATH");

    17 +  if ((rpath) && (strlen (rpath) == 0))

    18 +      rpath = NULL;

    19    if (! (bfd_elf_size_dynamic_sections

    20  	 (output_bfd, command_line.soname, rpath,

    21  	  command_line.filter_shlib,
crosstool-ng