Hi,

Made the following changes:
1) rename rumpxen-app-foo to rumpapp-xen-foo to make a future 
s/xen/other/ case more obvious.
2) made rumpapp-xen-make automatically execute make.  this makes the 
usage of the tool the same as regular make, and enables hardlinking 
rumpapp-xen-make to make and play $PATH games.  In case 
$RUMP_APPTOOLS_MAKE is set, that gets executed instead.
3) added rumpapp-xen-gmake as a shorthand.
4) made cc respect $RUMP_APPTOOLS_CC.  Would've wanted to use just $CC, 
but since make already sets CC to rumpapp-xen-cc, that's not possible.

https://github.com/rumpkernel/rumpuser-xen/compare/tools-newusage

ok or comments?


Also,

Is there any reason that the -D arguments to cc are in cc, and the -U 
argument to cc are in specs?  Can I just put all of them into specs so 
as to group logically similar parameters?

Can we replace -D__RUMPUSER_XEN__ with something like a more generic 
-D__RUMPAPP__?

Is the way CC gets set in the configure wrapper a bug?  I'm guessing it 
should be this way:

--- a/app-tools/rumpapp-xen-configure.in
+++ b/app-tools/rumpapp-xen-configure.in
@@ -2,4 +2,4 @@
  # invoke this (for example) as  .../app-configure ./configure --prefix=...
  set -e
  prog=$1; shift
-exec "$prog" --host=!ARCH!-rumpxen-netbsd CC=!APPTOOLS!/rumpapp-xen-cc
+CC=!APPTOOLS!/rumpapp-xen-cc exec "$prog" --host=!ARCH!-rumpxen-netbsd

However, that makes running configure very slow, since the whole xen 
image is linked for every test.  Also, the wrapper script is probably 
missing "$@".

As a note, couldn't figure out how to pass the --host parameter to 
configure transparently.  However, shouldn't it be --target?

   - antti

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
rumpkernel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rumpkernel-users

Reply via email to