Hello,
a number of typos and other mistakes have been found in my original
UTF-8 book patch. Many thanks to Randy and Archaic for reading the whole
thing. The corrected patch is at:
http://www.linuxfromscratch.org/~alexander/patches/lfs_book-r7236-utf8-1.patch
Issues dealt with:
* almost
Archaic wrote:
In order to make LFS usable in UTF-8 locales, and different man
program was chosen, man-DB. That program requires a database backend.
It can support GDBM or Berkeley DB.
Let me play dumb here for a minute: Why? ;-)
Would it be possible to do something similar to what we did
Hi all!
I'm still using LFS 5 on my desktop computer (Athlon XP 2800+) and now
I'm thinking of installing it on my laptop too. My laptop is a Athlon 64
CPU and I like to know if is already possible to a newby like me to
build the full system for 64 bits?
I now how to compile applications,
Hi all!
I'm still using LFS 5 on my desktop computer (Athlon XP 2800+) and now I'm
thinking
of installing it on my laptop too. My laptop is a Athlon 64 CPU and I like to
know
if is already possible to a newby like me to build the full system for 64 bits?
I now how to compile applications,
We have all the necessary information in cross-lfs.
http://www.linuxfromscratch.org/clfs/
--
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
LFS User # 2577
Registered Linux User # 299986
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe:
On Tue, 2005-12-27 at 16:02 -0200, Renato Riolino wrote:
Hi all!
I'm still using LFS 5 on my desktop computer (Athlon XP 2800+) and now
I'm thinking of installing it on my laptop too. My laptop is a Athlon 64
CPU and I like to know if is already possible to a newby like me to
build the
On Tue, Dec 27, 2005 at 06:33:57PM +0500, Alexander E. Patrakov wrote:
Links-2.1pre17: no way to properly configure for UTF-8 based character
cell display, there is no UTF-8 terminal encoding in the menu. If run on
the framebuffer console, doesn't properly accept keystrokes. If run from
X
On 12/27/2005 01:50, Alexander E. Patrakov wrote:
snip explanation
That was very thorough, thank you.
While it would be nice to avoid another dependency the reality is that I
usually end up with both GDBM and BDB on my systems. Yea, I know that's
not really an argument... To me the most
Jason Gurtz wrote these words on 12/27/05 13:52 CST:
It is worrisome about the seemingly ever-changing API, but not always
upgrading to the latest BDB could help alleviate that. They don't seem to
have a bad history of many security updates that would necessitate
upgrading often. :)
On 12/26/05, Ken Moffat [EMAIL PROTECTED] wrote:
I've been attempting to run an ICA on my CLFS ppc builds (CLFS from
20051214, but modified to also build a minimal 64-bit toolchain in
/opt/kgcc because the cpu is a G5). So, my observations have very
little to do with the alphabetical branch
Dan Nicholson wrote:
Did LFS use to build bison and flex in /tools?
When we used HJL binutils (before FSF binutils supported TLS/NPTL), yes.
HJL binutils require bison and flex (or at least, they used to).
signature.asc
Description: OpenPGP digital signature
--
Hello world,
It seems that XFree86-4.5.0 has issues with coreutils-5.92. The build
fails like this
DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API AuWrite.c
rm -f libXau.a
ar clq libXau.a AuDispose.o AuFileName.o AuGetAddr.o AuGetBest.o
AuLock.o AuRead.o AuUnlock.o AuWrite.o
On Wed, 28 Dec 2005, Andrew Benton wrote:
Hello world,
It seems that XFree86-4.5.0 has issues with coreutils-5.92.
Do you mean 5.92 ? LFS-svn has been on 5.93 for a few weeks, and some
of the behaviour is definitely different between the two versions.
Ken
--
das eine Mal als Trag�die,
On Tue, 27 Dec 2005, Dan Nicholson wrote:
bison, perl, vim - for me, these differ between my second and third
builds, but not for my third and fourth, nor for the first and second -
I guess this is the whole point of ICA and the build will be assumed
guilty unless an explanation can be
Archaic wrote:
On Tue, Dec 27, 2005 at 06:33:57PM +0500, Alexander E. Patrakov wrote:
Links-2.1pre17: no way to properly configure for UTF-8 based character
cell display, there is no UTF-8 terminal encoding in the menu. If run on
the framebuffer console, doesn't properly accept keystrokes. If
Randy McMurchy wrote:
This package doesn't work correctly in UTF-8 based locales.
This can never be placed on a BLFS page. Something needs to be
placed on the page that accurately describes the breakage, or
limited functionality you *may* see. Doesn't work correctly
is simply too vague.
[snip
Thomas Pegg wrote:
DJ Lucas wrote:
http://www.linuxfromscratch.org/~dj/blfs-xorg7/x/xorg7.html
EXAMPLE ONLY...none of it has been tested at all. It's only there to
show one possible screen/book layout, IMO the most presentable. I'll
beat it into shape over the next few days as I build it
17 matches
Mail list logo
