Building on non-std architectures

[pointo1d]

Hiya Dave ,
On 30/09/14 18:57, David Holmes wrote:
> Hi Dave,
>
> On 1/10/2014 2:05 AM, pointo1d wrote:
> <snip>
> For general cross-compilation we just set extra-cflags to pass things 
> like this through; and don't set the --with-target-bits option.
>
> Aside: I would think that supporting 31-bit would require a huge 
> number of changes to the sources (unless it is somehow masked by the 
> C/C++ compiler.
>
> David H.
>
>> TIA & rgds ,
>>
TFT fast response Dave.

I did play with that, but having invoked configure as ...

/home/foreman/sandbox/source/configure 
--with-boot-jdk=/home/foreman/sandbox/bootjvm/sdk80 
--with-import-hotspot=/home/foreman/sandbox/bootjvm/sdk80 
--with-cups-include=/home/foreman/sandbox/thirdparty/include/cups 
--with-alsa-include=/home/foreman/sandbox/thirdparty/include 
--with-extra-cflags="-m31 -DIBM_DBGMALLOC 
-I/home/foreman/sandbox/thirdparty/include -I/usr/include/freetype2" 
--with-extra-ldflags="-m31 -L/usr/X11R6/lib" 
--with-extra-cxxflags="-m31" --openjdk-target=s390-linux 
--with-boot-jdk-jvmargs=-Xmx800m --x-libraries=/usr/X11R6/lib

I always encounter the configure error ...

checking size of int *... 8
configure: The tested number of bits in the target (64) differs from the 
number of bits expected to be found in the target (31).
configure: I'll retry after setting the platforms compiler target bits 
flag to -m31
checking size of int *... 4
configure: error: The tested number of bits in the target (32) differs 
from the number of bits expected to be found in the target (31)
configure exiting with result code 1

-- 
​Dave Pointon FIAP MBCS - Contractor engaged by IBM

Now I saw, tho' too late, the folly of beginning a work before we count the cost and
before we we judge rightly of our strength to go thro' with it - Robinson Crusoe