1. 28 Sep, 2010 3 commits
  2. 27 Sep, 2010 4 commits
  3. 26 Sep, 2010 2 commits
  4. 23 Sep, 2010 1 commit
  5. 22 Sep, 2010 16 commits
  6. 21 Sep, 2010 4 commits
  7. 20 Sep, 2010 5 commits
    • Hendrik Visage's avatar
      MacOSX-Framework: updates for Snowleopard · 70a025f3
      Hendrik Visage authored
      1) PPC64 appears to be an 10.5 only supported architecture, so I
      forced 10.5 for 64bit if there is a need for PPC64, else 64bit only
      does x86_64
      
      2) proper "make clean" after every ./configure. fixes a bug where
      subsequent runs the 32bit do not get compiled
      
      3) Added a version numbering curl-$VERSION} rather than the "stock standard" A
      70a025f3
    • Daniel Stenberg's avatar
      RELEASE-NOTES: synced with 5fcc4332 · 95e230c5
      Daniel Stenberg authored
      Removed the duplicate entry of Kamil in the credits.
      95e230c5
    • Daniel Stenberg's avatar
      configure: don't enable RTMP if the lib detect fails · 5fcc4332
      Daniel Stenberg authored
      librtmp is often statically linked and using sub dependencies like
      OpenSSL, so we need to make sure we can actually link with it properly
      before enabling it. Otherwise we easily end up trying to link with a
      RTMP lib that fails.
      5fcc4332
    • Daniel Stenberg's avatar
      TODO: added 8.4 non-gcrypt under GnuTLS · 7d84113e
      Daniel Stenberg authored
      We must not assume gcrypt just because of GnuTLS
      7d84113e
    • Daniel Stenberg's avatar
      configure: check for gcrypt if using GnuTLS · f3df524b
      Daniel Stenberg authored
      1 - libcurl assumes that there are gcrypt functions available when
      GnuTLS is.
      
      2 - GnuTLS can be built to use libnettle instead as crypto library,
      which breaks assumption (1)
      
      This change makes configure make sure that if GnuTLS is requested and
      detected, it also makes sure that gcrypt is present or it errors
      out. This is mostly a way to make the user more aware of this flaw, the
      correct fix would be to detect which crypto layer that is in use and
      adapt our code to use that instead of blindly assuming gcrypt.
      
      Reported by: Michal Gorny
      Bug: http://curl.haxx.se/bug/view.cgi?id=3071038
      f3df524b
  8. 18 Sep, 2010 5 commits