[lfs-support] check 0.9.9 (5.13) fails

2012-11-12 Thread Tobias Gasser
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_thread_stress-check_thread_stress.Tpo -c -o 
check_thread_stress-check_thread_stress.o `test -f 
'check_thread_stress.c' || echo './'`check_thread_stress.c
mv -f .deps/check_thread_stress-check_thread_stress.Tpo 
.deps/check_thread_stress-check_thread_stress.Po
/bin/sh ../libtool --tag=CC   --mode=link gcc  -g -O2 -Wall -ansi 
-pedantic -Wextra -Wstrict-prototypes -Wmissing-prototypes 
-Wwrite-strings -Wno-variadic-macros   -o check_thread_stress 
check_thread_stress-check_thread_stress.o ../src/libcheck.la 
../lib/libcompat.la  -lrt
libtool: link: gcc -g -O2 -Wall -ansi -pedantic -Wextra 
-Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings 
-Wno-variadic-macros -o .libs/check_thread_stress 
check_thread_stress-check_thread_stress.o  ../src/.libs/libcheck.so 
../lib/.libs/libcompat.a -lrt -Wl,-rpath -Wl,/STAGE1/lib
/STAGE1/lib/gcc/x86_64-unknown-linux-gnu/4.7.2/../../../../x86_64-unknown-linux-gnu/bin/ld:
 
check_thread_stress-check_thread_stress.o: undefined reference to symbol 
'pthread_create@@GLIBC_2.2.5'
/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
/STAGE1/lib/libpthread.so.0: could not read symbols: Invalid operation
collect2: error: ld returned 1 exit status


the only differences to the book are the build-path (i use /STAGE1 for 
years without problems) and the kernel version: i use 3.4. as it is a 
long-term kernel.

i don't understand why 'GLIBC_2.2.5' is referenced, as the host-system 
is lfs 7.2 with glibc 2.16.1 and the lib in /STAGE1/lib is glibc 2.16.1 too.

check 0.9.8 compiles fine.

any idea what's wrong?

thanks
tobias
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] check 0.9.9 (5.13) fails

2012-11-12 Thread Tobias Gasser
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 was a little hasty writing my previous mail.

adding

CFLAGS=-L/STAGE1/lib -lpthread make...

fixes the problem



configure confirms to miss libpthread, but does not throw an error!

checking whether unsetenv is declared... yes
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for gawk... /usr/bin/gawk

tobias




-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


[lfs-support] glibc 2.16.0 (5.7)

2012-11-12 Thread Tobias Gasser

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#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: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] Network interface drivers

2012-11-12 Thread Robin
On 12 November 2012 17:07, Oshadha Gunawardena oshadha.ro...@gmail.comwrote:

 Hi all,

 Where to find Intel DH67BL Linux drivers, specifically for network
 interface. Searched through Google and couldn't find it.

 Thanks.

 --
 http://linuxfromscratch.org/mailman/listinfo/lfs-support
 FAQ: http://www.linuxfromscratch.org/lfs/faq.html
 Unsubscribe: See the above information page

 LAN support: Gigabit (10/100/1000 Mb/s) LAN subsystem using the IntelĀ®
82579V Gigabit Ethernet Controller

e1000 driver kernel option

-- 
rob
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] Network interface drivers

2012-11-12 Thread Firerat
On 12 Nov 2012 17:07, Oshadha Gunawardena oshadha.ro...@gmail.com wrote:

 Hi all,

 Where to find Intel DH67BL Linux drivers, specifically for network
interface. Searched through Google and couldn't find it.

 Thanks.


I would be very surprised if it were not in the kernel.

Anyway, I checked Intel's site for manual, LAN is Intel 82579v so add Linux
kernel to a google search to get more

-- 
Firerat
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] GCC-4.7.1 - Pass 2 Error unrecognized command line option '-V' unrecognized command line option '-qversion'

2012-11-12 Thread Chris Staub
On 11/12/2012 10:25 AM, lei huang wrote:
 Linux  2.6.18-308.16.1.el5 #1 SMP Tue Oct 2 22:01:37 EDT 2012 i686
 i686 i386 GNU/Linux

 config.log

 FATAL: kernel too old

 help!!!

There's the problem - your host system doesn't have a recent enough 
kernel. You will need to upgrade the kernel to at least the minimum 
version specified on the Host System Requirements page.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] check 0.9.9 (5.13) fails

2012-11-12 Thread Bruce Dubbs
Tobias Gasser wrote:
 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 was a little hasty writing my previous mail.

 adding

 CFLAGS=-L/STAGE1/lib -lpthread make...

 fixes the problem

 configure confirms to miss libpthread, but does not throw an error!

 checking whether unsetenv is declared... yes
 checking for the pthreads library -lpthreads... no
 checking whether pthreads work without any flags... yes
 checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
 checking if more special flags are required for pthreads... no
 checking for gawk... /usr/bin/gawk

check is only built in Chapter 5 and you don't mention your host system. 
  I've seen the error before in BLFS and figured it was a mismatch in 
autotools and used something similar to your workaround above.

   -- Bruce

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] glibc 2.16.0 (5.7)

2012-11-12 Thread Bruce Dubbs
Tobias Gasser wrote:

 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#rpc/types.h#' \
   -i sunrpc/rpc_clntout.c


 i guess this should be changed in the book

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.

   -- Bruce
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] check 0.9.9 (5.13) fails

2012-11-12 Thread Tobias Gasser
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 global DESTDIR=xy which works fine on most packages. but with 
some packages i have to specify 'make DESTDIR=xy install' as the global 
variable seems to be overwritten somewhere. after hours of searching i 
gave up to understand why this happens...

with gcc i tried to find out why the french langauge files are built. i 
set LANGUAGE=de and LINGUAS=de de_CH de_DE en en_GB global in the 
profile. most packages do as expected, some just ignore it and build 
everything (--enable-nls) or nothing (--disable-nls), but gcc is very 
special by buildint as expected the local/de but adds the french 
language at least back until version 4.4. (i tried with de,it and got 
de,it plus fr)


tobias


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] glibc 2.16.0 (5.7)

2012-11-12 Thread Tobias Gasser
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 package where the host has to be modified. that's why i prefer the 
sed instead of copying the headers.

tobias






-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] Systemd's journal (was Re: Latest news in GNOME world)

2012-11-12 Thread Matt Burgess
On Mon, 2012-11-12 at 15:26 -0600, Bruce Dubbs wrote:
 Matt Burgess wrote:
  On Mon, 2012-11-12 at 11:56 -0600, Bruce Dubbs wrote:
 
  What advantages does systemd give?
 
  Binary logs?  That's a little difficult to work with if Xorg isn't
  working.  How do you grep a binary log?
 
  I was going to say 'me too' to all of your post, Bruce, but then, in
  trying to find the list of 18(!) guides on how to use the various
  components of systemd came across
  http://0pointer.de/blog/projects/journalctl.html which describes how to
  access the binary logs.  The features it provides all seem pretty neat
  and all accessible from the command line.  So, that's one less thing for
  me to hold against it.
 
 
 OK, let's discuss this.  My first comment is that when you have custom 
 programs like this, the author has to think about everything an admin 
 might ever want.  What if the admin wants something the author didn't 
 think about?

It's open source, they can just extend it :-)

 Second is that you are using different tools from other logs such as 
 apache, ftp, mail and any other application that writes a log.

From my brief reading, it looked as if, if the service is controlled by
systemd, the journal will collate its logs.  In this respect, it's a lot
like things like logstash (http://logstash.net/). I *think* logstash
keeps its own copy of the logs, thereby doubling logging capacity, and
then adds an indexing overhead as well.  Again, I *think* journalctl
just stores the one copy, and will presume it also needs additional
space for indexing.  Whilst logstash requires the admin to configure the
inputs, filters and outputs, it looks as though journalctl works out of
the box.

 Third, if the logs were ascii, the bells and whistles in the link above 
 could be accomplished with a bash script fairly easily.

Maybe my bash-fu is a bit rusty, but collating multiple sources of logs
together, then filtering them back out again to drill down with the
flexibility that journalctl provides would have me googling for a piece
of software to do it after about an hour, I think :-)

Note that for home-user systems, I wouldn't bother with journalctl at
all, but on the enterprise environment's I have to support, I'd want
something like this to make cross-service log analysis much easier.

 About the only really sensible argument is that binary logs use less 
 disk space.  In the days of TB drives, even that isn't a big deal.

I'm not sure I'd even class that as a sensible argument.  
 To me the whole systemd philosophy moves away from user knows best to 
 developer knows best.  That's just like MS and Apple.  The difference of 
 course is that systemd *is* open source and we don't have to use it.

No, we don't have to use it, and I'm still not suggesting anyone
does :-)  I'm just pointing out that I can see the utility in
journalctl.  My jury's still out on systemd's service and resource
management though; and I don't think you can have either resource or log
management without the service management component.

Regards,

Matt.

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-support] Systemd's journal (was Re: Latest news in GNOME world)

2012-11-12 Thread Aleksandar Kuktin
WARNING!! FLAMEBAIT!!!


On Mon, 12 Nov 2012 15:26:08 -0600
Bruce Dubbs bruce.du...@gmail.com wrote:

 Third, if the logs were ascii, the bells and whistles in the link
 above could be accomplished with a bash script fairly easily.

FLAMEBAIT, USE ASBESTOS!

Well, since UNIX and clones have survived all these years, I believe it
is safe to bet they will continue surviving. :) After all, sysvinit
itself has, what, 30 years under its belt?

-- 
   Fourth law of programming:
   Anything that can go wrong wi
sendmail: segmentation violation - core dumped
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


[lfs-support] Grub 2.0 problem

2012-11-12 Thread Tobias Gasser
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 can't install my own compiled grub as a boot-loader!


/dev/sda1 = /boot
/dev/sda2 = / (for 32bit)
/dev/sda3 = / (for 64bit)

/dev/sda4 = extended
/dev/sda5 = SWAP
/dev/sda6 = DATA


booting the system with ubuntus grub works fine. running grub install 
/dev/sda from a chroot (dev, proc, sys are mounted with --bind) says 
everyting is fine but booting results in the grub console with:

GRUB loading.
Welcome to GRUB!

error: disk 'hd0,msdos1' not found.
Entering rescue mode...


'ls' just shows a newline - an empty list!

rebooting the live-cd, reinstalling grub, putting my grub.conf into 
place - the system boots fine.

i built grub as in the book.

grub-install /dev/sda has no errors:
Installatoin finished. no error reported


grub from ubuntu can boot either partitions (32 or 64bit), so does grub 
from parted magic.

i tried both grub versions i built (32/64) but none can boot, both just 
enter the console as mentionned above.

grub.conf is very basic and works fine with grub from ubuntu and parted 
magic.

** cut
set root='(hd0,1)'
set timeout=10
insmod ext2
menuentry linux 32bit {
   linux /boot/kernel-3.4.18-t32 root=/dev/sda2
}
menuentry linux 64bit {
   linux /boot/kernel-3.4.18-t64 root=/dev/sda3
}
** cut





ubuntu installs into
/boot/grub and /boot/grub/locale where the modules are in /boot/grub

lfs has an additional /boot/grub/i386-pc where the modules are. i 
already copied all from /boot/grub/i386-pc to /boot/grub but no change.

the boot symlink exists as required for a boot partition.

google was no help - i probably don't know what to ask for...


i'm trying to get grub up now for more than a week and have no more 
ideas what i could try.

any help welcome!

tobias


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] Grub 2.0 problem

2012-11-12 Thread Bruce Dubbs
Tobias Gasser wrote:
 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 can't install my own compiled grub as a boot-loader!


 /dev/sda1 = /boot
 /dev/sda2 = / (for 32bit)
 /dev/sda3 = / (for 64bit)

 /dev/sda4 = extended
 /dev/sda5 = SWAP
 /dev/sda6 = DATA


 booting the system with ubuntus grub works fine. running grub install
 /dev/sda from a chroot (dev, proc, sys are mounted with --bind) says
 everyting is fine but booting results in the grub console with:

 GRUB loading.
 Welcome to GRUB!

 error: disk 'hd0,msdos1' not found.
 Entering rescue mode...


 'ls' just shows a newline - an empty list!

 rebooting the live-cd, reinstalling grub, putting my grub.conf into
 place - the system boots fine.

 i built grub as in the book.

 grub-install /dev/sda has no errors:
 Installatoin finished. no error reported

 grub from ubuntu can boot either partitions (32 or 64bit), so does grub
 from parted magic.

 i tried both grub versions i built (32/64) but none can boot, both just
 enter the console as mentionned above.

 grub.conf is very basic and works fine with grub from ubuntu and parted
 magic.

 ** cut
 set root='(hd0,1)'
 set timeout=10
 insmod ext2
 menuentry linux 32bit {
 linux /boot/kernel-3.4.18-t32 root=/dev/sda2
 }
 menuentry linux 64bit {
 linux /boot/kernel-3.4.18-t64 root=/dev/sda3
 }

If /boot is a separate partition, then the linux lines should look like:

linux /kernel-3.4.18-t64 root=/dev/sda3 ro

note the you don't specify /boot there.  From the viewpoint of grub, 
there is no /boot directory.

I suspect that you installed grub from ubuntu without /boot mounted as a 
separate partition.

One thing to do is to drop to the grub command line and do:

grub ls (hd0,1)

For the ubuntu instances, try:

linux (hd0,2)/boot/kernel-3.4.18-t32 root=/dev/sda2
linux (hd0,3)/boot/kernel-3.4.18-t64 root=/dev/sda3

The trick is to know which version of the grub configuration file is 
being used.  A simple 'grub install /dev/sda' will assume that it is 
using /boot/grub/grub.cfg from where /boot is located when the install 
is run.

Check this and let us know if you need more help.

   -- Bruce
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page


Re: [lfs-support] Network interface drivers

2012-11-12 Thread Oshadha Gunawardena
This page has some drivers but I'm not sure if it compatible with my kernel
version (3.5.x)

http://www.intel.com/support/network/sb/CS-006120.htm

Linux* kernel versions 2.4.18 through 2.6.x.*
Linux kernel versions 2.4.18 through 2.6.x.*
Linux kernel version 2.2.20 through 2.4.16

These three were mentioned in the above Intel page.

Any ideas?


On Mon, Nov 12, 2012 at 11:00 PM, Firerat fire...@googlemail.com wrote:

 On 12 Nov 2012 17:07, Oshadha Gunawardena oshadha.ro...@gmail.com
 wrote:
 
  Hi all,
 
  Where to find Intel DH67BL Linux drivers, specifically for network
 interface. Searched through Google and couldn't find it.
 
  Thanks.
 

 I would be very surprised if it were not in the kernel.

 Anyway, I checked Intel's site for manual, LAN is Intel 82579v so add
 Linux kernel to a google search to get more

 --
 Firerat

 --
 http://linuxfromscratch.org/mailman/listinfo/lfs-support
 FAQ: http://www.linuxfromscratch.org/lfs/faq.html
 Unsubscribe: See the above information page


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page