[Solved] [WAS:libc build error] Mostly all solved bw-iw-ik from 4-20-2016

[Jeffrey Bouquet]

On Wed, 20 Apr 2016 18:37:45 -0700 (PDT), "Jeffrey Bouquet" <jbtakk at iherebuywisely.com> wrote:

> 
> 
> On Wed, 20 Apr 2016 17:37:16 -0700 (PDT), "Jeffrey Bouquet" <jbtakk at iherebuywisely.com> wrote:
> 
> > 
> > 
> > On Wed, 20 Apr 2016 12:28:29 -0400, Allan Jude <allanjude at freebsd.org> wrote:
> > 
> > > On 2016-04-20 12:06, Jeffrey Bouquet wrote:
> > > > unistd
> > > > 
> > > > 
> > > > /usr/src/lib/libc/../../include/unistd.h:330:45: error: expected function body after function declarator
> > > > int    execl(  .................................
> > > >                                                          332:46:    
> > > > same...
> > > > 
> > > > stops libc
> > > > otherwise clang36 seems to be building so far, if it builds unsure about installworld
> > > > _______________________________________________
> > > > freebsd-current at freebsd.org mailing list
> > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
> > > > 
> > > 
> > > The mailing list strips attachments. Can you upload it somewhere and
> > > provide a link
> > > 
> > > -- 
> > > Allan Jude
> > > _______________________________________________
> > > freebsd-current at freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > > To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
> > 
> > 
> > Well, it is now r298350 Wed Apr 20...
> > However several problems
> > 
> > SINGLE-USER BOOT PROBLEMS
> > 1... usual boot fails, this is single-user adjusted, but I cannot add swap (swapon? swapctl?)
> > 1a...  the last time, it was fixed with using the old /kernel ... 
> > 
> > multi-user boot problems
> > 
> > 2... the last usual boot dumped with vm_pager or something,  verbose boot times out with xpt_config not completing.
> > 2a.... could be a wrong setting is loader.conf, the nvidia.ko not yet updated (which it now is ) for the latter
> >   case I have yet to reboot to test
> >   2b...   Reboot to test takes longer, /rescue/mount each filesystem individually... 
> > 
> > 
> > As one might surmise, I'd rather see buildworld made more foolproof than other recent improvements 
> > (pkg, zfs, ...)
> 
> From backup, I have r288246 kernel and nvidia.ko  (v11)
> from source, I have world and all except those TWO files at r298350 )(v11), nvidia (newer) won't load with older kernel
> A few at-boot scripts no longer work as expected... but no other major problems (swap is present again)
> (multi-user boot works) 
> 
> Best practice maybe to update the kernel?  It is a custom one from way back in 2004 initially
> without sound drivers and without debug symbols...  and many esoteric lines added which I cobbled
> together at first then changed per diffs of GENERIC over the years...
> 
> Thanks for any known methods
> 
> J. Bouquet
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"


Updated to a slightly-less-than-full GENERIC.  Still dumped core.  Moved loader.conf out of
the way, works fine.  What will take some time now is moving loader.conf back piece by piece
[until/if there is/ever was a utility to do it for us... ] to find the problematic line or two, then
resume testing of the install of the custom kernel that also is 'fail' status at this point... unless/until
I decide to also test it, THEN resume the loader.conf line-by-line back in...

tl;dr   loader.conf problematic line and maybe an additional unknown in either kernel text file.