GNU Smalltalk and cross-building images

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

GNU Smalltalk and cross-building images

Holger Freyther
Hi Paolo,

for the OpenEmbedded integration I will need to build a GNU Smalltalk image
for ARM/PPC 32bit on maybe a AMD64 build host. Right now I only have the need
to build an image, any ideas how to approach this best? A script to convert
images, dedicated image writing?

holger

My current deployment script is:

Eval [
    | name img |
    name := Smalltalk arguments at: 1.
    img := Smalltalk arguments at: 2.

    (PackageLoader packageAt: name)
        fileIn;
        start.

    ObjectMemory
        snapshot: img;
        quit.

]


_______________________________________________
help-smalltalk mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-smalltalk
Reply | Threaded
Open this post in threaded view
|

Re: GNU Smalltalk and cross-building images

Paolo Bonzini-2
On Sat, Sep 17, 2011 at 20:11, Holger Hans Peter Freyther
<[hidden email]> wrote:
> Hi Paolo,
>
> for the OpenEmbedded integration I will need to build a GNU Smalltalk image
> for ARM/PPC 32bit on maybe a AMD64 build host. Right now I only have the need
> to build an image, any ideas how to approach this best? A script to convert
> images, dedicated image writing?

32-bit to 32-bit should work across hosts, even cross-endianness
(modulo bugs which should be fixed easily).  Just use an i686 binary
on the AMD64 host.

Can you set me up to look at debian multiarch?  Thanks,

Paolo

_______________________________________________
help-smalltalk mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-smalltalk
Reply | Threaded
Open this post in threaded view
|

Re: GNU Smalltalk and cross-building images

Holger Freyther
On 09/17/2011 08:28 PM, Paolo Bonzini wrote:

> 32-bit to 32-bit should work across hosts, even cross-endianness
> (modulo bugs which should be fixed easily).  Just use an i686 binary
> on the AMD64 host.


>
> Can you set me up to look at debian multiarch?  Thanks,

yes, I did not forget about it, i was just heading to a trip after vacation.
Feel free to send me a public ssh key.

holger

_______________________________________________
help-smalltalk mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-smalltalk
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: GNU Smalltalk and cross-building images

Paolo Bonzini-2
On 09/21/2011 09:38 AM, Holger Hans Peter Freyther wrote:
>>> >>  My debian friend says... one can use:
>>> >>
>>> >>  $ ls/lib/`gcc -print-multiarch`/libc*.so
>>> >>  /lib/x86_64-kfreebsd-gnu/libc-2.13.so
>>> >>  /lib/x86_64-kfreebsd-gnu/libcidn-2.13.so
>>> >>  /lib/x86_64-kfreebsd-gnu/libcrypt-2.13.so
> Okay -print-multiarch is only in gcc 4.6 of debian unstable, Ubuntu has a
> messed up gcc 4.5 without the print-multiarch option.

Then I don't care.  Sorry.  You don't break 20-year-old conventions and
invent new toolchain options without bothering to contact upstream gcc.

>> >    AC_CACHE_CHECK([how to dlopen the C library], gst_cv_libc_so_name, [
>> >      if test $GCC = yes; then
>> >  -    gst_lib_path=`$CC --print-multi-os-directory $CFLAGS $CPPFLAGS`
>> >  +    if gcc -print-multiarch>/dev/null 2>&1; then
>> >  +      gst_lib_path=`$CC -print-multiarch $CFLAGS $CPPFLAGS`
>
> this would be missing the '/lib' as print-multiarch only prints the host
> triplet.. (yeah to breaking cross compilation)

It us added later, compare these:

$ gcc -print-multiarch             # on Debian unstable
x86_64-kfreebsd-gnu
$ gcc --print-multi-os-directory   # on Fedora
../lib64

Paolo

_______________________________________________
help-smalltalk mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-smalltalk
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Re: GNU Smalltalk and cross-building images

Holger Freyther
On 09/21/2011 11:28 AM, Paolo Bonzini wrote:

>
> Then I don't care.  Sorry.  You don't break 20-year-old conventions and invent
> new toolchain options without bothering to contact upstream gcc.

I agree, it is insane to have that crap. On the other hand GNU Smalltalk is
probably not important enough for Canonical to fix that. But thanks for your time.





>> this would be missing the '/lib' as print-multiarch only prints the host
>> triplet.. (yeah to breaking cross compilation)
>
> It us added later, compare these:

okay, I will verify it is working on kFreeBSD64/debian and then don't care for
this version of Ubuntu.

_______________________________________________
help-smalltalk mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/help-smalltalk