Hi Scsijon,
please always address the list, as I hope we soon have enough new users again,
that they may also answer questions.
Also my other inboxes are rather crowded, so it becomes harder and harder to
stop individual things between all the other business, youtube, and spam.
This "MB_LEN_MAX wrong” message is also what others have already seen.
I have not yet time to look into this or debug where it is coming from and why.
You can probable touch a couple of this build logs, as some of those toolchain
builds are only to make sure we really have working tools, but your system
likely has a working m4, so … however, you might run into similar "MB_LEN_MAX
wrong” in other packages.
Let us know if you find out more.
René
On 06 Jan 2019, at 03:58, scsijon <[email protected]> wrote:
> I'll start with some basics
>
> On a new Build workstation>
> I created a complete T2 on a i5 system with the T2-9.0-r47356.iso
> I have three partitions
> -/
> -swap
> -/develop
> The T2 is loaded on the / partition
> This workstaion has NO external connection (deliberately)!
>
>
> I created a copy of T2-trunk at r47466 on the /develop from a portable drive
> I updated earlier, running ./scripts/Config -cfg t290-64, and
> ./scripts/Download -cfg t290-64 -required first to download the required
> packages. This will eventually supply the compiled packages for a new Puppy
> Linux called T290.
>
> As you know, I have problems with your site so have used the '-mirror none'
> setting to get sources, there were some errors, I have already mailed you
> about these separately.
>
> On the new Build workstation
> >I added my t290-64 target files to the target directory on /develop
>
> On a reboot and a cd to /develop/t2-trunk
> >I re-ran ./scripts/Config -cfg t290-64 and ./scripts/Download -cfg t290-64
> >-required to ensure everything was in place for the build without errors
> >appearing.
> >I then started ./scrips/Build-Target -cfg t290-64.
>
> >Initially it first failed at 0-linux-header, but with a ./scripts/Cleanup
> >-cache it restarted sucessfully.
>
> >It is now failing repeatedly at 0-m4 and I need some help
>
> Error message section is
> -------------------------------------
> make[3]: Entering directory
> '/develop/t2-trunk/src.m4.t290-64.20190106.102933.29163.localhost/m4-1.4.18/lib'
> CC gl_avltree_oset.o
> CC binary-io.o
> CC c-ctype.o
> CC c-stack.o
> CC c-strcasecmp.o
> CC c-strncasecmp.o
> CC clean-temp.o
> In file included from /usr/include/stdlib.h:1014,
> from ./stdlib.h:36,
> from clean-temp.c:29:
> /usr/include/bits/stdlib.h: In function 'wctomb':
> /usr/include/bits/stdlib.h:90:3: error: #error "Assumed value of MB_LEN_MAX
> wrong"
> # error "Assumed value of MB_LEN_MAX wrong"
> ^~~~~
> make[3]: *** [Makefile:1910: clean-temp.o] Error 1
> make[3]: Leaving directory
> '/develop/t2-trunk/src.m4.t290-64.20190106.102933.29163.localhost/m4-1.4.18/lib'
> make[2]: *** [Makefile:1674: all] Error 2
> make[2]: Leaving directory
> '/develop/t2-trunk/src.m4.t290-64.20190106.102933.29163.localhost/m4-1.4.18/lib'
> make[1]: *** [Makefile:1572: all-recursive] Error 1
> make[1]: Leaving directory
> '/develop/t2-trunk/src.m4.t290-64.20190106.102933.29163.localhost/m4-1.4.18'
> make: *** [Makefile:1528: all] Error 2
> Due to previous errors, no 0-m4.log file!
> (Try enabling xtrace in the config to track an error inside the build system.)
> --- BUILD ERROR ---
> Creating file list and doing final adaptions ...
> Searching for orphaned files ...
> Found 5 files for this package.
> Found 0 orphaned files for this package.
> Clear (old) md5sums ...
> Creating md5sum files ... done.
> Creating package description ...
> Making post-install adaptions.
> -------------------------------------------
>
> A full log is attached
>
> Any ideas?
>
> regards
> scsijon
> <0-m4-ERROR-LOG.txt>
--
ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
DE Legal: Amtsgericht Berlin (Charlottenburg) HRB 105123B, Tax-ID#: DE251602478
Managing Director: René Rebe
http://exactcode.com | http://exactscan.com | http://ocrkit.com |
http://t2-project.org | http://rene.rebe.de
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
