ArchThis Forum is for the discussion of Arch Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Never ever used Arch before, but have got myself a Raspberry Pi and needed a cut down OS to run on it. I've been installing packages on it without difficulty until I get to this part where I'm trying to install a library:
Code:
pacman -S libi2c-dev
which for some reason generates a 'target not found' error.
I've tried
Yes - as it tells you, the package doesn't exist. (why did you think it did?
Thank you, Snark.
This page: https://projects.drogon.net/raspberr...i/i2c-library/ is supposed to be current and that's why I assumed the package to be available. Being totally unfamiliar with pacman, I thought perhaps I might have expected it to do something with libraries that it did not in fact do. Sorry for the crap explanation, but you get my drift (hopefully!)
Ah, I see - they are using the Ubuntu repositories (they use the command 'apt-get'). In general, it's the distro's job to name and add packages - so the same package might have different names using different package managers (apt-get, yum, pacman, etc.) or even not exist at all!
I would try installing i2c-tools, and see if that works the same as in Ubuntu. If not, then you may just have to switch to Ubuntu, or find the source code for whatever library Ubuntu have packaged.
Ah, I see - they are using the Ubuntu repositories (they use the command 'apt-get'). In general, it's the distro's job to name and add packages - so the same package might have different names using different package managers (apt-get, yum, pacman, etc.) or even not exist at all!
I would try installing i2c-tools, and see if that works the same as in Ubuntu. If not, then you may just have to switch to Ubuntu, or find the source code for whatever library Ubuntu have packaged.
Regards,
Oh. I was under the impression that one merely substituted the name of the appropriate packet manager and its associated options when installing software on a different distro. What a blasted nuisance!
Sorry, sadly not. However, you've made a good choice with Arch - I've never before found a package that I wanted that wasn't in either the main repositories or the AUR, and the software they have is much more up-to-date than in Ubuntu (and, dare I say it, stable, despite Arch being a rolling release).
Having said that, look here: http://www.raspberrypi.org/phpBB3/vi...29953&p=262230
It gives you instructions on how to get the git version of the package i2c-tools, which does contain the header you're looking for. However, the package itself has been updated since the discussion in which they said it was out of date, so I would seriously recommend trying to install i2c-tools first and seeing if that solves your problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.