Mark Olbert wrote:
> I've just spent a hair-tearing day trying to get qpopper 4.0.9 to work on my
> new LFS system.
>
> The problem was that popper kept exiting after trying to do its second fork.
> This was on a system that was using xinetd (there is more detail about the
> problem, and log extrac
Dan Nicholson wrote:
> On Mon, Apr 21, 2008 at 7:34 AM, Arnie Stender <[EMAIL PROTECTED]> wrote:
>
>> Dan Nicholson wrote:
>> > That certainly looks like the type of error -Werror would throw, but I
>> > don't see it anywhere. What version of gcc is th
Dan Nicholson wrote:
> That certainly looks like the type of error -Werror would throw, but I
> don't see it anywhere. What version of gcc is this? On the other hand,
> casting from a pointer to a non-pointer seems totally wrong even if
> it's probably harmless in this instance, so I'm guessing tha
Hi All,
Interesting, this is the 2nd or 3rd time I went to post and couldn't
till I unsubscribed then re-subscribed. I keep getting mail from the
list but every so often... Does anyone else ever have that happen?? At
any rate the reason for the post. I had everything running fine on my
new BLFS
Simon Geard wrote:
> Just a wild guess (having never used XFCE), but do you have a D-Bus user
> session running (i.e the one running as yourself, not the system one
> started on boot)? The strace appears to be doing something involving
> D-Bus immediately before segfault occurs...
>
> Of course as
Alexander E. Patrakov wrote:
>
> XFCE is no longer supported in BLFS (and you didn't even specify its
> version!).
> There is some activity on the XFCE mailing list, but it is mostly about the
> upcoming 4.6 release.
>
> As for the segfault, strace logs are always useless in this situation, plea
Hi Folks,
I am sending this post from my new albeit minimal for now
workstation (CLFS/CBLFS multi-lib) running on AMD64 Athlon. I'm running
xorg-7.3 and XFCE window manager. Everything in XFCE started up except
for xfdesktop so it doesn't look too nice right now but at least it's
functional
Hi Folks,
Well I am almost to the point where I can boot into my new [C]BLFS
workstation and continue compiling the rest of the packages I need with
all the tools I need while doing it. The two last pieces are Firefox and
Thunderbird. I tried compiling Seamonkey but got errors that looked a
lot
Ag. D. Hatzimanikas wrote:
>> Excellent! That does give me the file format in the status line. I may
>> have been dreaming or maybe it is just my failing memory but I could
>> have sworn I remembered that along with that I saw a trailing '^M' on
>> the lines of the DOS format file I was editing. Th
Ag. D. Hatzimanikas wrote:
> The specific setting in vim is the 'fileformat', so by doing a
>
> :echo &fileformat
>
> you should be able to see the file's format, which indeed for the qt patch is
> dos.
>
> If you want to show it permanently in the status line, have a look at the
> status line
>
Ken Moffat wrote:
> This came up on -book or -dev last month, I think. The problem is
> the version of patch! Clfs is using an alpha version, I think
> someone said the patch is in dos format, and that's the problem.
> Robert came up with a solution sometime, involving running it
> through 'tr'.
Ken Moffat wrote:
> This came up on -book or -dev last month, I think. The problem is
> the version of patch! Clfs is using an alpha version, I think
> someone said the patch is in dos format, and that's the problem.
> Robert came up with a solution sometime, involving running it
> through 'tr'.
Hi Folks,
I don't know too much about how the patch application works so I
need some help. I am building the QT3 package from the CBLFS book and it
had a patch file that says it is a security patch having to do with
UTF8. I have downloaded the patch twice to make sure it didn't get
corrupted. W
Ken Moffat wrote:
snip//snip
Hi Ken,
I fixed the problem but I have no idea why what I did fixed it. Yet
more confusion. I get confused a lot here lately. :-( I'll not include
the whole thread here for the sake of space but I'll answer a number of
your comments and questions. I am running SMP.
michael lang wrote:
> Did you start from a clean directory? Some packages you need to remove
> the folder and unpack the source tar again.
Yes. The first time I did a 'make distclean' which has worked up till
now. When that didn't work I blew the directory away and un-tared a new
one with the same
Happy New Year All!
Nothing new here except the year. I'm confused again. :-( I'm trying
to compile gtk2 using the CBLFS book on my multilib CLFS system. 32 bit
compiled and installed and 64 bit compiled without error. When I ran the
install for 64 bit I got the following errors. I'll include t
Ken Moffat wrote:
> On Sat, Dec 22, 2007 at 06:02:47PM -0600, Arnie Stender wrote:
>
>> Well it didn't take long to get me confused again. Here I thought I was
>> doing so well. :-( I'm still compiling for Xorg this time the
>> dbus-glib.0.74 package. It comp
Well it didn't take long to get me confused again. Here I thought I was
doing so well. :-( I'm still compiling for Xorg this time the
dbus-glib.0.74 package. It compiled fine for 32bit but when I did the
64bit version I got these strange errors ending with a segmentation
fault on a non-existent .h
Dan Nicholson wrote:
> On Dec 22, 2007 9:19 AM, Arnie Stender <[EMAIL PROTECTED]> wrote:
>
>> Hello All,
>> I have been following the CBLFS instructions for compiling
>> glib-2.14.4 and got the error below while doing the 32bit compile on a
>> mul
Arnie Stender wrote:
> Hello All,
> I have been following the CBLFS instructions for compiling
> glib-2.14.4 and got the error below while doing the 32bit compile on a
> multi-lib CLFS system. It was compiling gatomic.o. Has anyone seen this
> before? I haven't tried the 6
Hello All,
I have been following the CBLFS instructions for compiling
glib-2.14.4 and got the error below while doing the 32bit compile on a
multi-lib CLFS system. It was compiling gatomic.o. Has anyone seen this
before? I haven't tried the 64 bit build yet. BTW, if I am supposed to
be posting
Hi Everyone,
I finally got my CLFS Multi-lib workstation to boot and am about to
embark on the current SVN of BLFS. I know I will need to ask some
questions and the last time I tried to post to this list it didn't work.
So, I'm testing the waters. I apologize if this actually posted for
wasting
Hi All,
I know this should really go to the CLFS support list but that list
is rejecting my posts at the moment and I can't seem to get anyone's
attention to fix it. I figure there are probably people watching this
list that can help and since I can't start on building my BLFS till I
get this
Hi All,
I know this should really go to the CLFS support list but that list
is rejecting my posts at the moment and I can't seem to get anyone's
attention to fix it. I figure there are probably people watching this
list that can help and since I can't start on building my BLFS till I
get this
Jens Radloff wrote:
> Hi Arnie,
>
> It works now again, my internet connection ;) You made me think of:
> which DNS does my router use, and which DNS are specifed in my
> resolv.conf? Well, there were different DNS specified in the
> configuration of my router, so I put the IP addresses of these
Jens Radloff wrote:
> Hi,
>
> well, I am not really fully acquainted with network configurations, so
> here it comes ... ;)
>
> in blfs 6.0 I have no connection to the internet anymore (it worked
> before, I did not intentionally change any dhclient settings, and I did
> not build and use a new ker
Andrew Beverley wrote:
> I'm trying to add a second IP address to the eth0 interface. Having done
> a lot of searching, it seems that the traditional method is to add
> another interface called eth0:0 with the second ip address. This works
> fine as a one-off, but if I try to make it permanent by a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
I meant this to go to all not just Tijnema. I guess i replied to the
wrong one. :-(
Arnie
- Original Message
Tijnema ! wrote:
> I'm not sure, but do you have libcrypto.so?
>
> I think it is requesting for that one (do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Folks,
I'm trying to compile kdebase-3.5.6. I have upgraded my ssl to
openssl-0.9.8e because while I was compiling the kdebase I was getting
errors about the libssl.a and libcrypto.a saying some .o was not
relocatable. I compiled the ssl wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
> The Mplayer in the book is pretty old. I'd give 1.0rc1 a shot.
> Presumably, they're just ironing out bugs as they approach 1.0rc1.
>
> http://www.mplayerhq.hu/design7/dload.html
>
> --
> Dan
Hi Dan,
Well, I took your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jignesh gangani wrote:
> Hi,
> There are four patches for mplayer. One of which allows you to
> compile Mplayer on GCC-4.1. Try applying the patches. You can get this
> patches on CBLFS. You have to download another version of MPlayer.
> Try ap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tijnema ! wrote:
> On 3/1/07, Dan Nicholson <[EMAIL PROTECTED]> wrote:
>>
>> On 3/1/07, Tijnema ! <[EMAIL PROTECTED]> wrote:
>> > On 2/28/07, Barius Drubeck <[EMAIL PROTECTED]> wrote:
>> >
>> > > Second thing:
>> > > 1927 ?00:00:00 smbd
>> > >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
I'm trying to compile MPlayer from the 6.2 book and I got an error
about a redefinition of getline. Before I sent this mail I commented
out the getline from vobsub.c and started the compile again. It ran past
the original error and stopped
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken Moffat wrote:
> Rang a vague bell with me, although I have no wish to develop RSI
> :-)
>
> Back in December '05 somebody asked the same question. Google
> linked to my posting, but came up with an entirely different mail.
> Fortunately, the v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
I'm working on a problem where I need to edit a directory entry and
need to install emacs so I can use dired. When I do the ./configure I
get the following output.
checking host system type... x86_64-unknown-linux-gnu
configure: error:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arden wrote:
> What is this -a option? My man cp doesn't show any -a option. I had
> the same trouble with cp so I have done this; cd to the partition you
> want to move and
> tar cvpf - .|(cd /mnt/hda6; tar xvpf - .)
>
> Seems to work better.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
> On 2/4/07, Arnie Stender <[EMAIL PROTECTED]> wrote:
>
>> I don't have time right now to test tar and cpio but I do know for
>> sure
>> a straight cp of an SUID file does NOT produce a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
> Not if you did it as an unprivileged user. It'd be a security hole for
> you to copy stuff and retain other's privileges. Only root can do
> that. A simple `cp -a' works, but `tar' or `cpio' are probably better
> suited for this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Good morning All and a Happy New Year to You!
A while back I posted a question about using SSL connections to pick up
my mail and I got a lot of good information. I proceeded to implement
based on that information but I still don't have it work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thierry Nuttens wrote:
>>
> Did you implement any Network Authentification protocol like Heimdal or MIT.
>
>
> Happy New Year
Hi Thierry,
No I haven't. Is that necessary in light of the fact that SSL (if
working properly) is encrypting e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shawn wrote:
> Hi Arnie, I hope you had a merry christmas too. :)
>
> For a long time I was confused about the myriad of email options on a
> linux system. Actually, I still am confused if I plan to run a server
> for more than local mail.
>
> So
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Guys,
I hope you all had a good holiday. I have a question that is not really
pertaining to the list but you have been my primary source of
information for a long time and I trust that you have the answers that I
need in this case. I am tryi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alberto Hernando wrote:
>
> Hi.
>
> As usual, Dan is right. If you have udev working you will have a /dev/video0
> device as soon as you load the driver, and the cam is plugged in, of course.
> Recently, I was given a cheap logitech quickcam webcam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Lord wrote:
> Arnie Stender wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Al,
>> Thanks for the input from google but it looks bad for me. It looks
>> like
>> the code for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Al,
Thanks for the input from google but it looks bad for me. It looks like
the code for the driver hasn't been touched since 2003 or earlier. I
don't think AMD64 CPUs were used much back then if they had been created
at all. The code is geared
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Lord wrote:
>
> Why not just type "Intel CS330 & Linux" into Google. The first link from
> the result set is: http://spca50x.sourceforge.net/spca50x.php?page=cams
>
> Do the same for "netmeeting & linux" and you get:
> http://www.linux.org/docs/l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
I have an Intel CS330 Cam I used to use on my Windows box and it worked
well with Net Meeting. It's USB and I plugged it in on my CLFS/BLFS
workstation thinking I would be able to see a new device to point my
xine or totem at and that h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Calling all programmers:
I have worked through a few problems now trying to get JDK-1.5.0
compiled. The last one is confusing me a bit because although I know my
mind is no longer the steel trap it used to be I am almost sure that
since startin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Lord wrote:
> You have to remove the :: to! See the first link to this problem I
> posted a dayor two back for aspell.
>
> Al
>
Al,
Thanks, that got me moving again but I quickly ran into another
problem. I did some googling and found a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Lord wrote:
> Dan Nicholson wrote:
> >> /usr/src/secondary/jdk-build/hotspot/src/share/vm/runtime/os.hpp:325:
>>> error: extra qualification 'os::' on member 'exception_name'
>>
>> These "extra qualification" issues are because of gcc-4.1. There'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Lord wrote:
> Dan Nicholson wrote:
> >> /usr/src/secondary/jdk-build/hotspot/src/share/vm/runtime/os.hpp:325:
>>> error: extra qualification 'os::' on member 'exception_name'
>>
>> These "extra qualification" issues are because of gcc-4.1. There'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
> On 10/31/06, Arnie Stender <[EMAIL PROTECTED]> wrote:
>>
>> After the recent thread on JDK I decided I would make an attempt at
>> getting it running. The BLFS page looks like it is mainly aimed at i3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
DJ Lucas wrote:
> Gaim is compiled against QT/KDE. IIRC, either run it once in KDE, or do
> this:
>
> mkdir ~/.kde/socket-name1/
>
> Might be a little more to it, but it's something along those lines.
>
> HTH
>
> -- DJ Lucas
>
Hi Lucas,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken Moffat wrote:
> Hi,
>
> I'm floundering in the dark here, so I thought I'd ask the list
> (maybe I'm looking in the wrong places). Since the end of last year
> I've gradually lost the ability to post on many mailing lists. The
> latest is the c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
I have been on a quest to get all facets of video and audio working on
my new system. As it turns out after I created dbus and hald when I
insert an audio CD in the drive totem starts up and plays it. If I shut
it down and try to restar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello again,
I found another codec that I don't have yet libdv but it needs glib
and gtk+ 1.2.10. I was told earlier that it would co-exist with and was
different from V2 of those packages so I decided to compile them. While
configuring glib I got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Lord wrote:
>> On 10/10/06, Arnie Stender <[EMAIL PROTECTED]> wrote:
>>
>>> The mount business was done because I got the error quoted in my
>>> original post when I did what you just said. I wanted t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
> They're in there.
>
> http://www.linuxfromscratch.org/blfs/view/svn/multimedia/libdvdread.html
> http://www.linuxfromscratch.org/blfs/view/svn/multimedia/libdvdcss.html
>
> libdvdread reads the dvd structure, and libdvdcss is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken Moffat wrote:
> Arnie, what's with this 'mount' business ? If it is going to be
> playable, put it in the drive, tell xine to play the DVD by klicking
> on the button labelled 'DVD', then use the menus. ISTR that all is
> not as it seems with th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On another note, while I was hanging my system and rebooting I noted
that every time I logged in again the background that I had set was gone
and it was set to the default gray/blue of Gnome. When I go into
Desktop-> Preferences-> Desktop Background th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Again,
I just finished building xine-lib-1.1.1 and xine-ui-0.99.4. While I was
going through the setup to make sure things looked sane I noted that the
default network connection speed was T1. When I attempted to reset it to
something closer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alberto Hernando wrote:
> Hi.
>
> I have installed a lfs-6.2. Then, following the blfs book (svn version) I've
> installed d-bus, hal, linux-pam and lots of other things. No problem so far,
> but now I'm trying to access my camera and pendrive from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shawn wrote:
> Jim:
> You can find the flash player for linux here:
>
>
>> http://www.adobe.com/shockwave/download/alternates/
>
> Flash version is 7.0 for linux. Download it and untar
> it then read the README. It is a very simple install,
> just a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK Guys,
Just when I started feeling comfortable with figuring out version
dependencies I ran into this. I'm compiling xmms-1.2.10. I ran the
configure out of the book and I got the following errors. I ran
'pkg-config --modversion glib-2.0' and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I ma getting a steady stream of entries in my kern.log that started on
September 23rd. I have no idea what I was doing at that time so I'm not
sure where to go to fix it. I have never seen anything like these before
so I haven't got a clue. Not unusual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan/Shawn,
Now I am totally confused. Before I went on to other things I decided
to build another package and do what I said. I chose gcalctool. I did a
find for the gcalctool.desktop and found it in /usr/share/applications/.
Ran the update and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shawn wrote:
> Hello Arnie:
>
> I am not an expert in this field but this is how I understand the XDG
> menu system.
>
> The XDG menu system is a freedesktop.org spec. that both gnome and kde
> use to define how an application is started and where/ho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shawn wrote:
> Hello,
>
> First, I use kde but I might be able to help.
>
> Do you have a menu at all? That is, if you press the "foot" on the
> toolbar, does it show an empty menu?
>
> If you have at least that much, go over the "desktop-file-utils
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Guys,
I don't normally log out of my BLFS workstation but it seems that when
I do the next time I login more and more applications start a login. It
seems like almost every application I have ever run started this time
around except for seam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
> On 9/30/06, Arnie Stender <[EMAIL PROTECTED]> wrote:
>>
>> I'm missing something. I have re-compiled popt-1.10.4 with
>> configure
>> switches --prefix=/usr and --libdir=/usr/lib. T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dennis J Perkins wrote:
> I think that recompiling only popt is sufficient. ldconfig is probably
> run when you run "make install", so popt should be visible afterwards.
> If it doesn't run ldconfig, you can run it yourself.
>
> If you built a 64-bi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I looked through the .la files in /usr/lib to see how many listed popt
in the dependencies line. There were 25 of them. Here is the list. Am I
going to have to recompile all of these to get rid of my problem? This
may take a while. :-(
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Guys,
I'm missing something. I have re-compiled popt-1.10.4 with configure
switches --prefix=/usr and --libdir=/usr/lib. This seems to have
installed libpopt files properly in /usr/lib. Now I am going back and
re-compiling other libs that ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I messed up and sent this from the wrong account. Second try.
Hi Guys,
OK, I did what Dan said about removing the /usr/lib64 and running
ldconfig but I still had problems compiling volume manager or whatever
the last package was. I started looking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken Moffat wrote:
> On Sun, Sep 24, 2006 at 05:19:58PM -0500, Arnie Stender wrote:
>> I still have the build
>> directories and checked the time stamps and I compiled popt before I
>> compiled libgnome-2.14.1. I'll have to go
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alessandro Alocci wrote:
> Hi Arnie, it seems like you haven't your libgnome and libbonoboui
> compiled with popt support. But I have just tried to recompile my
> libgnome hiding libpopt and that breaks the configure.
> Can you see what is the output o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Guys,
I've been trying to get my sound working and have started making some
progress but discovered that i don't really have any way to test the
sound once I get the udev, devices and modules working so I'm compiling
sound tools and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Henty wrote:
>> This small "bonus" even allows you to ignore all the filtering and
>> dump everything to one file if you so desire.
>
> Well, duh, that's what I *said*. I'm asking if there's a compelling
> reason not to do that. For instanc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
> Excellent, David! We should put this on the Wiki. I have a couple
> others I've noticed from installing into DESTDIRs.
>
> Dan
Dave/Dan,
OK, I have no clue what is going on and at this point I'm not sure I
want one. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
> Hmm. You should have
> ${GNOME_PREFIX}/etc/gconf/schemas/mahjongg.schemas. Does that exist?
> It should be installed by gnome-games. Are you installing into a
> DESTDIR, or directly to /? Also, what's the output from `gconftool-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Folks,
I have compiled the gnome-games from the dev book a while back and
everything was working as far as I had tried them. I have not tried them
all. My favorite is Mahjongg and it was running fine. I have been having
problems with gnome s
Ken Moffat wrote:
As a user of architectures other than x86, cdrecord itself is a
pain in the proverbial to build.
Ken
Hi Ken,
As I remember cdrecord didn't give me any grief at all. I decided to
use it because k3b was giving me so much trouble. I never did get that
one working.
Arnie
-
Ken Moffat wrote:
Do you know that the pages you are trying to serve are ok, or are
they untried/untested ?
Ken
To test the HTML just bring the .html file up in a browser. IE: Use
"file:///full/path/to/file.html". That way you leave the Apache server
out of the loop.
Arnie
--
http://l
Hi All,
I have been out of contact for a while. I posted three or four
messages and got no replies. I thought I may have run out of free
vouchers but it turns out my mail server was not sending my mail because
of bind problems. Before I figured that out I broke my system disk
mirror and loa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Folks,
While waiting for answers to my other problems last night I started
compiling the dependencies for the system monitor. I finally got to the
compile of the monitor itself and got the following error. I suppose I
ought to be grateful it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have slipped back to my more normal state of being confused. I've
been trying to get my sound working. I installed the bootscripts alsa in
init.d and linked it to rc5.d. I couldn't get the sound working so I
rebooted the system to see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
>
> Yeah. The idea was that since the error began occurring with
> gcc-3.4.x, it should reference that. It's necessary for that version
> and any newer one, though, since gcc gets stricter syntax with each
> version.
> The -2 and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
> Excellent! It's still a bit brute force, but at least now I have the
> use of for loops, sed, etc. If there are any particular Wiki page
> anyone wants to see, please ping me now.
>
> --
> Dan
Hi Dan,
My answer would b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Folks,
I'm trying to build the net-tools package from the dev book. One of the
patches you say to apply is net-tools-1.60-gcc34-3.patch I am running
with gcc-4.1.1. I got the following errors. Is there a different patch I
need to apply if us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Staub wrote:
>
>
> kdelibs does not require PCRE. You can add "--disable-pcre" to configure
> to tell it not to look for PCRE.
Hi Chris,
Thanks for the correction but configure didn't tell me that. It just
said I had to have it. If I h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Team,
While trying to compile kdelibs-3.5.2 I had compiled the "required"
aRts-1.5.2 but since I am running gnome I was not looking for a complete
KDE but just enough to compile k3b. The configure failed because it said
PCRE was "required" not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Folks,
Yet another relocate error this time trying to compile kdebase-3.5.2.
I'm actually running gnome but I'm trying to compile k3b and it wants
all the kde stuff. I didn't see any patches for this in the dev book.
Here is what I'm seeing.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alessandro Alocci wrote:
> At 18:56, sabato 19 agosto 2006, Arnie Stender wrote:
>
>> Second, I looked through the BLFS book and didn't see any trace utility
>> except traceroute. Is there a *LFS that has the trace utility in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
> Looks like it didn't try to build with -fPIC again. Out of curiosity,
> could you print the info from `perl -V'?
>
> Interestingly, I stumbled on this build log of a GAIM perl module on
> x86_64. Look at the output at the botto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I'm cross posting this because I'm hoping to reach someone who will
have the answer. I just posted a message to BLFS which tells of trying
to compile gaim-1.5.0 on a pure 64 CLFS build running on AMD64. When I
try running a build of gaim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
>> Think I found the silver bullet. File it under "perl sucks hard".
> Found someone having a similar problem on X86_64 trying to compile
> mod_perl.
>
> http://www.nntp.perl.org/group/perl.modperl.modules.dev/2
>
> The problem i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken Moffat wrote:
>
>
> FWIW, I've seen the same thing on recent versions of gnumeric. In
> that case, I pass --disable-perl. I've also had to build without
> perl on (an old version of) xchat, so I recomment looking at
> ./configure --help.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
>
>
> What happens when you don't force in the -fPIC?
>
> --
> Dan
Hi Dan,
The same thing. I don't change things unless something goes wrong. I am
getting the same basic error trying to compile libmng-1.0.9 This is
gett
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
>>
> As another person in this thread mentioned, 64 bit support was added
> in cups-1.2.x. It's not in BLFS yet, but Randy has only good things to
> say about it in the ticket.
>
> http://wiki.linuxfromscratch.org/blfs/ticket/197
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stan Sander wrote:
>
> Last I knew cups was 32 bit only. You can "fix" this by changing the
> cast from int to long and cups will compile, but then if you try to use
> cups to print more than one copy of something, you will get strange
> results. (i.
1 - 100 of 122 matches
Mail list logo
