up to yesterday, i never had problems with the charsets, but now i
finally could convince one of my customers to use linux on a new desktop
machine. up to now, i just use linux for servers, mostly lfs and the
desktops are running windows. most customers require one or another
proprietary softwa
> And this may very well be the issue, since nobody has reported this
> problem when building LFS before.
not quite true!
i had issues with perl, but everyone on this list told me i made a
mistake. as i couldn't track the problem down to it's realy cause, i
just gave up argueing. and the docs a
Mike Johnston schrieb:
> Hello,I have a LFS system with a read only file system. I have
> /etc/udev/rules.d a symlink to a read/write partition. The
> 70-persistent-net.rules file gets generated and keeps on growing for every
> reboot. If i make the root filesystem read/write, this file does
Mike Johnston schrieb:
> Thank you.
> That would work however, I want to make 30 instances for 30 machines. I need
> to generate the 70-persistent-net.rules file so each machine has fixed
> interface names.
you don't need a 70-persistent-net.rules file.
as you are writing in plural, you have
Dr.-Ing. Edgar Alwers schrieb:
> Hi,
>
> building gstreamer-0.10.24 with make version 3.82 ends with an make error:
>
> "Makefile: 878: *** missing separator (did you mean TAB instead of 8
> spaces?). Stop "
> make: *** [all] Error 2"
make requires tabs, not spaces. this is documented quite a
> Rosario Turco virgilio.it> writes:
remove the following blanks (^) and add the missing \
>> ../glibc-2.12.1/configure --prefix=/tools \
>> --host = $ LFS_TGT --build =$(../ glibc-2.12.1/scripts/config.guess) \
^ ^ ^ ^ ^
>> --disable-profile --enable-add-ons \
>> --e
firefox 3.6.16 fails on "make" with "nsEnumeratorUtils.cpp"
with gcc 4.5.2 i had no problem. (i just testet my scripts sucessfully
with gcc 4.5.2 and now restarted again with just replacing gcc 4.5.2
with 4.6.)
i tried firefox 4.0 with no success
it fails alreday during configure with
"cant't fin
running the "certificate authority certificates" scripts from blfs my
system fails with some certificates.
as i learned this is not a coreutils bug but a kernel problem. is there
a solution for 32bit kernels or do i have to rebuild with 64bit?
thanks
tobias
--
http://linuxfromscratch.org/mailman
baldu...@units.it schrieb:
>
> are you sure that xinetd is picking libtirpc up?
>
> pmap_{set,unset} are in libtirpc and in order to force the xinetd build
> process to link in libtirpc I had to:
>
> export LDFLAGS="-ltirpc"
that's it. now libtirpc is linked.
but now i get the next error
last time (3 days ago) i compiled gcc 4.6.2 on this machine (intel
i7-2600 with 8gb ram) the compile run 2 minutes, the tests 16min.
as far as i can see, i used the 7.0 release almost to the letter...
(i upgraded the kernel and kernel-headers to 3.1.4)
using this 7.0 system as base, i wanted to r
mpfr configure fails with:
...
checking for recent GMP... yes
checking for __gmpz_init in -lgmp... no
configure: error: libgmp not found or uses a different ABI (including
static vs shared).
Please read the INSTALL file -- see "In case of problem".
libgmp seems to be properly installed:
ld.so.
Bruce Dubbs schrieb:
> Tobias Gasser wrote:
>> mpfr configure fails with:
>>
>>
>> ...
>> checking for recent GMP... yes
>> checking for __gmpz_init in -lgmp... no
>
> I'm not sure what's happening, but I have:
>
> $ nm /usr/l
Bruce Dubbs schrieb:
>> checking for recent GMP... yes
>> checking for __gmpz_init in -lgmp... no
>
i had a typo with the 'adjust'. thus ld was searching the wrong
places... meanwhile the basic system is up and running
tobias
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: htt
i still have the errors in the gmp tests.
as the book says the tests are critical, i'd like to fix them. but as
already mentionned, google was no help - at least not for me.
is anybody else able to reproduce the errors?
tobias
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: ht
-space, or you'll have not the same but
a comparable problem again...
mit freundlichen grüssen
tobias gasser
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
why are the CC= AR= RANLIB= not set for glibc?
as far i can understand, glibc will be built with the hosts compiler and
not with the new one build in 5.5 as the new one didn't install
reachable with the PATH-variable.
in 5.8 binutils and 5.9 gcc will be built with the new compiler by
specifying t
Andrew Benton schrieb:
> On Thu, 21 Jun 2012 11:57:19 +0100
> Tobias Gasser wrote:
>
>> why are the CC= AR= RANLIB= not set for glibc?
>
> To quote from the glibc page
> http://www.linuxfromscratch.org/lfs/view/development/chapter05/glibc.html
>
> "--hos
Jeremy Henty schrieb:
> Can I be sure that GRUB2's hd0, hd1 etc. will always correspond to the
> same physical SATA connectors on the motherboard, no matter what
> hardware I plug in? (I know from experience that /dev/sda does not
> always map to the same connector.) If not, how can I
i'm going to upgrade some machines with Asrock A330GC boards with
Dual-Core Atom 330 processors.
they all are running lfs dated may 2011, kernel 2.6.39, gcc 4.5.2.
i built current dev without any problems, but booting was impossible.
grub does not show anything. after the bios messages i just hav
Am 03.09.2012 19:24, schrieb Israel Silberg:
> And another question, if I want in the end tohave a LFS or BLFS system
> without gcc in it, shold I keep it in the toolchain or should I remove it
> when the system is done?
i just add
--bindir=${DEVLOP}
--sbindir=${DEVLOP}
to the following pac
Baho Utot schrieb:
>
> I always build all of LFS with -j4 or -j8 and it has not failed me.
>
so you just had very very much luck on your way...
there are packages which CAN fail with parallel builds.
whenever i run into a problem, i just restart the package with -j1 which
often solved the prob
version 0.9.8 compiles fine, but the new 0.9.9 fails with
gcc -DHAVE_CONFIG_H -I. -I.. -I../src -I../src -g -O2 -Wall -ansi
-pedantic -Wextra -Wstrict-prototypes -Wmissing-prototypes
-Wwrite-strings -Wno-variadic-macros -MT
check_thread_stress-check_thread_stress.o -MD -MP -MF
.deps/check_
Am 12.11.2012 11:15, schrieb Tobias Gasser:
> /STAGE1/lib/gcc/x86_64-unknown-linux-gnu/4.7.2/../../../../x86_64-unknown-linux-gnu/bin/ld:
> note: 'pthread_create@@GLIBC_2.2.5' is defined in DSO
> /STAGE1/lib/libpthread.so.0 so try adding it to the linker command line
i
the book copies the rpc headers to the host system. to avoid changeing
the host, i use the same sed as in chapter 6
sed -e 's##"rpc/types.h"#' \
-i sunrpc/rpc_clntout.c
i guess this should be changed in the book
tobias
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: ht
Am 12.11.2012 19:10, schrieb Bruce Dubbs:
>
> check is only built in Chapter 5 and you don't mention your host system.
lfs/blfs about 3 weeks old
>I've seen the error before in BLFS and figured it was a mismatch in
> autotools and used something similar to your workaround above.
i use a gl
Am 12.11.2012 19:15, schrieb Bruce Dubbs:
>
> Possibly, but the book is really only adding some headers to the host
> system. The problem should only come up when using LFS-7.1 as a host.
ok. not really a problem.
except for the system requirements like {d,b}ash or {g,}awk there is no
other pa
since about 1 year i am using the same harddisk. as the procution system
is a little outdated now, i wanted to make a 'fresh' disk.
to boot from this disk i had to start an ubuntu livecd and install grub
from this cd. the systems (i have built both 32bit and 64bit) can boot
and run fine.
but i
Am 13.11.2012 03:20, schrieb Bruce Dubbs:
what i missed in my original message:
/sda1 is ext2
/sda2 and /sda3 are ext3 (first attempt was with ext4, but as grub
didn't work i made backups, reformatted with ext3 and restored).
> If /boot is a separate partition, then the linux lines should look
Am 13.11.2012 18:08, schrieb Bruce Dubbs:
> Tobias Gasser wrote:
>> Am 13.11.2012 03:20, schrieb Bruce Dubbs:
>>
>> what i missed in my original message:
>> /sda1 is ext2
>> /sda2 and /sda3 are ext3 (first attempt was with ext4, but as grub
>> didn't wo
Am 13.11.2012 20:26, schrieb Bruce Dubbs:
> OK, so I now understand that both sda2 and sda3 are lfs systems.
sorry for not being clear...
and sda1 is /boot for both systems
> What I suggest doing is
>
> mount -v /dev/sda1$LFS/boot
> mount -v --bind /dev $LFS/dev
as mentionned, that is what
Am 14.11.2012 00:26, schrieb Bruce Dubbs:
>
> I don't know what is going on. How is the disk partitioned?
>
> fdisk -l /dev/sda
bash-4.2# fdisk -l
Disk /dev/sda: 300.1 GB, 300069052416 bytes, 586072368 sectors
Units = Sektoren of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes /
> You should have /boot/grub/i386-pc/core.img.
this file exists.
> First, check that /usr/sbin/grub-install and
> /usr/share/grub/grub-mkconfig_lib exist. I suspect that is OK.
yes.
> Reading through grub-install, at line 336. we should have:
[...]
> Hopefully some of the above will help you
> You should have /boot/grub/i386-pc/core.img.
yes. it's size is 26433
> grub-install is a script. Lets try to look at that to see if we can
> figure it out. Adding a few echo commands can confirm some of the
> settings. You can also try 'grub-install --verbose /dev/sda'. You may
> want to a
Am 16.11.2012 12:06, schrieb Tobias Gasser:
> i now run "grub-install /dev/sda" with my inserted line 717.
> i'll be back in either 2 minutes after sucessful reboot, or 15 minutes
> id i have to use the live-cd to reinstall grub...
still the same. i just get the grub-rescu
> Reading back, my sentence could be misleading, so, to be clear, I was
> referring LO to build size, not install size (Bruce just pointed out
> this, but I feel it needed to be close to my own statement). For install
> size, it is about the same as OpenJDK, over 440MB, build size also the
> same o
Am 21.11.2012 14:38, schrieb Fernando de Oliveira:
> I thought in stripping it, but I am still not sure if any problem would
> appear. What is the command you used to strip?
i use DESTDIR on all packages, so i can loop thru all files in DESTDIR
to (re)compress all manpages, strip all binaries a
version 8.20 is available since oct 23.
lfs-book has a ticket for it: 3215
searching the lists just show the ticket, but no further comments so far.
the ticket says 'no announce yet', here it is:
http://lists.gnu.org/archive/html/coreutils-announce/2012-10/msg0.html
+ bugfix release
+ speed
My error with this page, even after having built one or two versions of
LFS, was that the last line:
"gcc compilation OK"
that made me ignore the other lines, when some of these lines were
telling me that I had requirements to fix.
I thought: "all right, host can compile, so the other lines are
Am 05.01.2013 18:39, schrieb Bruce Dubbs:
> The idea of the script was that it should be short. Generally the
> problem is that the symlinks are not set and occasionally makeinfo is
> not installed. Rarely is the problem an out-of-date executable.
agree.
so why not check just the very importan
> AWK=`readlink -f /usr/bin/awk`
> awk=/usr/bin/awk
> [ "$AWK" == "/usr/bin/gawk" ] || die "$awk is not a symlink to gawk"
some distros started to drop the /usr hierarchy
the script should be a little smarter to accept the files not only in
/usr/bin but just anywhere in $PATH
something like
Am 22.02.2013 22:50, schrieb Frans de Boer:
> I understand that gperf is not required - it would be mentioned
> otherwise does it?
yes. gperf is NOT required for glibc (or any other package in lfs)
and yes, all requirements are mentionned.
> However, I am not the first nor probably the last runni
Am 22.02.2013 23:29, schrieb Frans de Boer:
>
> Just search for "gperf glibc lfs". It is even on the archives by LFS.
>
thanks. i've got it.
so you really are not the first...
but the first part of my last message is stil valid: i never had to
build gperf in lfs.
tobias
--
http://linuxfrom
Am 22.02.2013 23:56, schrieb Bruce Dubbs:
> Looking at the glibc source, gperf only appears to arise from locale
> issues. It would appear that you did not set up the lfs user in
> accordance with the book:
>
> LC_ALL=POSIX
>
> No other LC_* or LANG settings should be set.
>
yep!
reading your r
Am 26.02.2013 15:24, schrieb Rick Berube:
>>
>
> Just as a guess, I moved gmp to the Real Machine and re-attempted the
> process. This time it was successful. I would infer that LFS doesn't
> play well on virtualized hosts.
>
> Thanks.
>
i use qemu since about 6 months. before i used virtualbox
>
> I'm sorry Mr. Bruce, I missed it.
> here is the result
> -
> root:/sys/class/net# dmesg|grep eth0
> [2.611331] via-rhine :00:12.0: eth0: VIA Rhine II at 0xfdffe000,
> 00:e0:4d:56:48:0a, IRQ 23
> [2.612057] via-rhine :00:12.0: eth0: MII PHY found at address 1,
> sta
Manuel Gonzalez Montoya schrieb:
>
> root [ ~ ]# ls -l /dev/null
> crw-rw 1 root root 1, 3 2008-03-24 12:44 /dev/null
>
something's wrong with your udev installation:
in /etc/udev/rules.d/25-lfs.rules
you have an line with
KERNEL=="null", MODE="0666"
1) you've missed to install t
David Kredba schrieb:
> I used the current SVN version of the LFS book.
>
> The util-linux-ng version is 2.13.1.
same version here
> I am using UNICODE="1" in /etc/sysconfig/console and LANG is set
> to cs_CZ.UTF-8.
LC_ALL=de_DE.UTF-8
LANGUAGE=de
LANG *unset*
/etc/sysconfig/console
UNICODE=yes
Spahn, Daniel schrieb:
> Correction!
> I read a little more carefully. You have not compiled the correct
> drivers for your SCSI hard drive into the kernel. You can run lspci,
> then make menuconfig (In a different terminal) and match up the SCSI
> drive characteristics with a driver, most likely i
>
> swapon: cannot stat dev/sda3: no such file or directory
> fsck.ext3: No such file or directory while trying to open /dev/sda4
>
> I suspect this is due to my grub configuration. Rather than installing
> grub, I added these lines to menu.lst on my host system:
>
> title LFS 6.3
> root (hd0,
>
> 00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE
> Controller (rev 02)
> 00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller
> (rev 02)
>
> I assume the first device is my DVD/CDRW, so the other must be my
> harddisk. Based on this, should I build t
> Root-FFS: No NFS server available, giving up
> VFS: Unable to mount root fs via NFS, trying floppy
> VFS: Cannot open root device "sda4" or unknown-block(2,0)
> Please append a correct "root=" boot option; here are the available
> partitions
> 0300 156290904 hda driver: ide-disk
> 0301 102398278
> Changing sda->hda in menu.lst an fstab allows me to boot, though it
> still displays hda. The proper sata driver is built into the kernel.
> From your post, it sounds like I probably have an older drive that's
> taking precedence over the sata, which is causing this problem?
>
> Just for
Michael schrieb:
> I'm going through Linux From Scratch v6.4, and I'm on Chapter 8.4.
> Currently, I'm running Linux completely off of an external hard drive, while
> I'm also building my Linux From Scatch build onto a seperate partition on
> that disk. The laptop already has one hard drive in
> A good package manager is, IMO, a necessity.
NO
i'll explain why i NEVER will use any package-manager:
have a look at the configure options with php5:
depending on what other packages i've alread installed, the php package
will contain the mcrypt/mhash ONLY IF NEEDED, same with mysql or
> I'm a little surprised at the vehemence of your statement.
> Why are you so excited by my opinion which applies only to
> the machines I own that you used four exclamation marks?
sorry, i didn't want to offend anybody.
> ISTM that you have relatively little contact with
> reasonable version con
Tushar Teredesai schrieb:
> On Fri, Mar 20, 2009 at 3:01 AM, Tobias Gasser wrote:
>> i'll explain why i NEVER will use any package-manager:
>>
>
> Looks like you have based your comments based primarily on package
> management used by "binary distros"
> This is a reasonable working definition from the viewpoint of the
> user, it does not describe a package manager from the perspective
> of the developer.
finally that's it. you found the bug in my brain!
i can follow your arguments and will try extend my knowledge about
package management by
RaptorX schrieb:
> I wouldnt suggest to a newcomer to not follow the book but in general when
> it comes to directories it is true that is a matter of preference...
>
> now you cannot forget about it because when in the book says go to
> /mnt/lfs/tools you should go to the folder you created to re
> now, I have a SATA drive 250GB, and my usb of 4GB. Those are the two
> HardDrives that my pc should recognice.
> CONFIG_SATA_PMP=y
> CONFIG_SATA_AHCI=y
you probably don't have the right sata driver.
the only one you're building is the generic AHCI driver which supports
most of the newer sata c
> check your bios setings and be shure to have it setup correct. sata must
>> be native, not raid or whatever other options are available. ahci
>> usually is only available in native mode.
>
>
> This should be optional right?
yes.
> this is in case I want to use the AHCI drivers... am I correc
as the sendpage-problem seems to be a serious vulnerability in the
kernel, i propose to add a paragraph in the errata-section and in the
kernel chapters (5.6.1 / 8.3). in my opinion even an update to lfs 6.5.1
(or 6.6 is subnumbering is not acceptable) would be ok.
i had no issues here building a
Bruce Dubbs schrieb:
>
> In the All Packages section is a note:
>
> "The Linux kernel is updated relatively often, many times due to discoveries
> of
> security vulnerabilities. The latest available 2.6.30.x kernel version should
> be
> used, unless the errata page says otherwise."
oops. i
try the following:
CC="$LFS_TGT-gcc -B/tools/lib/" \
AR=$LFS_TGT-ar \
RANLIB=$LFS_TGT-ranlib \
../glibc-2.11.1/configure --prefix=/tools \
--host=$LFS_TGT --build=$(../glibc-2.11.1/scripts/config.guess) \
--disable-profile --enable-add-ons \
--enable-kernel=2.6.18 --with-headers=/tools/i
Chris Staub schrieb:
> No...this is NOT necessary. If you "need" to add anything to the Glibc
> build instructions, you have missed something. There is absolutely no
> reason why the recently-built toolchain in /tools won't be used, if you
> followed the instructions. If any variables "need" to
Philippe Delavalade schrieb:
> Maybe a suggestion for those who read to quikly :
> five or six lines more in each chapter, something like
> cd /$LFS/sources
> tar -xvf package-version.tar.[gz|bz2]
> cd package-version
> ...
> cd ..
> rm -vfr package-version
> and eventually
> rm -vfr package-build
65 matches
Mail list logo
