gmane.linux.lfs.beyond.support

wpa_supplicant-1.0 fails to compile

John Burrell — 2012-05-24T14:21:53

wpa_supplicant-1.0 fails with:

../src/drivers/driver_nl80211.c:25:31: fatal error: netlink/genl/genl.h: No such file or directory
compilation terminated.

I had to include the libnl3 headers location:

CFLAGS="-I/usr/include/libnl3" make BINDIR=/sbin LIBDIR=/lib

for it to work.

jb.

[Fwd: Error in BLS Python-2.7.3]

Bruce Dubbs — 2012-05-23T20:49:41

-------- Original Message --------
Subject: Error in BLS Python-2.7.3
Date: Wed, 23 May 2012 17:00:53 -0300
From: Marcos Yoshito Kasahara <kasahara< at >ig.com.br>
To: bdubbs< at >linuxfromscratch.org

Dear Bruce

I think I have found a mistake in Python-2.7.3 (
http://www.linuxfromscratch.org/blfs/view/svn/general/python2.html),
in the line "Command Explanations" you mention "--with-system-ffi", but in
the actual command line there is no
"--with-system-ffi".

sed -i "s/ndbm_libs = \[\]/ndbm_libs = ['gdbm', 'gdbm_compat']/" setup.py &&
./configure --prefix=/usr --enable-shared &&
make

Thanks

Best Regards

Marcos Kasahara

MesaLib take about 18 SBU on my box.

xinglp — 2012-05-23T17:14:23

It said 3.0 SBU in the below URL, is that normal?
http://www.linuxfromscratch.org/blfs/view/svn/x/mesalib.html

Browsers and Linux

alex lupu — 2012-05-22T23:28:49


  but I don't wanna chat  :'(

Regards,

Browsers and Linux

alex lupu — 2012-05-22T17:32:55

Hello,

Warning:   the following might be interesting (if at all)
because of its hidden (and subtle) punch line.
Other than that, not necessarily worth reading and/or considering.

As we all know, the major event of the year happened this weekend
when Chrome exceeded IE usage (even if for a fleeting moment -
however, the trend is there.  Firefox slid to third, they say.)

Be that as it may, I assume the comparison was made on the basis of
the apples to apples principle, i.e., Windows to Windows (to Windows).

As the Linux world is fading more and more into irrelevance (sorry for
hurting some people's feelings with this "disclosure"), I'm listing
a couple of personal experiences that, to me, never bode well for
Linux development and success.

1.  A paranoid behavior to never admit mistakes;  probably for
fear that an imaginary enemy (Microsoft?) might use the news to their
advantage.

The main example is the kernel.org (and others) recent lengthy outage
which elicited nary a discouraging word.
Hush hush in th

crow

2012-05-22T04:09:51

My apoligies to moderator .I got a little carried away and the statement 
about following the rules was out of line. Certainly we all have  
observe the rules or things would get out of hand quickly. I will 
confine my posts to on topic discussions. 

### Mike Hollis ###

mail headache

Mike Hollis — 2012-05-21T02:38:44

 This is probably the the wrong forum for this , but it doesn't hurt to 
ask. I posted to this list earlier and received the responses to the 
post but didn't get my own post back. I thought perhaps this was due
to using my gmail account and switched back to the service provider's
mail server for the list mail. I'm trying to close service providers
account because of extremely slow connections and other reasons and
I changed the list mail back to gmail.I also changed the sendmail config
to use smtp.gmail.com as a smart host instead of the providers smtp 
server and changed my generics table to reflect the change.
 I'm also subscribed to the test-list and the chat list and have the
the same problem there. I have bind9 set up per BLFS instructions 
(except I added a couple zone files and added the service providers
dns servers as forwarders).
 I just wonder if this some kind of reverse dns snafu. I just sent a 
mail to myself at the service providers server sent with gmail and
fetchmail pulled it fine. So , I'

some broken links

John Burrell — 2012-05-20T15:06:59

Herewith some broken links which make automation a little more difficult -
http://ftp.debian.org/debian/pool/main/w/whois/whois_5.0.12.tar.gzftp://ftp.debian.org/debian/pool/main/w/whois/whois_5.0.12.tar.gzftp://apache.mirrors.pair.com/httpd/httpd-2.4.1.tar.bz2ftp://mirror.ovh.net/gentoo-distfiles/distfiles/db-5.3.15.tar.gzftp://ftp.x.org/pub/individual/lib/libpthread-stubs-0.3.tar.bz2
jb.       -- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

libtool gsl question

luxInteg — 2012-05-20T15:49:11

Greetings

When  I compile gsl-1.15 on by blfs box   I have lines like these in the 
output:-
/bin/sh ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I..    
-O3 -fexceptions -m64 -fPIC -MT init2d.lo -MD -MP -MF 

I  want to know what the M switches i.e. -MT -MD -MP -MF   mean.  I have 
looked at the man pages of  libtool
( http://www.manpagez.com/man/1/libtool/)
and of the gcc,   and a few other places and found  no explanation for the -MT 
-MD -MP -MF.


Advice would be appreciated.
Sincerely
Lux-integ

Open LDAP configuration warning

James Richard Tyrer — 2012-05-20T10:22:57

When I run 'configure' on OpenLDAP-2.4.31 I get this warning:

WARNING: Use of --without-threads is recommended with back-shell

Is this significant? and if so, what action is best?

I.E. Do I need the shell back-end?  Not using threads doesn't sound like 
a good solution.

Mesalib and new llvm location

John Burrell — 2012-05-18T15:57:31

When llvm was installed in /opt I could install mesalib albeit with a slight hiccough with makedepend.

With llvm now in /usr, the mesalib make gives me a long list of unfound llvm libraries, ending with:

/usr/bin/ld: cannot find -lLLVMCodeGen
/usr/bin/ld: cannot find -lLLVMScalarOpts
/usr/bin/ld: cannot find -lLLVMInstCombine
/usr/bin/ld: cannot find -lLLVMTransformUtils
/usr/bin/ld: cannot find -lLLVMipa
/usr/bin/ld: cannot find -lLLVMAnalysis
/usr/bin/ld: cannot find -lLLVMTarget
/usr/bin/ld: cannot find -lLLVMCore
/usr/bin/ld: cannot find -lLLVMAlphaDesc
/usr/bin/ld: cannot find -lLLVMAlphaInfo
/usr/bin/ld: cannot find -lLLVMMC
/usr/bin/ld: cannot find -lLLVMSupport
collect2: error: ld returned 1 exit status
make[4]: *** [lp_test_format] Error 1

This not surprising since llvm installs:

  /usr/lib/llvm/libLLVMScalarOpts.a
  /usr/lib/llvm/libLLVMSelectionDAG.a
  /usr/lib/llvm/libLLVMSparcCodeGen.a
  /usr/lib/llvm/libLLVMSparcDesc.a
  /usr/lib/llvm/libLLVMSparcInfo.a
  /usr/lib/llvm/libLLVMSupport

Shell at startup

David D — 2012-05-17T05:47:53

I am not sure if this is the right list for this but anyway...
Upon finishing the installation of LFS and booting the computer,
I continued on to BLFS.
In the section "Shells" (II.7) the book offers to install various other
shells,
and offers to make the installed shell the default shell.
Since I am not an expert in shells, I figured "why not".
Although there is a note that says that you have to reset the link
to bash in order to build _LFS_, it doesn't say you need to reset the
link in order to _boot_ the OS.
"Why?" you ask?
Well, I found out that soon after I restarted my PC, a bunch of errors
would pop up... the init scripts are written _bash-specific_ yet they
reference /bin/sh:
#!/bin/sh
(see http://www.linuxfromscratch.org/lfs/view/stable/scripts/apds04.html)

I suggest to either make the scripts non-bash-specific by changing certain
lines like
mkdir -p /run/{var,lock,shm}
to be compatible with shells that don't support brace expansion:
mkdir -p /run/var
mkdir -p /run/lock
mkdir -p /run/shm

OR
to chan

mutter and clutter

Lars Bamberger — 2012-05-15T21:49:46

Hello,

I've come across this problem during a GNOME build as per BLFS-SVN on an lfs-7.1 system:

During the build of mutter-3.4.1:
clutter-x11.h and clutter-x11-texture-pixmap.h are missing (needed by compositor.c). These are part of clutter-1.10.4 but they are not installed during the installation of clutter. If I copy them manually, there will be an 'undefined reference' error later. I then checked the clutter ChangeLog and did some more research.

My take is that these two versions (mutter-3.4.1 and clutter-1.10.4) are not compatible. Those header files are also not installed by the most recent clutter-1.11.2.

Any ideas?

Thanks,
Lars

gedit-3.4.1 fails to compile

John Burrell — 2012-05-15T15:38:31

gedit-3.4.0 installs okay but with 3.4.1 make I get:

libxml2.parserError:  Entity: line 1:  parser  error :  Opening and ending tag 
mismatch: app line 1 and p
 нето на код може да стане по-лесно и бързо.</p>
                                                                                
^
 Entity: line 1:  parser  error :  Premature end of data in tag p line 1
 нето на код може да стане по-лесно и бързо.</p>

Googling didn't shed much light so I don't know how to fix it. I don't
even know what language that is. Mon-Khmer?

jb.

mesalib patch

John Burrell — 2012-05-13T16:08:48

In the mesalib patch

would you kindly change this line:

$(INSTALL) -v -d -m755 $(DESTDIR)$(INSTALL_DIR)/bin

to this:

test ! -z $(DESTDIR)$(INSTALL_DIR)/bin || $(INSTALL) -v -d -m755 $(DESTDIR)$(INSTALL_DIR)/bin

Please always check if a dir exists before trying to create it with permission 755. The owner may not want the dir permission to be 755.

Thanks

jb.

KDE NetworkManager frontend

David D — 2012-05-12T19:39:05

In order to use the KDE NetworkManager frontend (is it
KNetworkManager, or the Network Management option under System
Settings?) do I have to add it to the panel at the bottom of the
screen?
If not:
Where can I find a KDE NetworkManager frontend and how do I use it?

Thanks in advance,
David Dorfman

screen use wrong pty-group

xinglp — 2012-05-12T18:25:00

http://www.linuxfromscratch.org/blfs/view/svn/general/screen.html

./configure --prefix=/usr                     \
            --with-socket-dir=/var/run/screen \
            --with-pty-group=4                \
            --with-sys-screenrc=/etc/screenrc

but http://www.linuxfromscratch.org/lfs/view/development/chapter06/createfiles.html

cat > /etc/group << "EOF"
root:x:0:
bin:x:1:
sys:x:2:
kmem:x:3:
tape:x:4:
tty:x:5:
EOF

Should the "tty:x:5:" and "--with-pty-group=4" use same number?

naming inconsistency

John Burrell — 2012-05-10T22:48:47

It may seem pedantic to you, but I wonder if you could be consistent with your naming of patches please.

As an example, the source name for pygobject2 is pygobject- while you've named the patch pygobject2-

As I say, you probably think this is trivial, but it actually makes a difference when automatically downloading and installing packages.

Thanks.

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

gcc-4.5.1 (BLFS) vs. gcc-4.7.0 (LFS)

alex lupu — 2012-05-07T20:03:16

Hi Andy,


As I said (and feared), I'd have to upgrade to 4.7.0 so I
could survive in this cruel world a while longer.

In case you can somehow, sometime find a submissive victim
to "volunteer to update the BLFS page ;)", maybe my input
will help this unhappy fella in his unenviable chore.

Followed _exactly_ the BLFS 4.5.1 instructions, by
substituting 4.7.0 for 4.5.1 with

Two exceptions:
1. Only "--enable-languages=c,c++"
(I skipped fortran and whatever this time :)

2. Before doing (at the very end),

ln -vs libgcc.a `gcc -print-libgcc-file-name | sed 's/libgcc/&_eh/'`,

I saved the original (for no real reason; just habit):

cd /usr/lib/gcc/i686-pc-linux-gnu/4.7.0/
mv libgcc_eh.a libgcc_eh.a-4.7.0

Note:  Of course, no ADA, no "make bootstrap" (just "make")
 and no all the GNAT nonsense.

Obviously, the proof of the pudding will be after I try
Chrome compile again (I'll download a fresh update).
If still alive, I'll report.

Thanks,

gcc-4.5.1 (BLFS) vs. gcc-4.7.0 (LFS)

alex lupu — 2012-05-07T15:27:04

Rick, Andy and Ken,

Thank you for your prompt and helpful comments.

Seams like everything points to my going for the dreaded* 4.7.0
I'll lose anyway but with head up high.

Cheers,

gcc-4.5.1 (BLFS) vs. gcc-4.7.0 (LFS)

alex lupu — 2012-05-06T23:49:26

My latest build (make) of the Chrome browser failed with
apparently a gcc (actually, g++) error of some sort:

"...
Please submit a full bug report, ...
See <http://gcc.gnu.org/bugs.html> for instructions. ..."

I've had gcc-4.5.1 (in good standing) for quite a while.
Rather than going through the big effort, uncertainty and
probably the futility of submitting a bug report,
I'm thinking about just upgrading to gcc-4.7.0 (the latest
as of this writing), thereby killing as many as two birds
(in the ideal outcome).

QUESTIONS
1.  Mostly theoretical.  Why this dissimilarity between
LFS and BLFS versions?
Any implications?

2.  Any problems with the 4.7.0?
Hidden, I mean.  Of course it works (both as installation and usage)
if the reader follows the LFS instructions _to the letter_ (as they
are constantly reminded in lfs-support).

Any helpful words will be highly appreciated.
Thanks,