1. 28 Dec, 2007 3 commits
    • unknown's avatar
      Merge trift2.:/MySQL/M50/bug33536-5.0 · b08baf91
      unknown authored
      into  trift2.:/MySQL/M50/push-5.0
      
      
      b08baf91
    • unknown's avatar
      Merge trift2.:/MySQL/M41/bug33536-4.1 · be2c41aa
      unknown authored
      into  trift2.:/MySQL/M50/bug33536-5.0
      
      
      scripts/make_binary_distribution.sh:
        Auto merged
      be2c41aa
    • unknown's avatar
      make_win_bin_dist CMakeLists.txt resolveip.c Makefile.am: · 471437fd
      unknown authored
        Better Windows support in the scripts directory
      mysql_config.pl.in, mysql_install_db.pl.in:
        New Perl version of Unix shell script, mainly for Windows
      Many files in scripts directory:
        Use default Perl location "#!/usr/bin/perl" instead of the build host path
      
      
      extra/CMakeLists.txt:
        Added target for executable "resolveip"
      extra/resolveip.c:
        Exclude Unix specific headers when compiling on Windows
      scripts/CMakeLists.txt:
        On Windows, filter Perl scripts and change name from ".sh" to ".pl"
        
          mysql_convert_table_format.sh  mysql_explain_log.sh
          mysql_secure_installation.sh   mysql_tableinfo.sh
          mysqld_multi.sh                mysqldumpslow.sh
          mysqlhotcopy.sh
        
        Do the same for the new Windows specific Perl versions of shell scripts
        
          mysql_config.pl.in             mysql_install_db.pl.in
        
        In CMake, set reasonable values for 'CFLAGS', 'prefix', 'datadir' and so on.
      scripts/Makefile.am:
        Include "mysql_config.pl.in" and "mysql_install_db.pl.in" in the source TAR
      scripts/make_win_bin_dist:
        Only include explicitly listed scripts from the "scripts" directory
      scripts/mysql_convert_table_format.sh:
        Use default Perl location "#!/usr/bin/perl" instead of the build host path
      scripts/mysql_explain_log.sh:
        Use default Perl location "#!/usr/bin/perl" instead of the build host path
      scripts/mysql_tableinfo.sh:
        Use default Perl location "#!/usr/bin/perl" instead of the build host path
      scripts/mysqld_multi.sh:
        Use default Perl location "#!/usr/bin/perl" instead of the build host path
      scripts/mysqldumpslow.sh:
        Use default Perl location "#!/usr/bin/perl" instead of the build host path
      scripts/mysqlhotcopy.sh:
        Use default Perl location "#!/usr/bin/perl" instead of the build host path
      scripts/mysql_config.pl.in:
        New Perl version of Unix shell script, mainly for Windows
      scripts/mysql_install_db.pl.in:
        New Perl version of Unix shell script, mainly for Windows
      471437fd
  2. 27 Dec, 2007 1 commit
    • unknown's avatar
      scripts/make_binary_distribution.sh: · 07aab86f
      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
      07aab86f
  3. 21 Dec, 2007 2 commits
  4. 20 Dec, 2007 1 commit
  5. 17 Dec, 2007 2 commits
  6. 15 Dec, 2007 1 commit
  7. 14 Dec, 2007 10 commits
  8. 13 Dec, 2007 15 commits
  9. 12 Dec, 2007 2 commits
  10. 11 Dec, 2007 3 commits