This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Hints for cross-compiling staprun?
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Grant Edwards <grant dot b dot edwards at gmail dot com>
- Cc: systemtap at sources dot redhat dot com
- Date: Mon, 30 Aug 2010 17:30:53 -0400
- Subject: Re: Hints for cross-compiling staprun?
- References: <i58rdt$k3i$2@dough.gmane.org> <i5h5tg$qf4$1@dough.gmane.org>
Hi -
grant.b.edwards wrote:
> [...]
> I've hit a few glitches, but I'm making progress. One issue is that
> the configure script refuses to check for the existence of files when
> cross-compiling. [...]
Perhaps we're using the wrong configure.ac directive to test for them.
> [...]
> The other problem is that the sources use a number of non-standard
> APIs without checking to see if they are, in fact, supported by the
> build environment. The ones that I tripped over are:
>
> index,rindex obsolete and not present in POSIX.1-2008.
OK, will fix.
> __progname doesn't seem to be part of any standard, and isn't
> present in any headers on any Linux system I've got.
(Where do we refer to that?)
> wordexp actually, I think this one is in POSIX.1-2008 -- it
> just wasn't enabled in my build of libc.
>
> It would result in a more graceful failure, if the configure script
> checked for those.
Well, we should be able to presume plain POSIX, but a few more tests
wouldn't hurt, I guess.
> [...]
> If the systemtap Makefile.in is going to use "install-sh -D",
> shouldn't it come with an install-sh that supports "-D"?
I guess on native linux boxes it was using /usr/bin/install, which
does understand -D. We should be able to adapt that to some
combination of -d / -t or mkdir -p. Will fix.
- FChE