Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Apr 2016 13:29:59 -0700 (PDT)
From:      "Jeffrey Bouquet" <jbtakk@iherebuywisely.com>
To:        "current" <current@freebsd.org>
Cc:        "current" <current@freebsd.org>, "kernel" <kernel@dollarmusicdownload.com>
Subject:   [Solved]  [WAS:libc build error]  Mostly all solved bw-iw-ik from 4-20-2016
Message-ID:  <E1atLEd-0001mu-8g@rmm6prod02.runbox.com>
In-Reply-To: <E1at3Yv-000201-5W@rmm6prod02.runbox.com>

next in thread | previous in thread | raw e-mail | index | archive | help


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

>=20
>=20
> On Wed, 20 Apr 2016 17:37:16 -0700 (PDT), "Jeffrey Bouquet" <jbtakk@ihere=
buywisely.com> wrote:
>=20
> >=20
> >=20
> > On Wed, 20 Apr 2016 12:28:29 -0400, Allan Jude <allanjude@freebsd.org> =
wrote:
> >=20
> > > On 2016-04-20 12:06, Jeffrey Bouquet wrote:
> > > > unistd
> > > >=20
> > > >=20
> > > > /usr/src/lib/libc/../../include/unistd.h:330:45: error: expected fu=
nction body after function declarator
> > > > int    execl(  .................................
> > > >                                                          332:46:=20=
=20=20=20
> > > > same...
> > > >=20
> > > > stops libc
> > > > otherwise clang36 seems to be building so far, if it builds unsure =
about installworld
> > > > _______________________________________________
> > > > freebsd-current@freebsd.org mailing list
> > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freeb=
sd.org"
> > > >=20
> > >=20
> > > The mailing list strips attachments. Can you upload it somewhere and
> > > provide a link
> > >=20
> > > --=20
> > > Allan Jude
> > > _______________________________________________
> > > freebsd-current@freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd=
.org"
> >=20
> >=20
> > Well, it is now r298350 Wed Apr 20...
> > However several problems
> >=20
> > SINGLE-USER BOOT PROBLEMS
> > 1... usual boot fails, this is single-user adjusted, but I cannot add s=
wap (swapon? swapctl?)
> > 1a...  the last time, it was fixed with using the old /kernel ...=20
> >=20
> > multi-user boot problems
> >=20
> > 2... the last usual boot dumped with vm_pager or something,  verbose bo=
ot times out with xpt_config not completing.
> > 2a.... could be a wrong setting is loader.conf, the nvidia.ko not yet u=
pdated (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 in=
dividually...=20
> >=20
> >=20
> > As one might surmise, I'd rather see buildworld made more foolproof tha=
n other recent improvements=20
> > (pkg, zfs, ...)
>=20
> 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 pr=
oblems (swap is present again)
> (multi-user boot works)=20
>=20
> Best practice maybe to update the kernel?  It is a custom one from way ba=
ck in 2004 initially
> without sound drivers and without debug symbols...  and many esoteric lin=
es added which I cobbled
> together at first then changed per diffs of GENERIC over the years...
>=20
> Thanks for any known methods
>=20
> J. Bouquet
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


Updated to a slightly-less-than-full GENERIC.  Still dumped core.  Moved lo=
ader.conf out of
the way, works fine.  What will take some time now is moving loader.conf ba=
ck piece by piece
[until/if there is/ever was a utility to do it for us... ] to find the prob=
lematic line or two, then
resume testing of the install of the custom kernel that also is 'fail' stat=
us 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 eit=
her kernel text file.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1atLEd-0001mu-8g>