Re: Building OOo m100 on AMD64

Hi Jan,
We are using 32 bit Debian on our dual AMD Opteron 250 system with Tyan 
K8 motherboard. Only the kernel itself is 64 bit:

ooo@shvo:~/SRC680_m100$ uname -a
Linux shvo 2.6.8-11-amd64-k8-smp #1 SMP Sun Apr 10 18:58:09 UTC 2005 x86_64 GNU/Linux

But our gcc is:

ooo@shvo:~/SRC680_m100$ gcc -v
Reading specs from /usr/lib/gcc/i486-linux/3.4.4/specs
Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr 
--libexecdir=/usr/lib --with-gxx-include-dir=/usr/include/c++/3.4 --enable-shared --with-system-zlib --enable-nls --without-included-gettext 
--program-suffix=-3.4 --enable-__cxa_atexit --enable-libstdcxx-allocator=mt --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-java-gc=boehm --enable-java-awt=gtk --disable-werror i486-linux
Thread model: posix
gcc version 3.4.4 20050314 (prerelease) (Debian 3.4.3-12)

So according to what you indicate below, we shouldn't be seeing these 
compile errors since we should be able to compile on an AMD64 
architecture running a 32 bit OS.

Could the problem be the version of gcc we are using?
Regards,

  - yba


On Tue, 24 May 2005, Jan Holesovsky wrote:

> Hi Jonathan,
>
> On Tue, 24 May 2005, Jonathan Ben Avraham wrote:
>
>> Can we get a copy of the code so that we can complete our compilation?
>> We don't need something bug-free, we just want to finish the build on our
>> dual AMD 250 so that we wont have to go back to using older, slower
>> hardware.
>
> I want to make it available soon, but don't expect that it'll help you
> much.  The (non)working bridges are just a bit of all the pain; more
> patches are necessary, and even with them you won't be able to load a
> document.  Of course, if you want to help with the porting, you are very
> welcome and I'll be happy to support you as much as I can!
>
> If you just need to get the compilation faster, I'd recommend you either
> to use icecream (http://wiki.kde.org/tiki-index.php?page=icecream) on all
> your machines and run a distributed build, or to setup a 32bit Linux
> installation in a directory on the 64bit machine, chroot there with
> linux32 and run the compilation.
>
> For the icecream solution I'd recommend you to build using ooo-build
> (http://go-oo.org/), it has --with-gcc-speedup=icecream configure switch.
> Icecream can use the AMD64 machines for 32bit builds by itself.
>
> If you do not want to use the distributed build, let's say that you have
> 64bit system in the root (/) and 32bit system in /32bit subdir (can be
> also another partition) on the 64bit machine.  Then do:
>
> export PKG_CONFIG_PATH="/usr/local/lib/pkgconfig:/usr/lib/pkgconfig:/opt/gnome/lib/pkgconfig"
> unset DISPLAY
> linux32 chroot /32bit
>
> and run the 32bit compilation there.
>
> Regards,
> Jan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

-- 
  EE 77 7F 30 4A 64 2E C5  83 5F E7 49 A6 82 29 BA    ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
      - [email protected] - tel: +972.2.679.5364, http://www.tkos.co.il -