Re: create / generate a new hal / public / xxxx.hal.o.uu file
Pavel Roskin <[email protected]>
| Newsgroups | gmane.linux.drivers.madwifi.user |
|---|---|
| Message-ID | <1264787328.27755.22.camel@mj> |
On Thu, 2010-01-28 at 22:43 +0100, [email protected] wrote: > I tried adding TARGET=mips-be-elf to make arguments, but compilation fail > due to compiler option specified in hal/public/mips-be-elf.inc file. > I can try to remove them all? The options from *.inc files are used in the build system to guard against incompatibilities between the build system used for HAL and the build system for the rest of the code. I suggest that you try other mips targets first. Removing the incompatible options should be the second thing to try. I think the linker would still prevent linking if the architecture is significantly different to cause problems. Alternatively, you could use the Subversion trunk version of MadWifi, which has no binary blobs and should not have that issue at all. > mips-linux-gcc: unrecognized option `-EB' > Assembler messages: > Error: -mips2 conflicts with the other architecture options, which imply > -mips1 > Error: trap exception not supported at ISA 1 It looks like you have a mips1 processor, and TARGET=mips-be-elf implies mips2. I don't know why -EB is not recognized. Maybe your target is little endian? Then the target to try would be mips1-le-elf. If you know that the target is big endian, then you'll need to remove -EB from the *.inc file. -- Regards, Pavel Roskin ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com