Hi and great product
I normally use linux as the recovery boot environment but I like to make my own stuff instead of using ready made ones ( for specific customization and lighter images).
Made my own boot image using buildroot (standard glib, 32bit, kernel 4.18) and among others I added tbirest to the image and compiled in also the required libraries and the resulting image is quite small (<10MB) also including other stuff I need. The binary tbirest (latest 3.24) is also linked against both libncursesw.so.5 and libtinfo.so.5.
My question is would be possible for you to make available a binary which doesn't link against both of them? Normally and lately the terminfo functionality is included in libncurses, so only a single lib is required. Also, the linking is made against different char versions of libraries (libncursesw -> wide-char and libtinfo->standard), so if for some reason that terminfo is required as a separate lib at least to use the same char-ness).
This is only for convenience when doing stuff like this, the extra step of rebuilding ncurses again with --enable-wide is not that much...
Thank you.
Image for Linux custom boot image
-
- Posts: 3598
- Joined: Thu May 05, 2011 10:37 pm
Re: Image for Linux custom boot image
you're correct, looks like tinfo isn't needed any more.
But do be warned if building your own ncursesw, there are bugs that were
fixed. I think they were reported to the group but found the text that
fixed the issue:
If HAVE_WCTOB is not defined but HAVE_WCTOMB is (and better be, missing
#error as result is undefined in that case) then when _nc_is_charable is
callled in charable.c it calls _nc_to_char which then uses the wctomb
function and assumes the returned mb string will have a z-term but it may
not (and didn't), so the strlen check is no good.
"iondoe" wrote in message news:15964@public.image...
Hi and great product
I normally use linux as the recovery boot environment but I like to make my
own stuff instead of using ready made ones ( for specific customization and
lighter images).
Made my own boot image using buildroot (standard glib, 32bit, kernel 4.18)
and among others I added tbirest to the image and compiled in also the
required libraries and the resulting image is quite small ( wide-char and libtinfo->standard), so if for some reason
that terminfo is required as a separate lib at least to use the same
char-ness).
This is only for convenience when doing stuff like this, the extra step of
rebuilding ncurses again with --enable-wide is not that much...
Thank you.
But do be warned if building your own ncursesw, there are bugs that were
fixed. I think they were reported to the group but found the text that
fixed the issue:
If HAVE_WCTOB is not defined but HAVE_WCTOMB is (and better be, missing
#error as result is undefined in that case) then when _nc_is_charable is
callled in charable.c it calls _nc_to_char which then uses the wctomb
function and assumes the returned mb string will have a z-term but it may
not (and didn't), so the strlen check is no good.
"iondoe" wrote in message news:15964@public.image...
Hi and great product
I normally use linux as the recovery boot environment but I like to make my
own stuff instead of using ready made ones ( for specific customization and
lighter images).
Made my own boot image using buildroot (standard glib, 32bit, kernel 4.18)
and among others I added tbirest to the image and compiled in also the
required libraries and the resulting image is quite small ( wide-char and libtinfo->standard), so if for some reason
that terminfo is required as a separate lib at least to use the same
char-ness).
This is only for convenience when doing stuff like this, the extra step of
rebuilding ncurses again with --enable-wide is not that much...
Thank you.
Re: Image for Linux custom boot image
Thanks for the quick reply,
Would be possible for you to compile tbirest & imagel as such that they:
1. either don't depend on mixed char-ness
2. or link only against libncurses(or libncursesw) that has libtinfo(libtinfow) included?
As it is now, both binaries (v3.24) link against libtinfo (standard char) and libncursesw (wide char).
Would be possible for you to compile tbirest & imagel as such that they:
1. either don't depend on mixed char-ness
2. or link only against libncurses(or libncursesw) that has libtinfo(libtinfow) included?
As it is now, both binaries (v3.24) link against libtinfo (standard char) and libncursesw (wide char).