This may be of interest here… - Hubert
> Hi, > > I have played though the „rebuilding“ steps, and got things going with a few > minor changes. > First the result: > > ls -l `pwd`/g4u*fs > -rw-r--r-- 2 feyrer staff 1474560 Mar 17 19:27 > /home/feyrer/work/NetBSD/cvs/src-g4u.v3-deOliviera/src/distrib/i386/g4u/g4u1.fs > -rw-r--r-- 2 feyrer staff 1474560 Mar 17 19:27 > /home/feyrer/work/NetBSD/cvs/src-g4u.v3-deOliviera/src/distrib/i386/g4u/g4u2.fs > -rw-r--r-- 2 feyrer staff 1474560 Mar 17 19:27 > /home/feyrer/work/NetBSD/cvs/src-g4u.v3-deOliviera/src/distrib/i386/g4u/g4u3.fs > -rw-r--r-- 2 feyrer staff 1474560 Mar 17 19:27 > /home/feyrer/work/NetBSD/cvs/src-g4u.v3-deOliviera/src/distrib/i386/g4u/g4u4.fs > ls -l `pwd`/g4u.iso > -rw-r--r-- 2 feyrer staff 6567936 Mar 17 19:27 > /home/feyrer/work/NetBSD/cvs/src-g4u.v3-deOliviera/src/distrib/i386/g4u/g4u.iso > ls -l `pwd`/g4u-kernel.gz > -rw-r—r-- 1 feyrer staff 6035680 Mar 17 19:27 > /home/feyrer/work/NetBSD/cvs/src-g4u.v3-deOliviera/src/distrib/i386/g4u/g4u-kernel.gz > > My build environment: > > - uname -a: NetBSD vmnetbsd.promi.se 7.0_STABLE NetBSD 7.0_STABLE (GENERIC) > #0: Tue Nov 8 22:19:10 CET 2016 > feyrer@promise.local:/Users/feyrer/work/NetBSD/cvs/src-7/obj.amd64/sys/arch/amd64/compile/GENERIC > amd64 > > Note that I usually cross-build from Mac OS X. No changes for g4u-build > were needed, no removeing -m64 etc. > Note this is on NetBSD 7.0 (stable) for amd64, not i386. > > - Sources checked out as documented, with an added „-P“ to remove empty > directories. If you have checked-out sources, you can get this with „cd …/src > ; cvs up -P -d“. The latter will also create new directories if needed. > > Now about what I had to change in sources from 20170418: There were a bunch > of variables that could possibly be used uninitialized. > God knows why this was not fixed in the sources, but the attached patch does > this. > To apply, something like the following should work: > > cd …/src > patch -p0 <…/diff-out.txt > > As you have already mentioned, in g4u-build, „G4U_BUILD_KERNEL=true“ is > needed. > > So altogether, this doen’t look as bad as I feared. > Let me know if this helps, then I can see into updating the build > instructions. > > > - Hubert >
Index: sys/dev/acpi/fujhk_acpi.c
===================================================================
RCS file: /cvsroot/src/sys/dev/acpi/fujhk_acpi.c,v
retrieving revision 1.4
diff -u -r1.4 fujhk_acpi.c
--- sys/dev/acpi/fujhk_acpi.c 23 Apr 2015 23:23:00 -0000 1.4
+++ sys/dev/acpi/fujhk_acpi.c 17 Mar 2018 18:35:15 -0000
@@ -243,7 +243,7 @@
{
struct fujitsu_hk_softc *sc = arg;
const int max_irb_buffer_size = 100;
- uint32_t irb;
+ uint32_t irb=0; /*HF*/
int i, index;
for (i = 0; i < max_irb_buffer_size; i++) {
Index: sys/dev/acpi/pckbc_acpi.c
===================================================================
RCS file: /cvsroot/src/sys/dev/acpi/pckbc_acpi.c,v
retrieving revision 1.35
diff -u -r1.35 pckbc_acpi.c
--- sys/dev/acpi/pckbc_acpi.c 18 Oct 2016 22:08:30 -0000 1.35
+++ sys/dev/acpi/pckbc_acpi.c 17 Mar 2018 18:35:30 -0000
@@ -234,7 +234,7 @@
static void
pckbc_acpi_intr_establish(struct pckbc_softc *sc, pckbc_slot_t slot)
{
- struct pckbc_acpi_softc *psc;
+ struct pckbc_acpi_softc *psc = NULL; /*HF*/
isa_chipset_tag_t ic = NULL;
void *rv = NULL;
int irq = 0, ist = 0; /* XXX: gcc */
Index: sys/dev/ic/rtsx.c
===================================================================
RCS file: /cvsroot/src/sys/dev/ic/rtsx.c,v
retrieving revision 1.2
diff -u -r1.2 rtsx.c
--- sys/dev/ic/rtsx.c 29 Oct 2014 14:24:09 -0000 1.2
+++ sys/dev/ic/rtsx.c 17 Mar 2018 18:35:35 -0000
@@ -199,7 +199,7 @@
bus_space_handle_t ioh, bus_size_t iosize, bus_dma_tag_t dmat, int flags)
{
struct sdmmcbus_attach_args saa;
- uint32_t sdio_cfg;
+ uint32_t sdio_cfg = 0; /*HF*/
sc->sc_iot = iot;
sc->sc_ioh = ioh;
@@ -917,7 +917,7 @@
rtsx_read(struct rtsx_softc *sc, uint16_t addr, uint8_t *val)
{
int tries = 1024;
- uint32_t reg;
+ uint32_t reg = 0; /*HF*/
WRITE4(sc, RTSX_HAIMR, RTSX_HAIMR_BUSY |
(uint32_t)((addr & 0x3FFF) << 16));
> > > >
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ g4u-help mailing list g4u-help@feyrer.de https://lists.sourceforge.net/lists/listinfo/g4u-help
