Welcome to the most active Linux Forum on the web.
Go Back > Blogs > rainbowsally
User Name


Rate this Entry

64-bit utilities (includes mc2-64 bit)

Posted 05-03-2015 at 06:00 PM by rainbowsally
Updated 05-04-2015 at 02:35 PM by rainbowsally (Uninstaller fixed and uploaded, mc2 build bugs fixed)

We'd better tool up. The old mc2 was for 32-bits. There are a few bugs in it but it should work for those needing 32 bit compilation on a 64 bit machine.

[Note: May 4, Found installer bugs in the mc2 src d/load. Path to panic version of mc2 was added so the stuff could update before being installed and pkg-config string replaces individual includes and libs now. Sorry about that. Should work now.]

But today's amazing journey into Mad Computer Science is...
  • Here is a whole mess of 64-bit utilities (includes mc2-64 bit):
  • kdevelop-3-64bit.tar.gz
    Outstanding experimenter's IDE lost since KDE3. This is from SuSE 10.0. Installs into /opt/kde3 with only a launcher in /usr/bin named kdevelop3. Works! if you have qt3 support installed.
  • kdbg-with-mng.tar.gz
    Fixes broken kdbg. (Symptoms -> MHDR errors and crash)
  • libLQ-mc2-qt-64bit-3.2.0-dyn-bin.tar.gz
    mc2 with qt support, binary SANDBOX installation. (Into ~/usr/*)
  • libLQ-mc2-qt-64bit-3.2.0-src.tar.gz
    Same as above, but better IF it compiles and installs (from ~/usr/src/...)
    [Path bug and pkg-config fixed, May 4, 2015]
  • new-make-installer-1.0.24.tar.gz
    The make based installer used by all the above.
  • runc-rs-1.3.tar.gz
    Runs C/C++ code as though it were a script. Sometimes bash just doesn't quite cut it. Has simple pipes and files functions similar to bash. Check out the test files for a few usage examples. (It can be configured for a 32 bit build if you can't do 64 yet.)

Here's the link.

But runc is a new addition and may not show in the index if you've hit the link before, due to your browser cache holding the older index still. So here's runc.

Hint: If you want kdbg to run inside the IDE, add an external tool named kdbg that runs kdbg.exec in the current folder. The link to the app will not last through an editing cycle but you can force it to be persistent and point to $PWD by editing

Under [External Tools] add or make sure we have
Tool Menu=kdbg

And under [Tool Menu kdbg] change the path to $PWD so it's always relative to where you're working.

kdbg.exec is an executable script containing the following.
CURDIR=`dirname "$0"`
cd "$CURDIR"
kdbg $current
And kdbg.current is a text file containing the name of the app you want to debug.

The following command...
mc2 -create ide <appname>
will generate kdbg.exec and kdbg.current as well as a launcher for kdevelop3 and a clickable backup utility so you can save your files in case you need to revert from some extraordinarily Mad Computer Science.

Note: These kdevelop3 and mc2 doo-dads are all relative addressed so you can move the entire folder anywhere and it will still find the files and compile without getting confused about which "project" it's supposed to be working on. Isn't progress wonderful? But wait... This is ancient technology!

-The Computer Mad Science Team

Posted in Uncategorized
Views 1239 Comments 0
« Prev     Main     Next »
Total Comments 0




All times are GMT -5. The time now is 08:45 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration