On 23/09/14 11:09, Martin Lucina wrote: >> 2) I then tried to build fstest2.c manually: >> >> $ gcc -o fstest2 fstest2.c -I../common -I../../../rump-static/include/ >> -L../../../rump-static/lib ../../../rump-static/lib/librump.a >> ../../../rump-static/lib/librumpuser.a >> ../../../rump-static/lib/librumpfs_sysvbfs.a -lrt -ldl > > Two things - I noticed later that the path to the image is required on the > command line, but that doesn't change the failure (since that happens when > doing mkdir). Further, I tried a normal dynamic build without MKPIC=no, > still linking fstest2 manually:
It's an automated test and not very user-friendly ... > $ gcc -o fstest2 fstest2.c -I../common -I../../../rump/include/ > -L../../../rump/lib -lrump -lrumpuser -lrt -ldl > > And the result is the same failure at mkdir time. You're missing -lrumpvfs, and actually a bunch of other components. See RUMPLIBS in fstest_img/Makefile. Alternatively, use ./rump/bin/rump_wmd. I think you need a dynamic build for the latter to work, though you can use the results from rump_wmd just the same on a static build. I'm sure there's a manpage somewhere in the buildrump.sh build, but just in case, here's the one on the web: http://netbsd.gw.com/cgi-bin/man-cgi?rump_wmd++NetBSD-current - antti ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
