--- Em sáb, 12/1/13, DJ Lucas escreveu: > De: DJ Lucas > Assunto: Re: [blfs-dev] icedtea-web on seamonkey problem > Para: "BLFS Development List" > Data: Sábado, 12 de Janeiro de 2013, 3:30 > On 01/11/2013 11:39 PM, JZB2 wrote: > > On Friday, January 11, 2013 04:38:10 PM Fernando de > Oliveira wrote: >>>> icedtea-2.3.3 (openjdk-1.7.0_09, built from >>>> source, after binary, per >>>> BLFS) >>>> seamonkey-2.13.2 >>>> icedtea-web-1.3 >>> I my case, >>> $ seamonkey --version >>> Mozilla SeaMonkey 2.15 >>> >> Thanks for the feedback. That's my next step, to >> try a newer monkey... >> >>> $ xulrunner -version >>> Mozilla XULRunner 18.0 - 20130109221022 >> That's a good point. I did not specifically >> install xulrunner. I simply >> install seamonkey as described in BLFS. The >> instructions for installing >> icedtea-web reference xulrunner as a prerequisite, but >> if one installs firefox, >> it seems that xulrunner is not needed per se. I >> made the logical inference >> then that since seamonkey is a superset of firefox, >> seamonkey alone should have >> sufficed. I was encoured in this belief by being >> able to build icedtea-web by >> merely adding the proper MOZILLA_CFLAGS and >> MOZILLA_LIBS env. vars., and >> installing seamonkey alone, no firefox and no >> xulrunner. >> >> I therefore assumed that no further dependence on >> xulrunner is needed. Do you >> see any runtime depencencies that this assumption does >> not cover? >> > Yes. If you run ldd on the IcedTeaPlugin.so, the lack of > "not found" > errors should make it fairly obvious. If you just build > XULRunner by the > book, it very well might work without rebuilding the plugin > (assuming > your modifications didn't break anything else), but I think > I'd still > rebuild the plugin after XUL. If you really want to get > around XUL, > adding LD_LIBRARY_PATH to whatever the Seamonkey equivalent > is of the > run-mozilla.sh script might be sufficient (I honestly don't > know), but > you should be aware that it is not tested...anywhere. Also, > please don't > make that variable or the libs global either. > Experimentation is fun, > but I think I'd stick to the book on this one (been there, > done that) > unless you are just really cramped for space.
Hi, DJ, I was not sure how to reply to John's questions, but recommending to follow books' instructions. > Also, for future reference, in general it is best practice > to consult > the support team of the distro unless you are absolutely > sure about a > bug. It's not an ego thing, it's just that it can look bad > on the distro > if too many invalid bugs are opened from its users (so I > guess it is an > ego thing). :-) When I was actually active on > distro-pkg-dev, I tackled > more than a few off list. Please do take the time to add a > comment to > the icedtea bug stating that this was user error and can be > closed > invalid (or, if you have permissions, just close it > yourself). As > evidenced by the number of bugs (a majority of which will > eventually be > tracked down to developers depending on undocumented > "features" or > deprecated code in the closed plugin), those guys have > enough on their > plate. :-) > > -- DJ Lucas Here, I only noticed the post was in dev, after your input, the question seems better for support, so John would have more chances of help there. []s, Fernando -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
