Lord Igtenio wrote:
Hence why I tried it as a throw-away solution.
Frankly, I do find it insulting that you assume I must have no
experience or so little as to be unable to follow a step-by-step
guide which is entirely focused towards learning. Do I make
mistakes? Of course. So do you. We all do
Lord Igtenio wrote:
> Probably. But I also have a sore spot for having
> self-educated myself in the usage and repair of
> Computers, and most "Professionals" considering
> that to be "trite"
Being self taught is not trite. It is the ultimate way to learn
because you won't forget so easily. I sa
>Attempting not to sound insulting here, but if you think adding>/usr/include to your path will change anything then you definitely do>not meet even the minimum prerequisites for building LFS at all, much
>less for using ALFS. Please read up on your Linux basics (for example,>at the links suggested
Lord Igtenio wrote:
>If you just had /tools/bin at the front of your path, then jhalfs
>almost assuredly didn't do this. In that case, this setting was
>probably done after jhalfs completed. In which case everything done
>by jhalfs is fine. However, everything you've done since then is not
Dan Nicholson wrote:
Wait a second. I thought with udev-only linux-2.6.15+ we don't have
to make that mount anymore. Is this a special situation just for
libgphoto2? Because my ghoto2 setup is exactly the same as Richard
just descibed except I'm using the hotplug package with udev-071.
With
I'd like to share my modified package management scripts with everyone.
They worked quite well to build up and strip down my LFS system. I first
created a full LFS system for development use, then from that I created a
stripped-down minimal LFS system for production (fits on a flash drive). I
use
>You had /tools/bin at the front of your path?Aye.>If you just had /tools/bin at the front of your path, then jhalfs>almost assuredly didn't do this. In that case, this setting was
>probably done after jhalfs completed. In which case everything done>by jhalfs is fine. However, everything you've
On 3/3/06, Lord Igtenio <[EMAIL PROTECTED]> wrote:
> >Is /tools still in your path? What's the output of `which gcc` or if
> >you don't have which, `type -p gcc`? Do you have the symlink
> >/usr/bin/cc -> /usr/bin/gcc?
> >
> >If you actually are using /usr/bin/gcc and the above output is from
> >
On 3/3/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
Lord Igtenio wrote these words on 03/03/06 16:26 CST:> I've built an LFS System twice before, following the book both times.> The entire reason I used jhalfs is because I have neither the time> nor patience to spend another two and a half days of
>Is /tools still in your path? What's the output of `which gcc` or if>you don't have which, `type -p gcc`? Do you have the symlink>/usr/bin/cc -> /usr/bin/gcc?>>If you actually are using /usr/bin/gcc and the above output is from
>that, then there are issues. My guess in this situation is that th
Lord Igtenio wrote these words on 03/03/06 16:26 CST:
> I've built an LFS System twice before, following the book both times.
> The entire reason I used jhalfs is because I have neither the time
> nor patience to spend another two and a half days of five-hour
> intervals to build a third. Call me
>However, my message to you is more along the lines of you should>probably not be trying to use an automated build of LFS until you>are comfortable building manually and you are able to discover on>your own a messed up toolchain, and what you need to do to repair
>that toolchain if indeed it is mes
On 3/3/06, Lord Igtenio <[EMAIL PROTECTED]> wrote:
> >It would seem that /usr/include is not the default for you. Can you
> >try the following commands to see what the compiler defaults are?
>
> This's what I got.
>
> ignoring nonexistent directory
> "/tools/lib/gcc/i686-pc-linux
> -gnu/3.4.3/../.
Lord Igtenio wrote these words on 03/03/06 15:57 CST:
> And should I submit this as a bug to the people
> who work on jhalfs? I figured it'd take care of this,
> but apparently it hasn't.
There are a whole slew of folks that have successfully used jhalfs
to build a working installation of LFS. Yo
>It would seem that /usr/include is not the default for you. Can you>try the following commands to see what the compiler defaults are?This's what I got.ignoring nonexistent directory"/tools/lib/gcc/i686-pc-linux
-gnu/3.4.3/../../../../i686-pc-linux-gnu/include"#include "..." search starts here:#in
On 3/3/06, Richard A Downing <[EMAIL PROTECTED]> wrote:
>
> I don't think that GPhoto2 uses anything in /sys or in /dev. If appears
> to find devices via /proc/bus/usb. So for GPhoto2 you need usbfs
> mounted. There may be others.
>
> Certainly I could not get GPhoto2 to work even by creating de
On Thu, 2006-03-02 at 09:36 +, Знаки wrote:
> ЗВОНИТЕ! (495) 505-66-89
> Подари любимой оригинальный знак на 8 марта!
>
> Как удивить своих любимых и друзей? Что подарить на праздник?
> На эти вопросы есть один ответ - закажи себе и друзьям оригинальный знак или
> номер на машину.
> Сделать
This's weird.First, I added /usr/include to ld.so.conf and ranldconfig. Nothing changed.
Then, for the heck of it, I ran Libmng with:make prefix=/usr ZLIBINC=/usr/include \ZLIBLIB=/usr/lib -f scripts/makefile.linux...which works fine, and detects zlibwithout problem.Why is it that when you leave ZL
Alexander E. Patrakov wrote:
> Richard A Downing wrote:
>
>> Does anyone know how to set up such a system for gphoto2 (not
>> usb-storage)? Any hints would be very welcome. Udevmonitor output
>> below.
>
> I have no digital camera, and thus can't provide the information you
> need immediately.
19 matches
Mail list logo
