Skip to content
  1. Sep 03, 2005
  2. Aug 27, 2005
    • Reid Spencer's avatar
      Implement PR614: · dfb3fb4a
      Reid Spencer authored
      These changes modify the makefiles so that the output of flex and bison are
      placed in the SRC directory, not the OBJ directory. It is intended that they
      be checked in as any other LLVM source so that platforms without convenient
      access to flex/bison can be compiled. From now on, if you change a .y or
      .l file you *must* also commit the generated .cpp and .h files.
      
      llvm-svn: 23115
      dfb3fb4a
  3. Aug 25, 2005
    • Reid Spencer's avatar
      For PR614: · 53846bcd
      Reid Spencer authored
      Move the implementation of the fix from Makefile.rules to Makefile. This
      ensures that it is only checked on a top-level rebuild, and not in every
      single subdirectory. This removes some annoying messages from the build and
      numerous executions of config.status if the .in file changes but not
      substantively enough to cause the .h file to be modified by config.status.
      
      llvm-svn: 23039
      53846bcd
    • Reid Spencer's avatar
      Don't attempt to update LLVM configured header files from a build in a · 83bde55c
      Reid Spencer authored
      project. Thanks to Chris for pointing out this deficiency.
      
      llvm-svn: 23037
      83bde55c
  4. Aug 24, 2005
    • Reid Spencer's avatar
      Whoops, don't use PROJ variables, these are all LLVM headers. This allows · bfb0c166
      Reid Spencer authored
      projects to compile properly.
      
      llvm-svn: 23007
      bfb0c166
    • Reid Spencer's avatar
      For PR619: · b48e3f8b
      Reid Spencer authored
      Make any header files that are automatically generated be preconditions of
      the compilation. This ensures that if a *.h.in file is changed then its
      corresponding *.h file gets updated on the next rebuild. Note that this can
      lead to confusing (but correct) results if the *.h.in file changed
      unsubstantially so that autoheader doesn't update the *.h file. In that case,
      manually touch the *.h file in question to restore order. Moral of the story,
      if you're going to "touch" a *.in file then modify it substantially.
      
      llvm-svn: 23006
      b48e3f8b
  5. Aug 17, 2005
  6. Aug 13, 2005
  7. Jul 23, 2005
  8. Jul 22, 2005
  9. May 24, 2005
    • Reid Spencer's avatar
      Two dist-check related changes: · 13f5193f
      Reid Spencer authored
      1. Allow DIST_CHECK_CONFIG_OPTION to specify a set of options to be passed
         to the configure script during the dist-check target. This allows things
         to be passed down on a project basis so the configure doesn't fail.
      
      2. Use the tar | (cd ; tar ) idiom to copy files which is more flexible
         than using the cp command. THis allows us to exclude CVS .svn
         directories at source rather than stripping them out of the tar ball.
      
      llvm-svn: 22166
      13f5193f
  10. May 19, 2005
  11. May 16, 2005
  12. May 13, 2005
  13. Mar 11, 2005
  14. Mar 01, 2005
  15. Feb 27, 2005
  16. Feb 24, 2005
  17. Feb 16, 2005
  18. Feb 14, 2005
    • Reid Spencer's avatar
      For PR496: · e9fa5444
      Reid Spencer authored
      When llvm-gcc is not available, bypass rules for Modules and Bytecode
      Libraries that require llvm-gcc and emit instead a warning that llvm-gcc
      is not available. This permits "make LLVMGCC=" to build LLVM completely
      without error and provides warnings about the modules and bc libs that
      could not be constructed.
      
      llvm-svn: 20185
      e9fa5444
  19. Feb 13, 2005
  20. Feb 09, 2005
  21. Feb 04, 2005
  22. Feb 02, 2005
  23. Jan 28, 2005
  24. Jan 16, 2005
    • Reid Spencer's avatar
      Several changes: · ba6a3dbd
      Reid Spencer authored
      * Rename BUILD_* to PROJ_*
      * Differentiate between LLVM's Makefile.conf and the project's
      * Use project specific install locations
      
      llvm-svn: 19590
      ba6a3dbd
  25. Jan 14, 2005
  26. Jan 11, 2005
    • Reid Spencer's avatar
      Implement the LOADABLE_MODULE option when building a shared library. This · 87e645c5
      Reid Spencer authored
      passes the -module option on the libtool command line to ensure that the
      shared library being built can be dlopened and dlsym can work on that
      module. LOADABLE_MODULE should be sent only in conjunction with the
      SHARED_LIBRARY directive. It should generally be used for any module that
      is intended to be the target of an LLVM -load option. Note that loadable
      modules will not have the lib prefix but otherwise look like shared
      libraries. This is per the libtool recommendations and prevents these
      special shared libraries from being linked in via -l option to the linker.
      
      llvm-svn: 19454
      87e645c5
  27. Jan 07, 2005
  28. Jan 03, 2005
Loading