On 11/22/2011 01:43 PM, Martin Ward wrote:
> On 22/11/11 11:49, Wayne Blaszczyk wrote:
>> On 11/11/11 00:33, DJ Lucas wrote:
>>> On 11/09/2011 06:07 PM, Jeremy Henty wrote:
>>>> Bruce Dubbs wrote:
>>>>> Andrew Benton wrote:
>>>>>> Yes, with wget I downloaded
>>>>>> ftp://ftp.mozilla.org/pub/firefox/releases/8.0/source/firefox-8.0.source.tar.bz2
>>>>>> It compiled on a 3.1 kernel without patching.
>>>>> I'd appreciate knowing the instructions you used.  I can't do it yet
>>>>> because I haven't put X on my development system yet.
>>>> I'm  not  the  person  you  replied  to, but  here  are  my  notes  on
>>>> Firefox-[78]* anyway...
>>>>
>>>> You must configure cairo with --enable-tee .
>>>>
>>>> If you haven't installed yasm then you must disable webm video.
>>>>
>>>> Jeremy
>>> Guys, just in case you are not aware, we should probably consider using
>>> external npapi. We can of course, fix anything that is using the
>>> incorrect version scheme, but looking to the future, that might be a bit
>>> of work (OpenJDK specifically will be a PITA, don't know about other
>>> open source plug-ins).
>>>
>>> -- DJ Lucas
>>>
>> I am having problems with Firefox 8 myself.
>> I've built xulrunner and firefox separately with no problems, but when I
>> try to execute firefox, it comes back with the following message:
>> Could not read application.ini
>> Googling comes up with a lot of hits, but no real solutions.
>>
>> Strace produces the following:
>> mmap(0x7f5a2c600000, 1048576, PROT_READ|PROT_WRITE,
>> MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f5a2c600000
>> stat("/usr/local/bin/firefox", 0x7fff5744a408) = -1 ENOENT (No such file
>> or directory)
>> stat("/bin/firefox", 0x7fff5744a408)    = -1 ENOENT (No such file or
>> directory)
>> stat("/usr/bin/firefox", {st_mode=S_IFREG|0755, st_size=65128, ...}) = 0
>> lstat("/usr", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
>> lstat("/usr/bin", {st_mode=S_IFDIR|0755, st_size=36864, ...}) = 0
>> access("/usr/bin/xulrunner/libxpcom.so", R_OK) = -1 ENOTDIR (Not a
>> directory)
>> open("/usr/bin/application.ini", O_RDONLY) = -1 ENOENT (No such file or
>> directory)
>> write(2, "Could not read application.ini\n", 31Could not read
>> application.ini
>> ) = 31
>> exit_group(1)
>>
>> Not sure why it would be checking /usr/bin/xulrunner/libxpcom.so since
>> /usr/bin/xulrunner is a symbolic link to a script.
>> Anyway copying the application.ini file to /usr/bin, just takes it to
>> the next problem:
>> Could not find the Mozilla runtime.
>> It seems to me that it is confusing /usr/lib with /usr/bin ?
>> The mozconfig I used is pretty much the same as what is current in the
>> BLFS book with slight alterations.
>>
>> Any pointers to what the problem might be?
>> Thanks,
>> Wayne.
>>
>>
>>
> Sounds like you need to put in a symbolic link from /usr/bin/firefox ->
> /usr/lib/firefox/firefox or similar, I believe this was missing in 8.0,
> but fixed in 8.0.1
>
>
>
> martin
I got the same problem. I think it's a mozilla bug.
I'm just compiling xulrunner with the following patch. Be patient or try it 
yourself!
----------------------------------------------------------------------------------
--- mozilla-release/xulrunner/stub/nsXULStub.cpp        2011-11-15 
08:25:26.000000000 +0100
+++ mozilla-release-cr/xulrunner/stub/nsXULStub.cpp     2011-11-22 
18:39:00.000000000 +0100
@@ -266,7 +266,7 @@
    strncpy(tmpPath, argv[0], sizeof(tmpPath));
    lastSlash = strrchr(tmpPath, '/');
    if (lastSlash) {
-    *lastSlash = 0;
+    // *lastSlash = 0;
      realpath(tmpPath, iniPath);
    } else {
      const char *path = getenv("PATH");
@@ -378,7 +378,7 @@
    nsINIParser parser;
    rv = parser.Init(iniPath);
    if (NS_FAILED(rv)) {
-    fprintf(stderr, "Could not read application.ini\n");
+    fprintf(stderr, "Could not read application.ini: '%s'\n",iniPath);
      return 1;
    }
--------------------------------------------------------------------------------------------

Claus
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to