Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

Installing Developer on 64-bit Linux


I just tried installing the latest Titanium Developer on a 64-bit RedHat machine. Should I expect this to work?

$ ./Titanium\ Developer 
./Titanium Developer: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by ./Titanium Developer)

Let me know if I can provide more information.


— asked June 2nd 2010 by Tim Schaub
  • 64-bit
  • developer
  • linux
1 Comment
  • And here are my results from a fresh Ubuntu (10.04) 64-bit machine.

    $ ./Titanium\ Developer ./Titanium Developer: symbol lookup error: /usr/lib/libgtk-x11-2.0.so.0: undefined symbol g_malloc_n

    This time I got the initial Developer install dialog and chose to install to my home directory. The install looks to have succeeded (based on the contents of my ~/.titanium directory). When I try to run Developer I get the above error.

    — commented June 2nd 2010 by Tim Schaub

2 Answers

  • Yes, thanks for posting a link to that. I found it earlier and it does indeed solve the problem on Ubuntu 10.04 (and I assume elsewhere with LibGDK 2.0).

    To reiterate (in hopes of making it easier for others to work around this issue), on Ubuntu 10.04 and perhaps everywhere with LibGDK 2.0, to get Titanium Developer to run, you need to remove a number of libraries in the runtime directory.

    rm ~/.titanium/runtime/linux/1.0.0/libgobject-2.0.*
    rm ~/.titanium/runtime/linux/1.0.0/libglib-2.0.*
    rm ~/.titanium/runtime/linux/1.0.0/libgio-2.0.*
    rm ~/.titanium/runtime/linux/1.0.0/libgthread-2.0.*

    This answer is given in a thread on g_malloc_n issues.

    I'll try again on 64-bit RedHat, but I think the original issue I posted about here is different than the LibGDK 2.0 conflict. If I can narrow it down, I'll make the description more specific.

    — answered June 11th 2010 by Tim Schaub
  • This solution work for me


    — answered June 10th 2010 by bunyawat singchai
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.