Xft rpms
- phoenixkid
- Posts: 27
- Joined: December 4th, 2002, 9:32 pm
- Contact:
Xft rpms
For those interested, I've posted Xft tarballs and rpm's (for rh8). Enjoy.
http://phoenix.ragweed.net/
http://phoenix.ragweed.net/
- whiprush
- Posts: 66
- Joined: November 4th, 2002, 10:06 pm
- Contact:
-
- Posts: 56
- Joined: December 7th, 2002, 8:26 pm
- mesostinky
- Posts: 215
- Joined: November 4th, 2002, 10:44 pm
- Location: NJ
-
- Posts: 56
- Joined: December 7th, 2002, 8:26 pm
Yes, thanks. That's exactly how I have it linked. The plain vanilla Phoenix build works fine, but the xft enabled has both the java issues and bookmark/history issues. That's after completely wiping out the program install directory and profile. <sigh> Ah well, enough for one day. Thanks for the thought though.
-
- Posts: 56
- Joined: December 7th, 2002, 8:26 pm
ROTFL! Just as I was about to throw in the towel, I got it working by deleting all files and directories within the phoenix path *except* for the plugins directory. I then used the tarball and copied over all but the plugins directory. Previously, I had been using the RPM. I dunno . . too much coffee? Not enough? Just dumb luck? Whatever, . . it works and this is *the* Linux browser! ))
-
- Posts: 56
- Joined: December 7th, 2002, 8:26 pm
-
- Posts: 56
- Joined: December 7th, 2002, 8:26 pm
When started from the console, this is the error I see with respect to the java plugin at startup:
LoadPlugin: failed to initialize shared library /usr/java/j2re1.4.1_01/plugin/i386/ns610/libjavaplugin_oji.so [/usr/java/j2re1.4.1_01/plugin/i386/ns610/libjavaplugin_oji.so: undefined symbol: GetGlobalServiceManager_16nsServiceManagerPP17nsIServiceManager]
LoadPlugin: failed to initialize shared library /usr/java/j2re1.4.1_01/plugin/i386/ns610/libjavaplugin_oji.so [/usr/java/j2re1.4.1_01/plugin/i386/ns610/libjavaplugin_oji.so: undefined symbol: GetGlobalServiceManager_16nsServiceManagerPP17nsIServiceManager]
-
- Posts: 56
- Joined: December 7th, 2002, 8:26 pm
Unfortunately, I don't know enough to properly explain this, but my research has led me to believe that the java issue is a result of the interaction between the jre and the version of the gcc lib used to compile Phoenix. Then again, I could have that backwards. In any case, there's apparently no fix unless one or the other is changed to make them play together. Ah well, no java for now I suppose.
-
- Posts: 15
- Joined: November 5th, 2002, 4:06 am
geekboy2000 wrote:Unfortunately, I don't know enough to properly explain this, but my research has led me to believe that the java issue is a result of the interaction between the jre and the version of the gcc lib used to compile Phoenix. ...
In fact, the java plugin won't work if Mozilla/Phoenix is compiled on Linux with the "wrong" version (whatever that is) of gcc. There is a bug about it. It is expected that this will be fixed in the next version of the plugin. Is this your problem ?
-
- Posts: 56
- Joined: December 7th, 2002, 8:26 pm
-
- Guest
glibc 2.2 vs glibc 2.3
Uh, I had the same problem with java not working with the anti-aliasing
builds. Well, the reason I came to Phoenix anyway was because Netscape
4.7.x started to crash every time it loaded a page with java after
upgrading to glibc 2.3.1. So it was important that I get java to work.
I noticed the builds I tried were compiled against glibc 2.2. Sol I
compiled my own against glibc 2.3 and everything works. I've used both
gcc 2.95 and 3.2. Both work.
builds. Well, the reason I came to Phoenix anyway was because Netscape
4.7.x started to crash every time it loaded a page with java after
upgrading to glibc 2.3.1. So it was important that I get java to work.
I noticed the builds I tried were compiled against glibc 2.2. Sol I
compiled my own against glibc 2.3 and everything works. I've used both
gcc 2.95 and 3.2. Both work.
-
- Posts: 56
- Joined: December 7th, 2002, 8:26 pm
-
- Guest
How does one build those nifty little binary tarballs?
hey geekboy:
Well, first, I spent an afternoon without Phoenix and found out how finicky these builds can be. Apparently while I can compile Phoenix with either gcc-3.2 or 2.95, fontconfig and libXft.so have to be compiled with 2.95. I have no idea why. I can't run Phoenix with the new Debian fontconfig package either. And for some reason my Phoenix wants to call libXft.so.1 instead of the libXft.so.2 that it needs. So I have to hide files and play tricks with ldconfig to get it to run. In summary, I'd be surprised if anyone could get my build to run on anything other than my stystem.
Anyway, I don't know how to build those binary packages, but if someone can explain it to me or if I can figure it out and it's less than 10 Mb, I should be able to post it. Hah, finally I can share my frustration!
Well, first, I spent an afternoon without Phoenix and found out how finicky these builds can be. Apparently while I can compile Phoenix with either gcc-3.2 or 2.95, fontconfig and libXft.so have to be compiled with 2.95. I have no idea why. I can't run Phoenix with the new Debian fontconfig package either. And for some reason my Phoenix wants to call libXft.so.1 instead of the libXft.so.2 that it needs. So I have to hide files and play tricks with ldconfig to get it to run. In summary, I'd be surprised if anyone could get my build to run on anything other than my stystem.
Anyway, I don't know how to build those binary packages, but if someone can explain it to me or if I can figure it out and it's less than 10 Mb, I should be able to post it. Hah, finally I can share my frustration!
-
- Posts: 56
- Joined: December 7th, 2002, 8:26 pm
Well, I'll be happy if I can find myself able to achieve your level of frustration. I spent most of last night trying to build Phoenix from Moz source, and gave up after hitting an "no rule to make target 'export'" error. I simply don't yet know enough to be able to tackle it yet. So, you're making good progress. I'll keep an eye out for your breakthrough.