Bug#610653: ITP: dmtcp -- Checkpoint/Restart functionality for Linux processes

[Kapil Arya <kapil@ccs.neu.edu>]

> # uname -m
> x86_64
> # dpkg --print-architecture
> i386
>
> quite often Debian 32bit-built systems are running on top of 32/64 bit
> capable kernel.  So, imho correct way to deduce built type is not from kernel
> but from toolchain itself:
>
> # grep OUTPUT_ARCH mtcp.t
> OUTPUT_ARCH(i386)
>
> and on 64bit kernel+toolchain it looks like
>
> $> ld -shared -verbose | grep OUTPUT_ARCH
> OUTPUT_ARCH(i386:x86-64)
>
> which is indeed somewhat inconvenient but signals that both 32bit and
> 64bit supported (related to my elderly question on 32bit libraries support on
> 64bit systems)
>
> May be OUTPUT_FORMAT content would be more appropriate?

So, is it true that in this case where
> # uname -m
> x86_64
> # dpkg --print-architecture
> i386

the OUTPUT_FORMAT would be "elf32-i386"? i.e.

#  ld -shared -verbose | grep OUTPUT_FORMAT
OUTPUT_FORMAT("elf32-i386", "elf32-i386",

> Another hint:  sed has -i option for 'infile' changes, so no need for temporary
>               files

Thanks, will use it. :-)

>
> --
> =------------------------------------------------------------------=
> Keep in touch                                     www.onerussian.com
> Yaroslav Halchenko                 www.ohloh.net/accounts/yarikoptic
>