Re: rump i386 cross compile trouble

["J. Hannken-Illjes" <hannken%eis.cs.tu-bs.de@localhost>]

On 07 Mar 2015, at 18:03, Patrick Welche <prlw1%cam.ac.uk@localhost> wrote:

> On Tue, Mar 03, 2015 at 02:56:16PM +0000, Patrick Welche wrote:
>> On Tue, Mar 03, 2015 at 12:10:15PM +0000, Patrick Welche wrote:
>>> Not having much luck.. with today's source I see:
>>> No DBG / optimisation anywhere. Additions to /etc/mk.conf:
>>> 
>>> RUMP_DIAGNOSTIC=yes
>>> RUMP_DEBUG=yes
>>> RUMP_LOCKDEBUG=yes
>>> RUMP_KTRACE=yes
>> 
>> Removing these gets a successful build - that narrows it down a bit...
> 
> Bisection just yielded a surprise: the build with RUMP_DEBUG=yes was
> broken by sys/kern/kern_module.c
> 
> revision 1.103
> date: 2015-02-28 23:04:34 +0000;  author: jmcneill;  state: Exp;  lines: +4 -3; 
> commitid: X5g1KIdu4fu6uPby;
> if the root file-system is not yet mounted, hide "vfs load failed" spam with opt
> ions DEBUG
> 
> 
> -               if (modclass != MODULE_CLASS_EXEC || error != ENOENT)
> +               if ((modclass != MODULE_CLASS_EXEC || error != ENOENT) &&
> +                   root_device != NULL)
> 
> but why? Compiler bug (gcc)?

Given this fragment is "#ifdef DEBUG" it looks like rump_server has to
be linked with librumpvfs in the DEBUG case?

Antti?

--
J. Hannken-Illjes - hannken%eis.cs.tu-bs.de@localhost - TU Braunschweig (Germany)