Hi, 1. use configure to create a default configuration. give it any name you want. 2. select minimal x86 in config and leave everything as it is. 3. use download -required to download all packages ( requires a fair amount of coffee since the process is time consuming) 4. use ./scripts emerge-pkg -cfg yourconfig m4 to update your m4. 5. try rebuilding again.
the issue you are facing is that base minimal t2 is not in sync anymore with the current updated package list. We are struggling to create an updated 9.0 image but it seems we are not having enough time to finalize. regards, Iulian > Hello! > > While trying to build T2-TRUNK, that I synced today, using as the build > system a VM where I installed t2-8.0-minimal-x86_64.iso, I got the error > below, that I can't solve yet: > > == 18:37:34 =[0]=> Building base/autoconf [2.69 9.0-trunk]. > -> Preparing build in > src.autoconf.default.20131122.183732.11794.TCC-T2 > -> Building. Writing output to $root/var/adm/logs/0-autoconf.out > !> checking whether directories can have trailing spaces... yes > !> checking for expr... /usr/bin/expr > !> checking for GNU M4 that supports accurate traces... > configure: error: no acceptable m4 could be found in $PATH. > !> GNU M4 1.4.6 or later is required; 1.4.16 or newer is > recommended. > !> GNU M4 1.4.15 uses a buggy replacement strstr on some > systems. > !> Glibc 2.9 - 2.12 and GNU M4 1.4.11 - 1.4.15 have another > strstr bug. > !> Due to previous errors, no 0-autoconf.log file! > !> (Try enabling xtrace in the config to track an error inside > the build system.) > == 11/22/13 18:37:49 =[0]=> Aborted building package autoconf. > -> Unmounting loop mounts ... > > Any hints? > > Tks, > Josmar > >
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
