Am Samstag, 20. Mai 2006 17:20 schrieb Dan Nicholson:
>
> OK. So, it seems that you are pseudo-scripting. Do you just copy and
> paste the commands from the text file to the shell?
Well, I copy and paste the commands from the LFS book in to the shell and
afterwards in my personal log file.
Aft
On 5/20/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
58.) GCC-4.0.3
cd /sources
cd ./gcc-4.0.3
> If you're scripting, you have to be very careful. You need to know
> that the script will continue unless you have some sort of error
> handling scheme. If you don't a crucial
Hi!
Sorry for the delay of my response. :-(
Am Donnerstag, 18. Mai 2006 23:37 schrieb Dan Nicholson:
> On 5/18/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
> > Sorry to ask, but what are the important symlinks?
>
> These guys:
OK. Obviously not a smart question
(http://catb.org/~esr/fa
Mag. Leonhard Landrock wrote:
Sorry to ask, but what are the important symlinks?
http://www.linuxfromscratch.org/lfs/view/stable/chapter06/createfiles.html
Andy
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the ab
On 5/18/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
Sorry to ask, but what are the important symlinks?
These guys:
http://www.linuxfromscratch.org/lfs/view/development/chapter06/createfiles.html
I did some kind of logging for _all_ steps within the LFS building. I just
wrote every
Am Donnerstag, 18. Mai 2006 22:39 schrieb Dan Nicholson:
> On 5/18/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
> > root:/# strings /sources/gcc-build/gcc/cppdefault.o
> >
> > /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/include
> > /usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../../include/c++/4.0.
On 5/18/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
root:/# strings /sources/gcc-build/gcc/cppdefault.o
/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/include
/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../../include/c++/4.0.3
/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/../../../../include/c++/4.0.3/i6
Hi Dan!
Am Donnerstag, 18. Mai 2006 01:05 schrieb Dan Nicholson:
> On 5/17/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
> > This is the result:
[snip]
> It looks like what I got. Unfortunately, that didn't explain
> anything. Just as a last ditch effort, could you run this command:
>
On 5/17/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
First of all: Thank you for so much care.
No problem. I'd like to figure out what the issue is. Especially
since someone else is stuck at the same spot.
> This might be a dead end I'm leading you down, but could you find the
> p
Hi Dan!
First of all: Thank you for so much care.
Am Dienstag, 16. Mai 2006 22:57 schrieb Dan Nicholson:
> On 5/16/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
> > echo | /sources/gcc-build/gcc/cc1 -v
> > ignoring nonexistent directory
> > "/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/include" i
On 5/16/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
echo | /sources/gcc-build/gcc/cc1 -v
ignoring nonexistent directory "/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/include"
ignoring nonexistent directory "/usr/lib/../i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...
Am Montag, 15. Mai 2006 23:52 schrieb Dan Nicholson:
> On 5/15/06, Dan Nicholson <[EMAIL PROTECTED]> wrote:
> > $ /sources/gcc-build/gcc/xgcc -v dummy.c | grep include
>
> I just figured out something simpler to see the header search path.
> xgcc is just a frontend for the actual driver, cc1. This
Hi Dan!
I noticed your second post, but just to make sure I try both tests (the one
from this mail and the one from the other mail).
Am Montag, 15. Mai 2006 23:30 schrieb Dan Nicholson:
> On 5/15/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
> > Hi once again!
> >
>
> OK, so let's try to
On 5/15/06, Dan Nicholson <[EMAIL PROTECTED]> wrote:
$ /sources/gcc-build/gcc/xgcc -v dummy.c | grep include
I just figured out something simpler to see the header search path.
xgcc is just a frontend for the actual driver, cc1. This guy actually
gets executed when compiling or preprocessing
On 5/15/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
Hi once again!
Am Sonntag, 14. Mai 2006 23:05 schrieb Mag. Leonhard Landrock:
> Am Sonntag, 14. Mai 2006 20:41 schrieb Dan Nicholson:
> >
> > cat > dummy.c << "EOF"
> > #include
> > main(){}
> > EOF
> >
> > cc -H dummy.c
Let's try
Hi once again!
Am Sonntag, 14. Mai 2006 23:05 schrieb Mag. Leonhard Landrock:
> Am Sonntag, 14. Mai 2006 20:41 schrieb Dan Nicholson:
> > That's correct.
> >
> > Can you try this other sanity check that will actually tell us
> > something useful about how it's searching for the headers.
> >
> > ca
Am Sonntag, 14. Mai 2006 20:41 schrieb Dan Nicholson:
> That's correct.
>
> Can you try this other sanity check that will actually tell us
> something useful about how it's searching for the headers.
>
> cat > dummy.c << "EOF"
> #include
> main(){}
> EOF
>
> cc -H dummy.c
>
> That should show you
On 5/14/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
Yes, you are right. The result is different. Here it comes:
#include "..." search starts here:
#include <...> search starts here:
/tools/include
/tools/lib/gcc/i686-pc-linux-gnu/4.0.3/include
End of search list.
That's what it sh
Am Freitag, 12. Mai 2006 23:03 schrieb Dan Nicholson:
> On 5/12/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
> > /sources/gcc-build/gcc/xgcc -B/sources/gcc-build/gcc/
> > -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem
> > /usr/i686-pc-linux-gnu/include -isystem
> > /u
Hello again!
First, sorry for the late reply. I just had no time.
Am Freitag, 12. Mai 2006 21:47 schrieb Jim Gifford:
> Mag. Leonhard Landrock wrote:
> > Hi!
> >
> > I am once again at this point where compilation of gcc fails. :-(
> >
> > In file included from ../../gcc-4.0.3/gcc/crtstuff.c:64:
On 5/12/06, Mag. Leonhard Landrock <[EMAIL PROTECTED]> wrote:
/sources/gcc-build/gcc/xgcc -B/sources/gcc-build/gcc/
-B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem
/usr/i686-pc-linux-gnu/include -isystem /usr/i686-pc-linux-gnu/sys-include -O2
-DIN_GCC-W -Wall -Wwrite-
Mag. Leonhard Landrock wrote:
Hi!
I am once again at this point where compilation of gcc fails. :-(
What did I so far in this chapter?
cd /sources
cd ./gcc-4.0.3
sed -i 's/install_to_$(INSTALL_DEST) //' libiberty/Makefile.in
sed -i 's/^XCFLAGS =$/& -fomit-frame-pointer/' gcc/Ma
Hi!
I am once again at this point where compilation of gcc fails. :-(
What did I so far in this chapter?
cd /sources
cd ./gcc-4.0.3
sed -i 's/install_to_$(INSTALL_DEST) //' libiberty/Makefile.in
sed -i 's/^XCFLAGS =$/& -fomit-frame-pointer/' gcc/Makefile.in
sed -i '[EMAIL PRO
23 matches
Mail list logo
