Hi,
Thanks for the help. I guess the problem is because I had not installed
GAWK-3.0 on my system. But now I have installed it.But I am not able to
link /usr/bin/awk to gawk. How do I link it ?
I was going through the host system requirements.
I have one more question regarding diffutil . I chec
On 01/-10/-28163 01:59 PM, Bruce Dubbs wrote:
> David Reese wrote:
>> Greetings from America,
>
> Greetings from Texas :)
>
>> [First, I apologize if this message is incorrectly formatted -
>> since Thunderbird 3.0 text formatting options seem woefully
>> limited. I did the best I could to manua
> On 2 March 2010 02:05, stosss wrote:
>
>>
>> I have been building Gentoo lately, because I want to build a 64bit
>> syytem with current source code and with a book already written for
>> 64bit systems. I also want a package manager. I will continue with my
>> LFS build and move to the 64bit book
On 2 March 2010 02:05, stosss wrote:
>
> I have been building Gentoo lately, because I want to build a 64bit
> syytem with current source code and with a book already written for
> 64bit systems. I also want a package manager. I will continue with my
> LFS build and move to the 64bit book when it
On Monday, March 1, 2010, brad martin wrote:
> I think this is where a package management system comes into play. In my
> past LFS system I wrote a package manager using shell scripts much like the
> one that Slackware uses (Sorry I no longer have it). What my package manager
> did was instal
On 2 March 2010 00:04, Mike McCarty wrote:
> It occurs to me that, since LFS is not exactly a supported
> distribution in the classic sense of the term, that keeping
> it up to date might be a bit interesting. What is the
> recommended process? How does one know when, and what?
>
> Simply rebuildi
I think this is where a package management system comes into play. In my
past LFS system I wrote a package manager using shell scripts much like the
one that Slackware uses (Sorry I no longer have it). What my package
manager did was installed the software to a fakeroot and then tar-ed the
files
It occurs to me that, since LFS is not exactly a supported
distribution in the classic sense of the term, that keeping
it up to date might be a bit interesting. What is the
recommended process? How does one know when, and what?
Simply rebuilding each time there is a new release, especially when
on
I'm currently stuck on section 5.7.1 of the book. I've configured glibc
correctly afaik, and everything else has gone fine. After completing the
configure stage (I didn't change any of the configure options from what's
listed in the book), I run `make' and get the following error in [1].
The CFLA
On 1 March 2010 22:01, wrote:
> I am getting error when it tries to compile libgcc. It say that it can
> not determine object suffix. Make stops with error. Checking config.log
> does have a error that may or may not be invovled but it is with /gcc/as:
> line 77 exec: : not found
>
> Brian
>
Hi,
I'm pleased to announce the release of LFS Version 6.6. This release
includes numerous changes to LFS-6.5 (including updates to
Linux-2.6.32.8, GCC-4.4.3, Glibc-2.11.1) and security fixes. It also
includes editorial work on the explanatory material throughout the book,
improving both the c
I am getting error when it tries to compile libgcc. It say that it can
not determine object suffix. Make stops with error. Checking config.log
does have a error that may or may not be invovled but it is with /gcc/as:
line 77 exec: : not found
Brian
--
http://linuxfromscratch.org/mailman/list
Cool story, bro.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
> Mike, I have done some research on this problem and its due
> to a package
> using a define that is not supposed to be used. To
> check if string.h is
> really the problem, you only need to do:
>
> cat > t.c << "EOF"
> #include
> int main(){}
> EOF
>
> gcc -o t t.c
>
> If that compiles,
> cat > t.c << "EOF"
> #include
> int main(){}
> EOF
>
> gcc -o t t.c
>
> If that compiles, the problem is not string.h.
>
> -- Bruce
>
It compiles:
oot [ ~/test ]# cat > t.c << "EOF"
> #include
> int main(){}
> EOF
root [ ~/test ]#
root [ ~/test ]# gcc -o t t.c
root [ ~/test ]# ls -l
to
brown wrap wrote:
>> Have you tried doing a diff of the file in /usr/include and
>> the
>> one which comes "fresh" out of the tarball?
>>
>> Mike
>
I rewrapped this for you this time; however, please read
http://www.linuxfromscratch.org/faq/#netiquette
> I really don't know what happened, but B
> The safe answer is "everything". More likely is "nothing",
> so
> long as you are rebuilding identically the same version of
> gcc.
>
> More realistically, I'd try looking at string.h and find
> out
> what happened to it. Without forensic information, it's
> difficult
> to say how to proceed. W
> Incidentally, this points up the need for doing backups,
> even on
> an incompletely built system.
>
> Mike
I remembered I moved all of the compiled programs to a separate directory. I
was able to go back and do another "make install" on glibc and then gcc. I was
then able to make net-too
Mike McCarty wrote:
> brown wrap wrote:
>> I have trouble compiling once I got into BLFS. I think I clobbered
>> something during an install. Anything that tries to include:
>>
>> /usr/include/string.h won't compile. I figured out that file get
>> installed from glibc, but gcc won't compile it. So
Mike McCarty wrote:
> brown wrap wrote:
>> I have trouble compiling once I got into BLFS. I think I clobbered
>> something during an install. Anything that tries to include:
>>
>> /usr/include/string.h won't compile. I figured out that file get
>> installed from glibc, but gcc won't compile it. So
brown wrap wrote:
>
> I have trouble compiling once I got into BLFS. I think I clobbered
> something during an install. Anything that tries to include:
>
> /usr/include/string.h won't compile. I figured out that file get
> installed from glibc, but gcc won't compile it. So I need to backup
> to a
On 01/03/10 08:49, Suraj Linux wrote:
> Hi,
>
> I have getting error while executing *make* command for 5.7. Glibc-2.10.1. I
> did give all the above command. I was even able to configure with out errors.
>
> I get the following error. ( See at the end )
>
> mawk: scripts/gen-sorted.awk: line 19:
On 03/01/2010 03:49 AM, Suraj Linux wrote:
> Hi,
>
> I have getting error while executing *make* command for 5.7.
> Glibc-2.10.1. I did give all the above command. I was even able to
> configure with out errors.
>
> I get the following error. ( See at the end )
>
> mawk: scripts/gen-sorted.awk: lin
Hi,
I have getting error while executing *make* command for 5.7. Glibc-2.10.1. I
did give all the above command. I was even able to configure with out
errors.
I get the following error. ( See at the end )
mawk: scripts/gen-sorted.awk: line 19: syntax error at or near ]
mawk: scripts/gen-sorted.a
Hi,
Thank you for the help. I was able to find my problem. That is, I had
extracted it as the different user. Hence I did not have access to the
files.
Thank you.
-Suraj
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: Se
25 matches
Mail list logo
