All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH] Remove checks for libcurl--we don't use it anymore
Date: Wed, 31 Aug 2005 22:41:13 -0500	[thread overview]
Message-ID: <43167859.9050000@us.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 233 bytes --]

These files seem to creep back into the build frequently due to merges.  
We don't depend on libcurl anymore (since we removed xfrd) so there's no 
point in checking for it.

Signed-off-by: Anthony Liguori

Regards,

Anthony Liguori

[-- Attachment #2: 6560_remove_libcurl.diff --]
[-- Type: text/x-patch, Size: 987 bytes --]

# HG changeset patch
# User root@howler
# Node ID 638d08f7e6ce904b763b59a3e2b38f1812af74de
# Parent  f0dc15fd3c1bcfc63e432e7fb365792cc671e955
Remove libcurl dependences, we don't need it anymore

diff -r f0dc15fd3c1b -r 638d08f7e6ce tools/check/check_curl_devel
--- a/tools/check/check_curl_devel	Wed Aug 31 23:22:45 2005
+++ /dev/null	Thu Sep  1 03:31:26 2005
@@ -1,11 +0,0 @@
-#!/bin/bash
-# CHECK-BUILD
-
-function error {
-    echo 'Check for libcurl includes failed.'
-    exit 1
-}
-
-set -e
-[ -e /usr/include/curl ] || error
-[ -e /usr/include/curl/curl.h ] || error
\ No newline at end of file
diff -r f0dc15fd3c1b -r 638d08f7e6ce tools/check/check_curl_lib
--- a/tools/check/check_curl_lib	Wed Aug 31 23:22:45 2005
+++ /dev/null	Thu Sep  1 03:31:26 2005
@@ -1,10 +0,0 @@
-#!/bin/bash
-# CHECK-BUILD CHECK-INSTALL
-
-function error {
-        echo 'Check for CURL library failed.'
-        exit 1
-}
-
-set -e
-ldconfig -p | grep libcurl.so || error
\ No newline at end of file

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

                 reply	other threads:[~2005-09-01  3:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43167859.9050000@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.