Bug#610653: ITP: dmtcp -- Checkpoint/Restart functionality for Linux processes
On Mon, 31 Jan 2011, Yaroslav Halchenko wrote:
> > > | dmtcp_1.2.0+svn864-1~nd09.04+1_i386.build FAILED
> > > | dmtcp_1.2.0+svn864-1~nd09.04+1_amd64.build FAILED
> > > `---
> > This is where I have some problem reproducing the failure. I tried
> > building it on Ubuntu9.10 and 10.10, both 32-bit, but it built just
> > fine. I didn't see any issues. I tried by downloading the files from
> > mentors.debian.net and then doing a dpkg-source followed by
> > dpkg-buildpackage. Can you tell me how to reproduce these failures?
> > Should I run a different set of commands?
> the only obvious difference was that in my case it was '-B' build, i.e.
> " binary-only build, limited to architecture dependent packages"; but I
> do not see how it should have impacted the build... I will check
> tomorrow in greater detail
ok -- the reason is:
# 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?
Another hint: sed has -i option for 'infile' changes, so no need for temporary
files
--
=------------------------------------------------------------------=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic
Reply to: