Hi, Im compiling the firefox-2.0 on ARM tool-chain over GTK-DFB. In the cross-compilation i have made the changes in the mozconfig for cross-compilation as follows:
I have installed libIDL for ARM in .moconfig: CROSS_COMPILE=1 LIBIDL_CONFIG=/usr/local/arm-linux/usr/bin/libIDL-config-2 HOST_LIBIDL_CONFIG=/usr/bin/libIDL-config-2 ac_add_options --target=arm-linux ac_add_options --build=i686-linux But when i start the make: It gives me problem at nsinstall. Says its a Wrong format and it cannot execute. The file of "nsinstall" shows its built for ARM. Pls help me to recover from this ---------------------------- bsd wrote: > >>1. Cross Compilation is giving a hell of a problem as the binaries >>generated for arm are required to build mozilla further. So obviously i >>get errors like "FILE IN WRONG FORMAT ".......Somehow its a lil silly >>becoz it totally nullifies the need of Cross-Compilation.......I would >>love to get some tips on this . > > I am no expert but I have crosscompiled firefox 1.5 with the directfb > patch applied OK. Once you have things configured OK should compile > without such problems. Ensure you have libIDL compiled for both your host > and target. > > Makesure your .mozconfig has something along the lines of > > CROSS_COMPILE=1 > LIBIDL_CONFIG=/usr/$MYTARGETCHOST/usr/bin/libIDL-config-2 > HOST_LIBIDL_CONFIG=/usr/bin/libIDL-config-2 > CXX=$MYTARGETCHOST-gcc > CC=$CXX > ac_add_options --target=$MYTARGETCHOST > > substituting $MYTARGETCHOST as appropriate. LIBIDL_CONFIG needs to point > to a libIDL-config-2 for the target and HOST_LIBIDL_CONFIG to one for the > host. This is essentially what I used - > > 'CXX=$MYTARGETCHOST-gcc > CC=$CXX' > > may not actually be required but I dont have time to try it without now. > > You may find you need to update build/autoconf/config.sub, > build/autoconf/config.guess, mozilla/nsprpub/build/autoconf/config.sub, > mozilla/nsprpub/build/autoconf/config.guess , > directory/c-sdk/config/autoconf/config.sub, > directory/c-sdk/config/autoconf/config.guess so that it configures > properly for with your CHOST - perhaps take config.sub and config.guess > from the root of your gtk+ tree for this. > > Once it's configuring correctly you should at least find it's not trying > to execute binaries built for the target on the host. You'll probably > still hit further problems - I may be able to help with these if you post > the specific problems. > >>2. To overcome this issue , I got the gnu make on my target system and >>started Compiling Mozilla on arm itself. Believe me its a very >>irritating idea coz it takes around 2.5 hrs to build around 50% >>(obviously the processor speed is a big drawback-----300MHz). My work >>was going on well until i got messed up with some java utilities which >>needed "java, javac, javah, jar " tools. I tried to find the Source for >>JDK which i had planned to cross compile for arm but i was not able to >>get it on the net freely.........(If someone can share,it will be a big >>help). The only thing that was close to solving my problem was JDK >>built for arm4. But somehow it didn't work as for my system i need arm5 >>built. > > I dont have any java* in my cross compile environment. Perhaps you can > disable some stuff in your .mozconfig. I disabled alot of stuff with the > intention of re-enabling it if I needed it. I wanted smallest possible > build. > > Hope this is of some help. Be interesting to hear how you get on. > -- View this message in context: http://www.nabble.com/Mozilla-porting-over-GTK-DirectFB-on-arm-tf3034391.html#a14020187 Sent from the Mozilla - Embedding mailing list archive at Nabble.com. _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
