I got the PKGBUILD for Núcleo's AUR package:
Code:
# Contributor: Tomasz Binasiewicz <tomasz.binasiewicz@gmail.com> |
Googling .. Núcleo libpng14 ..
> > > about three hits. Guess, nobody else ever tried to compile Nucleo with libpng14. ..... |
I wonder if there is a precompiled 64-bit Núcleo binary somewhere.
|
Why don't you write a 'libpng12.pc' yourself ?
We are in the extreme simple and basic department here. It's a ten liner text file. Editing a copy of your libpng14.pc is also easy : Edit and rename to libpng12.pc . Here comes a libpng12.pc example .. Code:
prefix=/usr system, and mail it to you. The "nucleo-result-0.7.6.tar.bz2" is 2.5 MB. But no guaranty, it works. Versions of ffmpeg, etc. are critical. ..... |
I would have never suspected that it's a text file, I thought it was an exe.
And I should use /usr/lib, not /usr/lib64 on my 64-bit system, right? Anyway, I will create the file, make an Arch pacgake from it called "libpng12pc", and install it. |
I made the package, but I must have done something wrong, because this happens:
Code:
$ pacman -Qs libpng |
I'm a bit ate here, but I did find a rpm in 64-bit with a nice clear list of dependencies;
http://www.rpmfind.net/linux/RPM/man....0.x86_64.html Then you can pick any of the nice tools in the AUR; http://aur.archlinux.org/packages.ph...m&do_Search=Go Or perhaps one of these; Quote:
Or the DEB. http://yaro.gdi.pl/deb/edgy/metisse_...rc4-1_i386.deb Arch64 FAQ; http://wiki.archlinux.org/index.php/Arch64_FAQ Hope this helps you. |
1 Attachment(s)
Here's what I need to do:
EDIT: I attached a newer version of the .pkg.tar.gz file I made, I don't know if this one will confuse pacman the way the other one did. Please remove the ".txt" at the end before using. (And this is just for you to look inside and extract it, install it at your own risk (it might do what happened in post #36)!) |
I got to get to school so i can't be as nice as I want to be, but;
http://www.google.com/search?hl=en&q...ed=0CCAQrQIwBA There has to be some useful info somewhere in all those Arch forum threads |
Post # 36.
An entry in //pkgconfig/ must have suffix .pc to work. The idea is to create : libpng12.pc And then make a link by name : libpng.pc I.e. : # ln -s libpng12.pc libpng.pc P.S. : The attached file in post # 38 looks OK. ..... |
So I can just have libpng12.pc in my home dir and link libpng.so to it, and then link it back to libpng14.so when Núcleo and Metisse are compiled?
Still, I want to uninstall the faulty package I made. Every time I use pacman for whatever reason is shows the message I highlighted in bold: Code:
[michael:~]$ pacman -Qs bash Note that the package I made that did this is not the one attached to post #36. The one attached to post #36 is a revised version that I thought will work. |
Try;
Quote:
What error does it produce? |
Code:
[root:michael]# pacman -R libpng12pc |
Have a look in /var/lib/pacman/
It is safe to delete everything but local, since those get regenerated after a pacman -Syy. Don't delete local. Instead, refresh your DB and attempt to remove it once more. If this fails, look in local for packagename and delete it out of there. Don't delete local! (if applicable, I'm on a school PC, so I can't test it out on my netbook :() http://bbs.archlinux.org/viewtopic.php?id=34494 Data above proven here: http://bbs.archlinux.org/viewtopic.php?id=62968 Other important pacman files to look in: Code:
Conf File : /etc/pacman.conf http://wiki.archlinux.org/index.php/Pacman Hope this helps. (And don't delete local!! Just the bad entry!! :p) {Remember the IgnorePkg possibility too.} {Have you seen this link yet: http://bbs.archlinux.org/viewtopic.php?id=46084 ?} |
I deleted the directory /var/lib/pacman/local/libpng12pc-1.2.40 and pacman works fine now.
I ran pacman -Syy and pacman -Sc afterwards. Now back to the original topic... |
All times are GMT -5. The time now is 01:43 AM. |