Doug Turner (:dougt) Reporter
	Description • 16 years ago

in our mozconfig, in order to build from windows 32 to windows ce, it is required that we set:

CROSS_COMPILE = 1

However, it appears that this flag is superficial and autoconf already can tell if you are cross compiling based on the target and host flags.

Furthermore, code in configure.in, such as:

http://mxr.mozilla.org/mozilla-central/source/js/src/configure.in#215

is not being executed.

We should clean this up, and not required CROSS_COMPILE to be defined and simply determine if we are cross compiling based on the target being set.

	Mike Hommey [:glandium] Assignee
	Comment 1 • 11 years ago

Turns out I'm backslapped by this in bug 969164 because of how poorly we're subconfiguring libffi. It turns out js/src is already setting CROSS_COMPILE=1 semi-automatically, so that makes libffi happy by chance, and moving libffi subconfigure to top-level breaks the charm. So, might as well do the right thing with CROSS_COMPILE.

	Mike Hommey [:glandium] Assignee
	Comment 2 • 11 years ago

https://tbpl.mozilla.org/?tree=Try&rev=05e93b3ebaa8

	Mike Hommey [:glandium] Assignee
	Comment 3 • 11 years ago

(In reply to Mike Hommey [:glandium] from comment #2)
> Created attachment 8372184 [details] [diff] [review]
> Stop requiring CROSS_COMPILE being set
> 
> https://tbpl.mozilla.org/?tree=Try&rev=05e93b3ebaa8

A note: this patch also makes us stop pretending that the linux 32 bits are cross compiles when in fact, they aren't because we build both host and target stuff with gcc -m32.

	Mike Hommey [:glandium] Assignee
	Comment 4 • 11 years ago

https://hg.mozilla.org/integration/mozilla-inbound/rev/01de43f70bed

	Ryan VanderMeulen [:RyanVM]
	Comment 5 • 11 years ago

https://hg.mozilla.org/mozilla-central/rev/01de43f70bed