[arch-dev-public] subversion rebuild needed for i686
Re: http://bugs.archlinux.org/task/14832 Could someone please rebuild subversion for i686? Something fishy with Berkeley DB on my standard system prevented building one library, and building in a clean chroot resulted in a java-related error. So I did the best I could, but I have failed miserably :( F
On Sat, 2009-05-30 at 11:39 +0200, Firmicus wrote:
Re: http://bugs.archlinux.org/task/14832
Could someone please rebuild subversion for i686?
Something fishy with Berkeley DB on my standard system prevented building one library, and building in a clean chroot resulted in a java-related error.
So I did the best I could, but I have failed miserably :(
F
The java error, was it something with TimeZone in it? You will need to link/copy the correct timezone file to /etc/localtime, otherwise several java applications won't work (Java will crash).
Jan de Groot a écrit :
On Sat, 2009-05-30 at 11:39 +0200, Firmicus wrote:
Re: http://bugs.archlinux.org/task/14832
Could someone please rebuild subversion for i686?
Something fishy with Berkeley DB on my standard system prevented building one library, and building in a clean chroot resulted in a java-related error.
So I did the best I could, but I have failed miserably :(
F
The java error, was it something with TimeZone in it? You will need to link/copy the correct timezone file to /etc/localtime, otherwise several java applications won't work (Java will crash).
Apparently not. The error message was: /usr/lib/jvm/java-1.6.0-openjdk/bin/javac: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory make: *** [subversion/bindings/javahl/classes/org/tigris/subversion/javahl/BlameCallback2.class] Error 127 But latest openjkd6 from extra is installed and libjli.so is where it should be. F
Firmicus a écrit :
Re: http://bugs.archlinux.org/task/14832
Could someone please rebuild subversion for i686?
Something fishy with Berkeley DB on my standard system prevented building one library, and building in a clean chroot resulted in a java-related error.
So I did the best I could, but I have failed miserably :(
F
Succeeded now. (Thanks in good part to Gerardo who made me realize that the javac binary was unable to find libjli.so, even though it was where it should be. Symlinking to /usr/lib solved the problem. So this was some LIBPATH problem in my supposedly pristine chroot.) But ... I have again forgotten to run extrapkg with a meaningful message as argument :( Sorry. For the record: this closes FS#14832, which was specific to the i686 package. No need to rebuild for x86_64. Stupid(?) question: Why is subversion still orphaned?! F
2009/5/30, Firmicus <Firmicus@gmx.net>:
Stupid(?) question: Why is subversion still orphaned?!
That's a Douglas Soares de Andrade's packages. Douglas, please adopt it again. -- Arch Linux Developer http://www.archlinux.org
Em Sábado 30 Maio 2009, às 21:02:26, Giovanni Scafora escreveu:
2009/5/30, Firmicus <Firmicus@gmx.net>:
Stupid(?) question: Why is subversion still orphaned?!
That's a Douglas Soares de Andrade's packages. Douglas, please adopt it again.
Hum, strange thing it was adopted. Anyway, i not using subversion anymore, so do anyone wishes to maintain it ? If anyone wants i can still maintain it. Thanks
On Sun, 2009-05-31 at 08:32 -0300, Douglas Soares de Andrade wrote:
Em Sábado 30 Maio 2009, às 21:02:26, Giovanni Scafora escreveu:
2009/5/30, Firmicus <Firmicus@gmx.net>:
Stupid(?) question: Why is subversion still orphaned?!
That's a Douglas Soares de Andrade's packages. Douglas, please adopt it again.
Hum, strange thing it was adopted. Anyway, i not using subversion anymore, so do anyone wishes to maintain it ?
If anyone wants i can still maintain it.
Not using subversion anymore? How do you submit packages then, using telnet or something? :P
Em Domingo 31 Maio 2009, às 08:46:56, Jan de Groot escreveu:
On Sun, 2009-05-31 at 08:32 -0300, Douglas Soares de Andrade wrote:
Em Sábado 30 Maio 2009, às 21:02:26, Giovanni Scafora escreveu:
2009/5/30, Firmicus <Firmicus@gmx.net>:
Stupid(?) question: Why is subversion still orphaned?!
That's a Douglas Soares de Andrade's packages. Douglas, please adopt it again.
Hum, strange thing it was adopted. Anyway, i not using subversion anymore, so do anyone wishes to maintain it ?
If anyone wants i can still maintain it.
Not using subversion anymore? How do you submit packages then, using telnet or something? :P
Ah, sure hehehehehehe Well, in this sense it is extrapkg who uses it, not me hehehehehehe
2009/5/31, Jan de Groot <jan@jgc.homeip.net>:
Not using subversion anymore? How do you submit packages then, using telnet or something? :P
Ahahahahahahahah. Awesome. :-) -- Arch Linux Developer http://www.archlinux.org
Succeeded now. (Thanks in good part to Gerardo who made me realize that the javac binary was unable to find libjli.so, even though it was where it should be. Symlinking to /usr/lib solved the problem. So this was some LIBPATH problem in my supposedly pristine chroot.)
Dammit!!! My new package happens to have the same GD problem Douglas originally had: see FS#14738 Folks, I am no longer sure to understand the subtleties of "building in a clean chroot" ... Now that I know that this package belongs to Douglas, I'll happily let him deal with it ;D On the other hand, I'd be grateful to be a bit more enlightened about all this. Has anyone experienced any similar issues whilst building packages in a chroot? F
Firmicus wrote:
Succeeded now. (Thanks in good part to Gerardo who made me realize that the javac binary was unable to find libjli.so, even though it was where it should be. Symlinking to /usr/lib solved the problem. So this was some LIBPATH problem in my supposedly pristine chroot.)
Dammit!!! My new package happens to have the same GD problem Douglas originally had: see FS#14738
Folks, I am no longer sure to understand the subtleties of "building in a clean chroot" ...
Now that I know that this package belongs to Douglas, I'll happily let him deal with it ;D
On the other hand, I'd be grateful to be a bit more enlightened about all this. Has anyone experienced any similar issues whilst building packages in a chroot?
My guess on all these issues is that there are makedepends (which are probably also optdepends) missing so various component are not being built on a clean system. Allan
Em Domingo 31 Maio 2009, às 09:37:27, Firmicus escreveu:
Succeeded now. (Thanks in good part to Gerardo who made me realize that the javac binary was unable to find libjli.so, even though it was where it should be. Symlinking to /usr/lib solved the problem. So this was some LIBPATH problem in my supposedly pristine chroot.)
Dammit!!! My new package happens to have the same GD problem Douglas originally had: see FS#14738
Folks, I am no longer sure to understand the subtleties of "building in a clean chroot" ...
Now that I know that this package belongs to Douglas, I'll happily let him deal with it ;D
On the other hand, I'd be grateful to be a bit more enlightened about all this. Has anyone experienced any similar issues whilst building packages in a chroot?
Me too, till then i will build packages in my working enviroment, i really did not understood why the package buillt in the chroot had problems, any ideas ? Thanks
Douglas Soares de Andrade wrote:
Em Domingo 31 Maio 2009, às 09:37:27, Firmicus escreveu:
Succeeded now. (Thanks in good part to Gerardo who made me realize that the javac binary was unable to find libjli.so, even though it was where it should be. Symlinking to /usr/lib solved the problem. So this was some LIBPATH problem in my supposedly pristine chroot.)
Dammit!!! My new package happens to have the same GD problem Douglas originally had: see FS#14738
Folks, I am no longer sure to understand the subtleties of "building in a clean chroot" ...
Now that I know that this package belongs to Douglas, I'll happily let him deal with it ;D
On the other hand, I'd be grateful to be a bit more enlightened about all this. Has anyone experienced any similar issues whilst building packages in a chroot?
Me too, till then i will build packages in my working enviroment, i really did not understood why the package buillt in the chroot had problems, any ideas ?
As I replied earlier, missing makedeps is the most likely answer. Compare what the configure output gives you when running in the clean chroot and your system. Allan
participants (5)
-
Allan McRae
-
Douglas Soares de Andrade
-
Firmicus
-
Giovanni Scafora
-
Jan de Groot