Date: Mon, 23 Feb 2015 17:10:34 -0600 From: Rob J <rjohanne@gmail.com> To: freebsd-sparc64@freebsd.org Cc: Marius Strobl <marius@alchemy.franken.de> Subject: Re: upd lite broken on sparc64 with vimage Message-ID: <CAEsfORx_cmmTDeoRvLnp9fgcdB0NkjummVVNPmLC8YiTfM5h5w@mail.gmail.com> In-Reply-To: <CAEsfORwj5EvzX%2Bt5k2D7Ebd0_=79K9V79F2LV27a_%2BznRyGA6A@mail.gmail.com> References: <CAEsfORwj5EvzX%2Bt5k2D7Ebd0_=79K9V79F2LV27a_%2BznRyGA6A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Marius, When you said userland is broken untill r278870 - is some of the behaviour like what I am seeing after buildinng world? I am getting a lot of sendsig errors about all sorts of binaries being too old, and that I need to rebuild them example while installing world: sendsig: bc is too old, rebuild it example after eventually installing world: sendsig: syslogd is too old, rebuild it (syslogd doesn't get started) Every time I get the sendsig, the related command dies. Can you provide some insight to this? Thanks, Robert On Fri, Jan 16, 2015 at 10:32 AM, Rob J <rjohanne@gmail.com> wrote: > Hello, > I checked out the stable sources for 10.1 via svnlite, and I have tried > compiling a generic kernel with "options VIMAGE" added, but the compile > breaks down while compiling src/sys/netinet/in_proto.c with dereferencing > errors like this: > > In file included from /export/usr/src/sys/netinet/in_proto.c:83: > /export/usr/src/sys/netinet/udp_var.h: In function 'get_inpcbinfo': > /export/usr/src/sys/netinet/udp_var.h:153: error: dereferencing pointer to > incomplete type > /export/usr/src/sys/netinet/udp_var.h:153: error: dereferencing pointer to > incomplete type > /export/usr/src/sys/netinet/udp_var.h: In function 'get_pcblist': > /export/usr/src/sys/netinet/udp_var.h:159: error: dereferencing pointer to > incomplete type > /export/usr/src/sys/netinet/udp_var.h:159: error: dereferencing pointer to > incomplete type > *** Error code 1 > > Apparently this was an issue in the power-pc platform as well back in May of > 2014, but was resolved - see this thread: > http://lists.freebsd.org/pipermail/freebsd-net/2014-May/038831.html > > Is there a fix that can be applied on the sparc64 platform? > > Thanks, > > Robert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEsfORx_cmmTDeoRvLnp9fgcdB0NkjummVVNPmLC8YiTfM5h5w>