I just created an kubuntu 64-bit session on my VMware setup, Iinstalled SimpleIDE-0-9-47, and the results:I
Installing ./simpleide as ray
Found /opt/parallax/bin
On first run ./simpleide will install ~/Documents/SimpleIDE .
Remove ~/Documents/SimpleIDE to get a new copy of the workspace.
Previous users should remove ~/.config/ParallaxInc/SimpleIDE.conf .
Setup complete. To run program use: ./simpleide
ray@ubuntu:~/Downloads/SimpleIDE-0-9-47$ ./simpleide
ray@ubuntu:~/Downloads/SimpleIDE-0-9-47$ Cannot mix incompatible Qt library (version 0x40804) with this library (version 0x40802)
Aborted (core dumped)
Kubuntu 64-bit does not like too run very well in a VMware session, especially when you are trying too run Firefox at the same time you trying to do other things. More on this later.
Here we learn installing libpng-compat might help:
$ yum install libpng-compat
Kbuntu: Again, back to Google. Sure enough a ton of people have had that problem as well...
Hey but wait, SimpleIDE only needs the libQtGui and libQtGui both of which are in the package. And the simpleide shell script should take care of finding them in the bin directory.
Wow, what a horrible VMware session I just had with the kubuntu 64-bit install. Either VMware does not like 64-bit installations, or kubuntu 64-bit needs a whole lot of resources to run, or a combination of both. To end the VMware session, I just had running, I had to power down the computer to get VMware to release the kubuntu 64-bit session it was running.
I think I need to make a choice of a Linux system, looks like Debian should be the system of choice, and give up on the other versions of Linux, as far as running Propeller related software is concerned. I guess I will just stick with a Debian box, and let someone else test out Fedora, all variations of Ubuntu, and openSUSE, and the other endless list of Linux installs.
So, Debian is the only REAL Linux system, for now.
Wow, what a horrible VMware session I just had with the kubuntu 64-bit install. Either VMware does not like 64-bit installations, or kubuntu 64-bit needs a whole lot of resources to run, or a combination of both. To end the VMware session, I just had running, I had to power down the computer to get VMware to release the kubuntu 64-bit session it was running.
I think I need to make a choice of a Linux system, looks like Debian should be the system of choice, and give up on the other versions of Linux, as far as running Propeller related software is concerned. I guess I will just stick with a Debian box, and let someone else test out Fedora, all variations of Ubuntu, and openSUSE, and the other endless list of Linux installs.
So, Debian is the only REAL Linux system, for now.
Ray
Not that I have any interest in Kubuntu, but your tales of misery make me want to try it running under Parallels on my Mac. I'll grab an image and see how it works for me.
Doubtful... As you've seen, VMWare runs Debian 64-bit versions without issue. Did you install VMWare Tools? Did you try different VMWare settings? Did you check-in on the VMWare forums to see if others have run Kubuntu 64-bit and had similar problems? As others have noted, Google can help you find solutions pretty quickly.
So, Debian is the only REAL Linux system, for now.
Careful there, some would say that Slackware is still the "original and best":)
Debian is close enough for me.
You might be interested in some notes I made on how I set up Debian starting from a small netinst CD: http://the.linuxd.org/debian-installation-log/ I like to have KDE rather than that awful GNOME desktop.
Careful there, some would say that Slackware is still the "original and best"
Forgot about that one, I think I will run that with VMware, just too get a sense of what that one is all about. Maybe I will change my mind after the VMware session, and then I will start touting Slackware. All in all, their are just too many Linux versions ...
For Debian, Ubuntu, Kubuntu (presumably), and other .deb (APT)-based package systems, you won't need to resort to Google to find which package you need to install to get e.g. libpng12. Just do 'apt-cache search libpng12' from the command line (or from any of the Gui wrappers if you prefer). Or, if that doesn't work, use 'apt-file': apt-get install apt-file; apt-file update; apt-file search name-of-file
I just did a re-install of a Debian KDE box, which will be my final solution. I also just installed SimpleIDE-0-9-47, and I noticed something weird, when the hello program comes up and I run it, nothing shows up on the terminal screen. But when I change the print("Hello") to printf("hello"), then it shows on the terminal screen. Did my simpletools.h get messed up? Is anybody else seeing this?
I just re installed SimpleIDE-0-9-47, and I am still getting the same problem, print() is not functioning. But strange enough the pause() works, so it seems that simpletools.h is all right, just print() is not working. Hopefully somebody with a Debian 64 will try it out and see if they get the same results. This occurs in a newly created project, and the Welcome session.
We haven't had a chance to run a program of testing on the default branch yet, so I'm not sure if we should be "distributing" it. That said, I doubt that has anything to do with Ray's simple library problem.
The first run of simpleide is supposed create a directory "SimpleIDE" in ~/Documents. Or at least that's what it says in the INSTALL.txt and it's what it does if I have a ~/Documents directory.
However my machine does not have a ~/Documents directory and neither do I want one. So this sequence:
$ tar -xjvf SimpleIDE-0-9-47.x86_64.debian-linux.tar.bz2
$ cd SimpleIDE-0-9-47/
$ ./setup.sh heater
$ ./simpleide
silently fails to create that ~/Documents/SimplIDE directory.
What does it actually do?
It creates ~/SimpleIDE instead. And when you look in the Properties dialog that is where it looks for the "Workspace Folder".
Heater, Not sure about that clear folder stuff. It would be great if you can help understand it though. Did you remove the ~/.config/ParallaxInc properties folder before running the program? The "Clear Settings" button does the same thing.
Yep, been doing a lot of removing of ~/.config/ParallaxInc, ~/SimpleIDE and /opt/parallax just now.
Can't get external RAM to work on my Gadget Gangster board any more:
Loading the serial helper to hub memory9808 bytes sent
Verifying RAM ...
OKLoading external memory driver 'sqi_sram_xmem.dat'
1008 bytes sent
Loading program image to RAM
20564 bytes sent
Loading .xmmkernel
1984 bytes sent
I don't know. I just deleted everything and installed again.
Again the board type was empty.
This time I just opened the properties and hit OK, then all was well.
Now what is the board type for the Gadget Gangster SDRAM board again? Didn't we used to have something that said SDRAM?
I don't know. I just deleted everything and installed again.
Again the board type was empty.
This time I just opened the properties and hit OK, then all was well.
Now what is the board type for the Gadget Gangster SDRAM board again? Didn't we used to have something that said SDRAM?
The default branch does things differently, and that driver hasn't been ported yet.
Try "SimpleIDE Linux"
You might get off into the same weeds I did. I do try to contextualize searches as much as possible. . . not sure what Google is up to.
Using Forth has gotten me up to speed on using PASM as Dave Hein's pfth is very clear. So GCC keeps ending up on the backburner in my tiny world.
Comments
Odd, typing "SimpleIDE" into Google gets me directly to the right page as the first hit. http://learn.parallax.com/propeller-c-set-simpleide
Perhaps Google know me too well.
Ray
Your obvious next step is Google "libpng12 fedora"
That immediately gets you to others who have had this problem already. For example:
http://developer.appcelerator.com/question/137812/fedora-17-64bit-libpng12
Here we learn installing libpng-compat might help:
Kbuntu: Again, back to Google. Sure enough a ton of people have had that problem as well...
Hey but wait, SimpleIDE only needs the libQtGui and libQtGui both of which are in the package. And the simpleide shell script should take care of finding them in the bin directory.
I think I need to make a choice of a Linux system, looks like Debian should be the system of choice, and give up on the other versions of Linux, as far as running Propeller related software is concerned. I guess I will just stick with a Debian box, and let someone else test out Fedora, all variations of Ubuntu, and openSUSE, and the other endless list of Linux installs.
So, Debian is the only REAL Linux system, for now.
Ray
Not that I have any interest in Kubuntu, but your tales of misery make me want to try it running under Parallels on my Mac. I'll grab an image and see how it works for me.
Doubtful... As you've seen, VMWare runs Debian 64-bit versions without issue. Did you install VMWare Tools? Did you try different VMWare settings? Did you check-in on the VMWare forums to see if others have run Kubuntu 64-bit and had similar problems? As others have noted, Google can help you find solutions pretty quickly.
dgately
Careful there, some would say that Slackware is still the "original and best":)
Debian is close enough for me.
You might be interested in some notes I made on how I set up Debian starting from a small netinst CD: http://the.linuxd.org/debian-installation-log/
I like to have KDE rather than that awful GNOME desktop.
Ray
... and Linux people complain about Forths??? Sheeeesh!!!
You can run a forth on Linux, but you can't run Linux on a forth. You might be able to run it on a fifth though
You might consider it after a fifth!
-Tor
Ray
Probably. I would honestly expect the opposite to happen though.
Ray
Where does the SimpleIDE workspace come from in your 0-9-47 distribution?
Which PropellerGCC version do you build?
Thanks.
Workspace is the thing I get prompted to fetch with hg somewhere along the line. What happens to it next I have no idea.
I'll have to check the details when I get back to my PC later today.
propgcc in that packager was a very recent pull of the default branch: propside also a recent pull of the spinside branch: The Works space is the default (only) branch:
Does that say anything? What is the issue here?
We haven't had a chance to run a program of testing on the default branch yet, so I'm not sure if we should be "distributing" it. That said, I doubt that has anything to do with Ray's simple library problem.
The other "tips" look fine to me.
I'll test that package when I have time.
The first run of simpleide is supposed create a directory "SimpleIDE" in ~/Documents. Or at least that's what it says in the INSTALL.txt and it's what it does if I have a ~/Documents directory.
However my machine does not have a ~/Documents directory and neither do I want one. So this sequence:
$ tar -xjvf SimpleIDE-0-9-47.x86_64.debian-linux.tar.bz2
$ cd SimpleIDE-0-9-47/
$ ./setup.sh heater
$ ./simpleide
silently fails to create that ~/Documents/SimplIDE directory.
What does it actually do?
It creates ~/SimpleIDE instead. And when you look in the Properties dialog that is where it looks for the "Workspace Folder".
Ah, so Ray is now on the testing team. Excellent:)
If only I had a Propeller around here to test against.
Ray
I don't have any board types in the "Board Type" drop down box. Can't program anything without a board type.
I have a "/opt/parallax/propeller-load" directory full of nice .cfg and .dat files.
And that is where SimpleIDE says it is looking in the properties dialog.
If I clear the "Loader Folder" setting and save that. Then go back in there and set the same thing back again it works!
So, I now have Welcome.c running. The "print" works. No "printf" required.
Heater, Not sure about that clear folder stuff. It would be great if you can help understand it though. Did you remove the ~/.config/ParallaxInc properties folder before running the program? The "Clear Settings" button does the same thing.
Can't get external RAM to work on my Gadget Gangster board any more: Used to work ages ago.
Again the board type was empty.
This time I just opened the properties and hit OK, then all was well.
Now what is the board type for the Gadget Gangster SDRAM board again? Didn't we used to have something that said SDRAM?
Ah, OK. Propgcc release branch build now under way.
Try "SimpleIDE Linux"
You might get off into the same weeds I did. I do try to contextualize searches as much as possible. . . not sure what Google is up to.
Using Forth has gotten me up to speed on using PASM as Dave Hein's pfth is very clear. So GCC keeps ending up on the backburner in my tiny world.