1. 28 Dec, 2007 2 commits
    • unknown's avatar
      Merge trift2.:/MySQL/M50/bug33536-5.0 · e6f7c99e
      unknown authored
      into  trift2.:/MySQL/M51/bug33536-5.1
      
      
      scripts/make_binary_distribution.sh:
        Manual merge of the fix for bug#33536 from 5.0 to 5.1,
        the restructuring of this script makes automerge fail.
      e6f7c99e
    • unknown's avatar
      Merge trift2.:/MySQL/M41/bug33536-4.1 · 1b0a18a0
      unknown authored
      into  trift2.:/MySQL/M50/bug33536-5.0
      
      
      scripts/make_binary_distribution.sh:
        Auto merged
      1b0a18a0
  2. 27 Dec, 2007 1 commit
    • unknown's avatar
      scripts/make_binary_distribution.sh: · 86ebe38e
      unknown authored
      Fix the code to get the "libgcc" file name so that the failure of Intel's ICC
      to provide this information does not cause any problems.
      
      This fixes  bug#33536  Option "--print-libgcc-file" does not work with ICC compiler
      
      
      scripts/make_binary_distribution.sh:
        The (old) code to get the "libgcc" file name does not really work when using Intel's ICC.
        ICC accepts the "--print-libgcc-file" option but ignores it, does not produce any output.
        
        However, ICC tricks automake into taking it for a GCC ("GXX" variable is set, see
        http://www.gnu.org/software/autoconf/manual/html_node/C_002b_002b-Compiler.html#C_002b_002b-Compiler
        and its discussion of the "AC_PROG_CXX" macro).
        
        There are two possible approaches:
        a) Check "$CC" or "$CXX" to tell ICC from GCC, and do not ask ICC for the "libgcc" file name.
        b) Just ask it, but protect that code so that its failure does not cause any damage.
        
        This patch takes the second route:
        1) Put the call "@CC@ ... --print-libgcc-file" into a pipeline, followed by "|| true",
           so that (for the shell semantics) the command cannot fail.
           (ICC will exit non-zero because it is not given a source file.)
        2) Explicitly redirect any error messages.
        3) Do not use the compiler's return code but rather the (non)empty variable to check success.
        4) Ensure that the contents really is a file before taking it as a file name.
        
        Item 1) is especially important when the tool gets a "set -e" (this happens in 5.1, currently)
        which would make the failing compiler call a fatal thing.
        
        This fixes  bug#33536  Option "--print-libgcc-file" does not work with ICC compiler
      86ebe38e
  3. 21 Dec, 2007 5 commits
  4. 20 Dec, 2007 3 commits
  5. 17 Dec, 2007 5 commits
  6. 15 Dec, 2007 5 commits
  7. 14 Dec, 2007 19 commits