Closed bishopmatthew closed 9 years ago
Is this on raspbian? do you have the build-essential package installed?
Yes, and yes.
dpkg -s build-essential
Package: build-essential
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 36
Maintainer: Matthias Klose <doko@debian.org>
Architecture: armhf
Source: build-essential (11.5)
Version: 11.5+b1
Depends: libc6-dev | libc-dev, gcc (>= 4:4.4.3), g++ (>= 4:4.4.3), make, dpkg-dev (>= 1.13.5)
Description: Informational list of build-essential packages
If you do not plan to build Debian packages, you don't need this
package. Starting with dpkg (>= 1.14.18) this package is required
for building Debian packages.
.
This package contains an informational list of packages which are
considered essential for building Debian packages. This package also
depends on the packages on that list, to make it easy to have the
build-essential packages installed.
.
If you have this package installed, you only need to install whatever
a package specifies as its build-time dependencies to build the
package. Conversely, if you are determining what your package needs
to build-depend on, you can always leave out the packages this
package depends on.
.
This package is NOT the definition of what packages are
build-essential; the real definition is in the Debian Policy Manual.
This package contains merely an informational list, which is all
most people need. However, if this package and the manual disagree,
the manual is correct.
Yeah, figured but wanted to check. I think the message is clearer if it's missing.
I'm using the same distro and kernel version, but with node v0.10.
On Thu, Feb 19, 2015 at 6:57 PM, Matthew Bishop notifications@github.com wrote:
Yes, and yes.
dpkg -s build-essential
Package: build-essential Status: install ok installed Priority: optional Section: devel Installed-Size: 36 Maintainer: Matthias Klose <doko@debian.org> Architecture: armhf Source: build-essential (11.5) Version: 11.5+b1 Depends: libc6-dev | libc-dev, gcc (>= 4:4.4.3), g++ (>= 4:4.4.3), make, dpkg-dev (>= 1.13.5) Description: Informational list of build-essential packages If you do not plan to build Debian packages, you don't need this package. Starting with dpkg (>= 1.14.18) this package is required for building Debian packages. . This package contains an informational list of packages which are considered essential for building Debian packages. This package also depends on the packages on that list, to make it easy to have the build-essential packages installed. . If you have this package installed, you only need to install whatever a package specifies as its build-time dependencies to build the package. Conversely, if you are determining what your package needs to build-depend on, you can always leave out the packages this package depends on. . This package is NOT the definition of what packages are build-essential; the real definition is in the Debian Policy Manual. This package contains merely an informational list, which is all most people need. However, if this package and the manual disagree, the manual is correct.
Reply to this email directly or view it on GitHub: https://github.com/kelly/node-i2c/issues/54#issuecomment-75171360
Ok, downgrading worked. Thanks!
Cool! Tho, an issue for v0.12 compatibility that someone can close via a PR isn't a bad idea to have around.
0.12 is now supported in the current release thanks to @emersion
This seems like a house of cards, I'm trying to use the latest tools, node 7.8.0; but I'd have to go back to version 0.12 to install a package that essentially doesn't seem to be supported any more. I understand that if I want it, I could upgrade the package; but the whole idea of using open-source shared components is that if they are published, they should work. I've wasted many hours with install errors and dependencies that are out-of-date or no longerexist. It's very frustrating. I shouldn't have to downgrade to years-old versions to install a package only to upgrade back to the latest package of node. How do I know what those old dependencies are and if the code even works any more.
@billtrudell dependency management is one of the hardest problems to solve, but it's not really related to this module or this thread.
Any idea what's going wrong?
npm install i2c
contents of npm-debug.log