From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 644210491392 X-Google-Groups: supmua X-Google-Thread: 3030fda1bf,ed8e139b3a39490b,start X-Google-Attributes: gid3030fda1bf,domainid0,public,googlegroup X-Google-NewGroupId: yes X-Received: by 10.42.103.208 with SMTP id n16mr31221685ico.22.1426698238028; Wed, 18 Mar 2015 10:03:58 -0700 (PDT) X-BeenThere: supmua@googlegroups.com Received: by 10.50.83.38 with SMTP id n6ls557450igy.20.gmail; Wed, 18 Mar 2015 10:03:57 -0700 (PDT) X-Received: by 10.66.236.74 with SMTP id us10mr54257655pac.28.1426698237709; Wed, 18 Mar 2015 10:03:57 -0700 (PDT) Return-Path: Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com. [2607:f8b0:4001:c05::234]) by gmr-mx.google.com with ESMTPS id e4si242028igt.3.2015.03.18.10.03.57 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Mar 2015 10:03:57 -0700 (PDT) Received-SPF: pass (google.com: domain of pengyu.ut@gmail.com designates 2607:f8b0:4001:c05::234 as permitted sender) client-ip=2607:f8b0:4001:c05::234; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of pengyu.ut@gmail.com designates 2607:f8b0:4001:c05::234 as permitted sender) smtp.mail=pengyu.ut@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Received: by mail-ig0-x234.google.com with SMTP id ue6so105709004igb.1 for ; Wed, 18 Mar 2015 10:03:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=a1H+ghHAWG6w4tfRir00wdDOESQrNYJWi1UotikYCnE=; b=DrpCq00P+06WlAahSS8d+F4HBmkziEtEel8R9ro+H6R3/wCSKlGR15YeI/ZZpacdC6 bOI7+cjqNP3xuwchmtCca83DZP1DfLEM2WQAf8VEvVuVjQJ9a+Ttu3EmelzWWXBfZMgF +aREHfKwvUJ/OufNxDGy+jyawekr9VldJGhnmVbtOMBDRjrRL+VYqc45ewnt6wSS9Z9n D0boo2v5EuX1aUDq8Z1wm62fRLTOmERy5UgAPOgUpnD8e6q2DnOI6W9hygYDRiNcS0gh urE+KKqoJLFkp0Cx1BZSvMYHb2GZhjeEfiv9YAwPcaug/bc/cBIw1D4EcNI0nMyRsg6j zX2g== MIME-Version: 1.0 X-Received: by 10.107.150.149 with SMTP id y143mr39090532iod.21.1426698237594; Wed, 18 Mar 2015 10:03:57 -0700 (PDT) Received: by 10.42.123.11 with HTTP; Wed, 18 Mar 2015 10:03:57 -0700 (PDT) Date: Wed, 18 Mar 2015 12:03:57 -0500 Message-ID: Subject: xapian problem (install sup) From: Peng Yu To: None Content-Type: text/plain; charset=UTF-8 I have the following problem, when I install sup. Does anybody know what is wrong? Thanks. /tmp/ruby-2.0.0-p643$ sudo gem install sup Fetching: ncursesw-1.4.9.gem (100%) Building native extensions. This could take a while... Successfully installed ncursesw-1.4.9 Fetching: rmail-sup-1.0.1.gem (100%) Successfully installed rmail-sup-1.0.1 Fetching: highline-1.7.1.gem (100%) Successfully installed highline-1.7.1 Fetching: trollop-2.1.2.gem (100%) Successfully installed trollop-2.1.2 Fetching: lockfile-2.1.3.gem (100%) Successfully installed lockfile-2.1.3 Fetching: mime-types-1.25.1.gem (100%) Successfully installed mime-types-1.25.1 Fetching: locale-2.1.0.gem (100%) Successfully installed locale-2.1.0 Fetching: chronic-0.9.1.gem (100%) Successfully installed chronic-0.9.1 Fetching: unicode-0.4.4.2.gem (100%) Building native extensions. This could take a while... Successfully installed unicode-0.4.4.2 Fetching: sup-0.21.0.gem (100%) Building native extensions. This could take a while... ERROR: Error installing sup: ERROR: Failed to build gem native extension. /usr/local/bin/ruby mkrf_conf_xapian.rb xapian: installing xapian-ruby.. xapian: platform specific dependencies.. Building native extensions. This could take a while... Gem files will remain installed in /usr/local/lib/ruby/gems/2.0.0/gems/sup-0.21.0 for inspection. Results logged to /usr/local/lib/ruby/gems/2.0.0/gems/sup-0.21.0/ext/gem_make.out -- Regards, Peng