Forum: Blackrhino - Help forum for the Blackrhino Linux distro for the PS2. No warez allowed!


The above video goes away if you are a member and logged in, so log in now!




 
Would you like to get all the new info from
PSX-Scene in your email each day?




Want to learn more about the team keeping you up to date with the latest scene news?

Read about them now!

Check out our Developer bios, too!

 


User Tag List

Thread: Problems Compiling Glib-2.0
  

Results 1 to 7 of 7
  1. #1 Problems Compiling Glib-2.0 
    Isles487 is offline Member
    Join Date
    Apr 2010
    Posts
    21
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    Hey everyone,

    No matter what version of GLib-2.0 I try to compile, I get the message
    "parse error in VERSION script."
    I've attached a text file because if I post here it says I can't post links.
    error.txt
    Deba5er, your version seems to install fine, but I'm not sure that it's ok.... because I get all sorts of messages about "invalid string offset" from ld while installing, and I get the same messages while compiling Pango. Does anyone know what I can do?
    Reply With Quote  

  2. #2  
    deba5er's Avatar
    deba5er is online now Moderator
    Join Date
    Jan 2006
    Posts
    593
    Downloads
    0
    Uploads
    0
    Mentioned
    2 Post(s)
    Tagged
    1 Thread(s)
    Likes Given
    6
    Likes Received
    8
    supports_anon_versioning=no is what most "configure" scripts should come up with. Unfortunately some idiot (just my opinion, no flames) decided to have "/usr/bin/ld --version" report "GNU ld 2.9-ee-990721". Doesn't look like any expected version number that a normal configure would look for so when it looks for the x.y.z format it sees x.y-z and miscalculates the value for supports_anon_versioning (and sets it to yes). So you could fix any configure which does such a check or you could take the easy route like I did and su to root, then "vi /usr/bin/ld", Type exactly "/2.9-ee" and then press <enter>. Press <n> to find the second instance, and you will see a line that has "2.9-ee-990721" and a bunch of ^@ characters and also "GNU ld version". Move the cursor over the "-" after 2.9 and press <r>, then press <.>. Press capital Z twice to save.

    Now when you enter "/usr/bin/ld --version" it reports "GNU ld 2.9.ee-990721". Still ugly looking but will work with most configure files. Yes this is a crappy fix, but seems to me that the original 2.9-ee versioning text was a pretty out-there choice anyway, so a hackish fix to a hackish version of ld seems appropriate. Good luck - glad to see some compiling going on for PS2-Linux. Let me know if you run into any sticking points. Wish I could get a newer binutils working (newer ld included) but no luck so far.
    PS2 v9 NTSC, PS2 v12 NTSC, PS2 v15 VESA
    Reply With Quote  

  3. #3  
    Isles487 is offline Member
    Join Date
    Apr 2010
    Posts
    21
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    Thanks a lot Deba5er, that was a very quick, very helpful post. That fixed the configure script problems for Pango.

    Unfortunately, compiling GTK has been a very frustrating experience. I attempted to follow the same versions you posted on your 4shared for glib and pango. Your premade Cairo seemed to work fine. The problems come when compiling Glib/Pango. Between the two of them, I get "invalid string offset" errors that occur during compiling. Doesn't stop the build process, but I think it might be causing all sorts of problems. For instance, after Pango compiles, it won't install-- it complains that a certain glib shared library is missing, and the library it's missing is clearly in my lib path. I think the invalid string offsets are to blame.

    By disabling shared library builds, I was able to eventually compile a working GTK-- the only problem is that there was no text-- just squares, and this seemed to be due to pango having errors about not finding modules. Probably because I only built Pango as a static library.

    When I've searched online for "invalid string offset," I've read that this can be a problem with the linker tools. Any experience with this?
    Reply With Quote  

  4. #4  
    deba5er's Avatar
    deba5er is online now Moderator
    Join Date
    Jan 2006
    Posts
    593
    Downloads
    0
    Uploads
    0
    Mentioned
    2 Post(s)
    Tagged
    1 Thread(s)
    Likes Given
    6
    Likes Received
    8
    Have you run "ldconfig" as root on all directories containing library files, including glib2.0 after installing? This should ensure that the linker finds the libraries needed. As far as the "invalid string offset" error goes, I also experienced it in many compiles, but would be able to run the programs which resulted from such compiles. However, I know that 2.9 has known bugs, one of which prevents me from compiling dillo 3.x so I am hoping to get a good compile/install of a newer binutils/compiler (the gcc 3.0.3 compiler to be exact, which I already have with the old ld version 2.9).
    PS2 v9 NTSC, PS2 v12 NTSC, PS2 v15 VESA
    Reply With Quote  

  5. #5  
    Isles487 is offline Member
    Join Date
    Apr 2010
    Posts
    21
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    Oddly enough, I was able to compile Dillo 3, using the GCC 3.0.3. I downloaded/upgraded some of the X11 libraries, and I think that worked. If you'd like, I can tell you what versions I needed in order for Dillo to work. If I remember correctly, the problem was compiling FLTK-1.3.

    EDIT:
    Here are the X-org libraries I downloaded/compiled/installed:
    xtrans-1.2.6
    util-macros 1.9.0
    kbproto-1.0.5
    inputproto-2.0.1
    xproto--7.0.19
    libXau-1.0.0
    Xcb-proto 1.5
    libpthread-stubs-0.3
    renderproto-0.11.1
    xcb-1.4
    xcb-proto-1.5
    xrender-0.9.6
    x11-1.4.4

    Not an X library, but I probably needed it for something-
    GNU Gperf 3.0.1

    Most of these are all really small libraries and some of them are only headers.
    Last edited by Isles487; 10-02-2011 at 08:56 PM.
    Reply With Quote  

  6. #6  
    deba5er's Avatar
    deba5er is online now Moderator
    Join Date
    Jan 2006
    Posts
    593
    Downloads
    0
    Uploads
    0
    Mentioned
    2 Post(s)
    Tagged
    1 Thread(s)
    Likes Given
    6
    Likes Received
    8
    @Isles487

    Thanks. I'll get to compiling. How is dillo 3? Much improved or about the same except using fltk 1.3?
    PS2 v9 NTSC, PS2 v12 NTSC, PS2 v15 VESA
    Reply With Quote  

  7. #7  
    Isles487 is offline Member
    Join Date
    Apr 2010
    Posts
    21
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    It seems much the same from my testing. Still runs very nicely on the PS2 though. FLTK 1.3 doesn't seem to be much different.
    Reply With Quote  

Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •