On 29/12/14 19:16, Kevin Smith wrote:
> I've been following rumpkernel development from afar ever since I read
> Antti's thesis over a year ago. I've recently started working on a project
> where I think the rumpkernel arch, specifically rumprun-xen, could be a
> great fit.

The _idea_ is that you could do development conveniently with 
rumprun-posix in userspace, and then just build & deploy the final image 
where you want it (cloud, device, etc.).  But things are not quite there 
yet, at least if you're not intimately familiar with the in-flux 
differences between -posix and -xen/baremetal.

> stunt ld: unknown option -pie
>
> I tracked this down to app-tools/ld not understanding -pie. Based on the
> other case clauses I added one to skip -pie (see attached diff). This got
> me a bit further but then the build failed when ld couldn't find
> libssp_noshared.

I think we should just ignore PIE for now, so your patch is correct in 
that sense.  I think a similar approach would work for libssp_noshared 
(you might need to run the build with -fno-stack-protector).

As you can see, part of the problem is that the target platform leaks 
through from the build chain, even though we only want the target 
machine architecture.  So we run into this whack-a-mole game where you 
need to plug the places where the target platform shines through from 
the toolchain.

> I wasn't sure what to do here since I think (please correct me if I'm
> wrong) the build should resolve dependencies inside the tree (probably from
> rumpsrc?) On a related note I'm getting many instances of this warning from
> the build using /usr/include/sys/cdefs.h from the Linux host:
>
> /usr/include/sys/cdefs.h:1:2: warning: #warning usage of non-standard
> #include <sys/cdefs.h> is deprecated [-Wcpp]
>
>   #warning usage of non-standard #include <sys/cdefs.h> is deprecated
>
> Should the build use the sys/cdefs.h from rumpsrc instead of my local
> system version?

Yes, you are correct in thinking that the host sys/cdefs.h should never 
be used for rumprun-xen.  I'm not sure why that happens.  Are you 
running ./buildxen.sh?

> Should I be able to compile rumprun-xen on Linux or do I need a NetBSD
> compilation environment?

The build should be host independent, for any reasonable value of $host. 
  If things don't work on any modern'ish unixy system, I'd consider that 
a bug.  (and if they don't work on IRIX 5.3, tough).

------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
rumpkernel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rumpkernel-users

Reply via email to