-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alas, the hack I was going to do will not work, and ChucK is out of the picture for me until the ChucK developers are able to make it 64-bit clean. I was planning to build JACK in 64-bit and 32-bit versions and then build ChucK in 32-bit mode and link it against the 32-bit versions of the libraries, and thus have ChucK use 32-bit libraries to converse with the JACK server and all the other 64-bit softsynths and audio applications. But I have been told by one of the JACK developers that this would not work anyway, because you can't have 32-bit and 64-bit apps conversing with the same JACK server. There are pointer-size fixes they could do to enable this, but not too many people clamoring for it, so it's low priority. I'm told that it is possible to run ChucK on a 64-bit Linux system, by turning it into a 32-bit system: one would have to build an entire 32-bit chroot environment, including *all* audio apps, and run *all* the audio apps, and JACK itself, in 32-bit mode. I ain't going there. Cool language, though. I'll revisit it a couple years from now, and see how it's progressed. - -ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGdrrYe8HF+6xeOIcRAgMUAKDI9qhdQt8G/vO3tK/HT2h/7N+JzACeJDMn g9o/sPK5BTMMxoKzqajG/0s= =zA+/ -----END PGP SIGNATURE-----
Ken Restivo wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alas, the hack I was going to do will not work, and ChucK is out of the picture for me until the ChucK developers are able to make it 64-bit clean.
I was planning to build JACK in 64-bit and 32-bit versions and then build ChucK in 32-bit mode and link it against the 32-bit versions of the libraries, and thus have ChucK use 32-bit libraries to converse with the JACK server and all the other 64-bit softsynths and audio applications.
But I have been told by one of the JACK developers that this would not work anyway, because you can't have 32-bit and 64-bit apps conversing with the same JACK server. There are pointer-size fixes they could do to enable this, but not too many people clamoring for it, so it's low priority.
I'm told that it is possible to run ChucK on a 64-bit Linux system, by turning it into a 32-bit system: one would have to build an entire 32-bit chroot environment, including *all* audio apps, and run *all* the audio apps, and JACK itself, in 32-bit mode. I ain't going there.
Cool language, though. I'll revisit it a couple years from now, and see how it's progressed.
- -ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGdrrYe8HF+6xeOIcRAgMUAKDI9qhdQt8G/vO3tK/HT2h/7N+JzACeJDMn g9o/sPK5BTMMxoKzqajG/0s= =zA+/ -----END PGP SIGNATURE----- _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
Hi Ken, just my two cents: Since two years ago, I'm using a 32bit distro (Slackware) for everyday use and for audio works and a 64bit distro in which I boot exclusively when I need to work with those applications that are optimized to work at 64bit and if the performance gain is enough to bother rebooting. c. -- http://www.cesaremarilungo.com
Dear all, Thanks again for the input and sorry for punctuating the spam equilibrium with my barrage of posts! I think with the recent posts, we are definitely narrowing down a list of high priority targets for the next round of development. We'd love to see 64-bit ChucK happen, but don't have a good idea of how soon we can get that done. We will investigate it in the next few weeks and come up with a plan of attack. Thanks again for the continued input on this. Earlier posts on 64- bit can be found here and probably a few other places: https://lists.cs.princeton.edu/pipermail/chuck-users/2007-April/ 001750.html Best, Ge! On Jun 18, 2007, at 1:03 PM, Ken Restivo wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alas, the hack I was going to do will not work, and ChucK is out of the picture for me until the ChucK developers are able to make it 64-bit clean.
I was planning to build JACK in 64-bit and 32-bit versions and then build ChucK in 32-bit mode and link it against the 32-bit versions of the libraries, and thus have ChucK use 32-bit libraries to converse with the JACK server and all the other 64-bit softsynths and audio applications.
But I have been told by one of the JACK developers that this would not work anyway, because you can't have 32-bit and 64-bit apps conversing with the same JACK server. There are pointer-size fixes they could do to enable this, but not too many people clamoring for it, so it's low priority.
I'm told that it is possible to run ChucK on a 64-bit Linux system, by turning it into a 32-bit system: one would have to build an entire 32-bit chroot environment, including *all* audio apps, and run *all* the audio apps, and JACK itself, in 32-bit mode. I ain't going there.
Cool language, though. I'll revisit it a couple years from now, and see how it's progressed.
- -ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGdrrYe8HF+6xeOIcRAgMUAKDI9qhdQt8G/vO3tK/HT2h/7N+JzACeJDMn g9o/sPK5BTMMxoKzqajG/0s= =zA+/ -----END PGP SIGNATURE----- _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
participants (3)
-
Cesare Marilungo -
Ge Wang -
Ken Restivo