Received: by 10.236.83.39 with SMTP id p27mr1552331yhe.27.1342622272113;
        Wed, 18 Jul 2012 07:37:52 -0700 (PDT)
X-BeenThere: nodejs@googlegroups.com
Received: by 10.236.42.69 with SMTP id i45ls2975908yhb.3.gmail; Wed, 18 Jul
 2012 07:37:40 -0700 (PDT)
Received: by 10.236.115.137 with SMTP id e9mr1500982yhh.32.1342622260072;
        Wed, 18 Jul 2012 07:37:40 -0700 (PDT)
Received: by 10.236.115.137 with SMTP id e9mr1500981yhh.32.1342622260043;
        Wed, 18 Jul 2012 07:37:40 -0700 (PDT)
Return-Path: <i...@bnoordhuis.nl>
Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.213.181])
        by gmr-mx.google.com with ESMTPS id e37si6215094yhi.1.2012.07.18.07.37.39
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 18 Jul 2012 07:37:39 -0700 (PDT)
Received-SPF: pass (google.com: domain of i...@bnoordhuis.nl designates 209.85.213.181 as permitted sender) client-ip=209.85.213.181;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of i...@bnoordhuis.nl designates 209.85.213.181 as permitted sender) smtp.mail=i...@bnoordhuis.nl
Received: by mail-yx0-f181.google.com with SMTP id l3so1979990yen.26
        for <nodejs@googlegroups.com>; Wed, 18 Jul 2012 07:37:39 -0700 (PDT)
        d=google.com; s=20120113;
        h=mime-version:x-originating-ip:in-reply-to:references:date
         :message-id:subject:from:to:content-type:x-gm-message-state;
        bh=s82/Eu/iE51UQUSydNvfoEq85rEXjoQT63F5hqcuMOk=;
        b=ABnI3sB6zYKlED/PICz60u1T0u9HWE3fcDWE2coFTUUI+b0Nx0+bZTgVR3XdX7zx6K
         a67aq7sGEgvj6E8w3C4soH8ojsDx1ySnkIaqO39g0VCvr0sv53Pf5nB5T45OlRh/eqD+
         wtFye3xhjiw8GkDKSEZ90qwdUxqKh+84MpcS6KfRLaA6F9/2+XoG1pLo6rqL8EbtZSRa
         Yky467WXSkV/uANfrY/foPfK3Li14OONp/MToN/dUIOcjFgc3ah+Soy6A699wCgJIC+3
         3D9fnHqHZwLq0GP5hNDsBpGw2Oq8mDHuS6Udkmff3b4ubB0tL0WrnLHuGcCo1aR0nEdS
         b1nw==
MIME-Version: 1.0
Received: by 10.68.131.41 with SMTP id oj9mr8590284pbb.130.1342622259615; Wed,
 18 Jul 2012 07:37:39 -0700 (PDT)
Received: by 10.68.226.103 with HTTP; Wed, 18 Jul 2012 07:37:39 -0700 (PDT)
X-Originating-IP: [87.214.96.125]
In-Reply-To: <c5998c7c-90fe-44fa-a51a-308b4f2f0...@f8g2000pbf.googlegroups.com>
References: <50b2446a-0cd0-4649-b609-c2b6deac9...@t1g2000pbl.googlegroups.com>
	<17bfc8cc-1d4f-457b-bb27-ecebcca0d1ea@googlegroups.com>
	<5ef3aec6-3d18-4de8-beb3-38ab8de44...@t1g2000pbl.googlegroups.com>
	<CAHQurc_qxYVEffmR8nK1DRoP0b5OVcBRif1fmrSmLzMa-cr...@mail.gmail.com>
	<7427867f-ab9b-4324-9bb6-800b545c1...@l6g2000pbi.googlegroups.com>
	<CAHQurc8qp=cRV_ezu+2wdDh_1OYtR0YatzJ1A29zaWysi+i...@mail.gmail.com>
	<c5998c7c-90fe-44fa-a51a-308b4f2f0...@f8g2000pbf.googlegroups.com>
Date: Wed, 18 Jul 2012 16:37:39 +0200
Message-ID: <CAHQurc_Kguq8fd_5rwno2Y6kJCL8qbqyvPi0vNFAu6zOcPH...@mail.gmail.com>
Subject: Re: [nodejs] Re: installing libxmljs in centos 5.x
From: Ben Noordhuis <i...@bnoordhuis.nl>
To: nodejs@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQk7oZ1HGGa+BlE/6es5JUsG0GdyroM1pv69xiaeCHinEyf/B2IJOKGS0EdoX3XRBEkJeNzN

On Wed, Jul 18, 2012 at 3:31 PM, Angelo Chen <angelochen...@gmail.com> wrote:
> I did and built it, i got v0.8.3-pre.
> the compile error with libxmljs go away, but still get errors:
>
> 151 info postuninstall libxm...@0.5.4
> 152 error libxm...@0.5.4 install: `node-waf configure build`
> 152 error `sh "-c" "node-waf configure build"` failed with 1
> 153 error Failed at the libxm...@0.5.4 install script.
>
> so i tried to compile it from source,  node-gyp configure, I got
> following:
>
> gyp info it worked if it ends with ok
> gyp info using node-...@0.6.0
> gyp info using n...@0.8.3-pre | linux | ia32
> gyp ERR! configure error
> gyp ERR! stack Error: "pre" versions of node cannot be installed, use
> the --nodedir flag instead
> gyp ERR! stack     at install (/usr/local/lib/node_modules/node-gyp/
> lib/install.js:68:16)
> gyp ERR! stack     at Object.commands.forEach.self.commands.(anonymous
> function) [as install] (/usr/local/lib/node_modules/node-gyp/lib/node-
> gyp.js:56:37)
> gyp ERR! stack     at getNodeDir (/usr/local/lib/node_modules/node-gyp/
> lib/configure.js:147:20)
> gyp ERR! stack     at /usr/local/lib/node_modules/node-gyp/lib/
> configure.js:87:9
> gyp ERR! stack     at ChildProcess.exithandler (child_process.js:
> 534:7)
> gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:91:17)
> gyp ERR! stack     at maybeClose (child_process.js:634:16)
> gyp ERR! stack     at Socket.ChildProcess.spawn.stdin
> (child_process.js:805:11)
> gyp ERR! stack     at Socket.EventEmitter.emit (events.js:88:17)
> gyp ERR! stack     at Socket._destroy.destroyed (net.js:358:10)
> gyp ERR! System Linux 2.6.18-128.1.10.el5.xs5.5.0.51xen
> gyp ERR! command "node" "/usr/local/bin/node-gyp" "configure"
> gyp ERR! cwd /home/info/libxmljs
> gyp ERR! node -v v0.8.3-pre
> gyp ERR! node-gyp -v v0.6.0
> gyp ERR! not ok

That's a feature (as it were) of node-gyp.

Normally, you'd point it to the proper version with --target 0.8.2 but
that won't work here because the change hasn't landed in a release
yet.