Re: Xen-LFS hint

[Luca]

- Original Message - 
From: "Bryan Kadzban" <[EMAIL PROTECTED]>
To: "LFS Developers Mailinglist" 
Sent: Wednesday, September 05, 2007 1:05 PM
Subject: Re: Xen-LFS hint


> I'm going to guess that that's because your Gmail account is not the 
> one
> that you've subscribed to the list you're trying to post to.  I've 
> been
> hit with that too.  Subscribe it, and I'm guessing it'll work fine.

Hi Bryan.

Wrong guess.
When I changed email subscription account to Gmail one happened so I 
changed it back to another one.

Luca 

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Xen-LFS hint

[Luca]

Hello.

Sorry to say it'll take me more time than estimated.
I've got to publish a paper and waiting new hardware delivery (to be 
used to test and write the hint).

Regards,
Luca

P.S. Posts sent via my Gmail account are classified and rejected as spam
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: LFS-6.3/Hints

[Luca]

- Original Message - 
From: "Peter Ennis" <[EMAIL PROTECTED]>
To: 
Sent: Friday, August 17, 2007 10:10 PM
Subject: Re: LFS-6.3/Hints

> ... I am interested in trying LFS as Xen Dom0,
> and would want to base it on 6.3
>
> Thanks,
>
> Peter

Hello Peter.

Well, it seems I have to change a line: there are two users interested 
:)

I be back in two weeks and I'll start testing XEN-Lfs using Xen-4.0.0 
and Lfs-6.3 as dom0 and domU then write the hint.

Luca 

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: LFS-6.3/Hints

[Luca]

- Original Message - 
From: "Bruce Dubbs" <[EMAIL PROTECTED]>
To: "LFS Developers Mailinglist" 
Sent: Thursday, August 16, 2007 5:14 PM
Subject: Re: LFS-6.3/Hints



> It should probably be released by then.  The only change I know of 
> will
> be linux 2.6.22.3 and some minor text changes.  I know of no
> instruction, bootscript, udev, etc, changes fo r6.3.
>
>> 2) What about Hint Project? I mean, after writing and testing the 
>> hint,
>> posting to hint mailing list will be picked up or what? I ask because
>> state of hint project.
>
> We will get it into the repository.
>
>  -- Bruce

Hi Bruce and thanks for the reply :)


Regards,
Luca 

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: LFS-6.3/Hints

[Luca]

- Original Message - 
From: "Alan Lord" <[EMAIL PROTECTED]>
To: 
Sent: Thursday, August 16, 2007 9:49 AM
Subject: Re: LFS-6.3/Hints


> Might want to check out VirtualBox - XenSource has just been acquired 
> by
> Citrix for a very cool $500m! I don't know if this will affect xen 
> much
> but Citrix are hardly known for the Open Source contributions... ;-)
>

Hello Alan.

I'm already using VirtualBox to test projects :)

About Xen I know XenSource has been acquired and soon will be released 
version 4 (August 20).
Anyway there's XenExpress (Free Starter Package) which I'll try out; 
actually I tested using Xen source tarball 3.1.0 (built from scratch) 
and previous releases.
About OpenSource contributions... well... I know... and, as you may 
imagine, Xen-3.1.0 is no-more available to download, just to state how 
the things are :)
Anyway  there's Open Source Xen (actually up-to-date 3.1.0 release) 
freely downloadable as pre-packaged and source code.

Luca 

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

LFS-6.3/Hints

[Luca]

Hello.

I'm thinking about writing a Hint to build a XEN-Lfs (when I'll be back) 
since, at least, there's one user who asked me how to build it.
So I've got a couple of questions:
1) Is LFS-6.3 going to be released sometime during next two weeks and, 
if not, could I use it safely (I mean no expressive changes) instead of 
6.2?
2) What about Hint Project? I mean, after writing and testing the hint, 
posting to hint mailing list will be picked up or what? I ask because 
state of hint project.

Regards,
Luca 

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Gnome-Python

[Luca]

- Original Message - 
From: "Alexander E. Patrakov" <[EMAIL PROTECTED]>
To: "BLFS Development List" <[EMAIL PROTECTED]>
Sent: Monday, August 13, 2007 3:15 PM
Subject: Re: Gnome-Python


> Luca wrote:
>> no-reply received
>
> Strange. I sent my ideas on improving the proposed XML syntax. Could 
> you
> please check your "spam" folder? Due to XML tags, my message could 
> well
> end up there.
>
> -- 
> Alexander E. Patrakov

I checked and  Spam folder is empty; checked also filters and all is ok.

Could try replying to my email address using to post to lfs and blfs 
lists?

Luca 

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

Re: gcc make check

[Luca]

- Original Message - 
From: "Bruce Dubbs" <[EMAIL PROTECTED]>
To: "LFS Developers Mailinglist" 
Sent: Thursday, July 26, 2007 8:31 AM
Subject: gcc make check


>I was investigating the gcc-4.1.2 build and got the output below.  What
> was surprising to me is that there were no unexpected failures.
>
> Should the comments in the book about expecting some failures be 
> changed?
>
>  -- Bruce

Hello Bruce.

I had similar results with gcc-4.3.0-exp testsuite first (months ago) 
and last time I tried it (few days ago).

I should have the testsuite log  somewhere (I posted to Alexander first 
time I tried gcc-4.3.0), if interested I could search and post it here 
or as attachment.

Luca 

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: {B,C}LFS State of Things (was Re: SVN-20070706: ...)

[Luca]

- Original Message - 
From: "Jeremy Huntwork" <[EMAIL PROTECTED]>
To: "LFS Developers Mailinglist" 
Sent: Monday, July 23, 2007 8:51 PM
Subject: Re: {B,C}LFS State of Things (was Re: SVN-20070706: ...)


>
> That's what bringing x86_64 into LFS would be - adding what has 
> already
> been done with deviations appropriate for our BOOK/community. I'm not 
> at
> all trying to make this about me, so it's not *my* deviations. The 
> only
> reason I was the one to create the branch and start dropping in 
> changes
> is because I was hoping to create a full 64-bit LiveCD. It would be 
> very
> useful to me personally and at work, and we've had a few requests for
> such a CD on the livecd list.

Hello Jeremy.

Really I appreciate your efforts.

A full 64-bit LiveCD is interesting indeed, I'm working since last year 
to a DVD installation set covering archs I've tested and adding more 
things to installation options, deviating from LFS and BLFS so don't 
take it as related or whatever.
Now I'm looking for a good Qt4 programming book to change installer to 
have it graphical too (if one wants it) using Qt libraries (I don't like 
Gtk, that's all).

Best wishes,
Luca 

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: {B,C}LFS State of Things (was Re: SVN-20070706: ...)

[Luca]

- Original Message - 
From: "Bryan Kadzban" <[EMAIL PROTECTED]>
To: "LFS Developers Mailinglist" 
Sent: Saturday, July 21, 2007 2:49 PM
Subject: Re: {B,C}LFS State of Things (was Re: SVN-20070706: ...)


> According to their site, it is maintained, just no new features are
> being added.  (Though I'm not sure what sense of the word "maintained"
> they're using then... but whatever.  Presumably it just means they'd
> still fix bugs if there are any.)

Hello Bryan.

I used "maintained" simply according to your words: only fixes but dead 
for all the rest.

Happy testing :)
Luca 

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: {B,C}LFS State of Things (was Re: SVN-20070706: ...)

[Luca]

- Original Message - 
From: "Jeremy Huntwork" <[EMAIL PROTECTED]>
To: "LFS Developers Mailinglist" 
Sent: Friday, July 20, 2007 10:54 PM
Subject: Re: {B,C}LFS State of Things (was Re: SVN-20070706: ...)


> Indeed. I meant to drop something in, but forgot about it. bin86/lilo
> would probably be alright. Anyone tried grub2?
>

Hello.

Grub-0.9x is old Grub legacy and no-more maintained.

Grub-1.x is new one (latest I tried was 1.95, release 2006-10-15) but 
it's still experimental and doesn't support all file-systems features 
(xfs btrees aren't supported as example) but it will support much 
file-systems than old one; I tried it only x86 but there was a similar 
discussion in Debian for x86-64 arch support.

Supported archs are: PC (i386), Mac (powerpc), Pegasos II (powerpc), 
Sparc v9 (Sun UltraSparc) - under development, Mac (i386) - under 
development.
Supported file-systems: ext2, fat (+ long filenames), ufs (versions 1 
and 2), minix (versions 1 and 2), iso9660 (plus rockridge extensions), 
jfs, hfs, affs, sfs, xfs (no btrees).
Supported loaders: PC (chainloader, linux, multiboot), Mac (linux).
Terminals: PC (VGA framebuffer, textmode, VESA framebuffer - in 
progress), PPC & UltraSparc ( ANSI - Open Firmware).
Partition maps: standard pc and extended partitions, BSD partitions, 
Macintosh partitions, Amiga style partitions (RDB), Sun partitions, GPT 
(used by EFI).
Features: memory management, module loading, font support (framebuffer 
only), grub-emu (testing/debugging), argument parsing interface, 
rescue/normal mode, variable support, compression support, command 
history/tab completion (normal mode), scripting.

Anyway you can find more on the GRUB Wiki - http://grub.enbug.org/ - 
under GRUB 2.

Regards,
Luca 

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Safer linux-headers install

[Luca]

- Original Message - 
From: "Dan Nicholson" <[EMAIL PROTECTED]>
To: "LFS Developers Mailinglist" 
Sent: Saturday, July 14, 2007 5:38 PM
Subject: Re: Safer linux-headers install


> So, I thought about this a little and decided to just use the hammer
> approach of INSTALL_HDR_PATH=dest, cp dest/include/* /usr/include. I
> don't feel real comfortable depending on variables internal to their
> headers script. We can change this if the consensus changes, but for
> now I'm just going to push in the simple version.
>
> --
> Dan

Hello Dan.

Thanks for the reply and taking it under consideration.

Instead I'm sorry but haven't had the time to check about the headers 
installed with wrong permissions issue; Thor's hammer on me :)
Anyway I promise I'll check and eventually report it; the only thing I 
can say is that I read many people having this one.

Regards,
Luca

P.S. Last days I changed email address globally but mails were rejected 
as spam and I had to change it again; I sent a mail to the postmaster 
but had no response... 

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Safer linux-headers install

[Luca]

> - Original Message - 
> From: "Dan Nicholson" <[EMAIL PROTECTED]>
> To: "LFS Developers Mailinglist" 
> Sent: Wednesday, July 11, 2007 3:16 PM
> Subject: Re: Safer linux-headers install
> 
> 
>> Unless it's going to be accepted upstream, then I'm not really
>> interested in adding a patch here which takes one extra command to
>> workaround. Which, now that I look again, makes this much easier to
>> solve.
>> 
>> # make INSTALL_HDR_PATH=/usr oldheaders= headers_install
>> 
 
 It can be used "make INSTALL_HDR_PATH=/usr oldheaders= unwanted= 
 headers_install" too; it's definitely simpler.
 
 Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Safer linux-headers install

[Luca/Gmail]

- Original Message - 
From: "Dan Nicholson" <[EMAIL PROTECTED]>
To: "LFS Developers Mailinglist" 
Sent: Wednesday, July 11, 2007 3:16 PM
Subject: Re: Safer linux-headers install


> Unless it's going to be accepted upstream, then I'm not really
> interested in adding a patch here which takes one extra command to
> workaround. Which, now that I look again, makes this much easier to
> solve.
> 
> # make INSTALL_HDR_PATH=/usr oldheaders= headers_install
> 

It can be used "make INSTALL_HDR_PATH=/usr oldheaders= unwanted= 
headers_install" too; it's definitely simpler.

Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Default filesystem

[Luca]

Luca ha scritto:
> I think that it depends on the system you're building, example you could 
> build LFS on a flash device, on a machine with another os or building on 
> a supercomputer or something requiring an "advanced" setup.
>
>   

I don't know if that's what you mean but I could take the examples of a 
fully XEN-LFS (already done), a HASH-LFS (already done), a SELinux-LFS 
(I have to try this yet); these "setups" require some changes at 
toolchain and kernel level so they "could" be "bare" system changes.

Have a nice weekend,
Friendly,
Luca

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Default filesystem

[Luca]

Hi Richard.

Thanks for the answer.

I think that it depends on the system you're building, example you could 
build LFS on a flash device, on a machine with another os or building on 
a supercomputer or something requiring an "advanced" setup.

In a reply I took the simple example of using a different filesystem.

Anyway I can write some hints, as per your suggestion :)

Could you please clarify me what do you mean with "something it can't 
handle" ?

Best wishes,
friendly,
Luca.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Default filesystem

[Luca]

TheOldFellow ha scritto:
> Dan Nicholson wrote:
>   
>> On 2/3/07, TheOldFellow <[EMAIL PROTECTED]> wrote:
>> 
>>> What I need is something it can't handle, like Udev for several months a
>>> year ago, or a new booting scheme...
>>>   

Hi.

I think, but not sure about, something not handled could be LVM, Flash 
devices, dual boots (I managed a dual boot between LFS and Solaris with 
ZFS filesystem) etc... too.

Right, some things require an "advanced" setup as said by Alexander, 
this is true, but at least there could be some examples or some hints 
pointers or notes...

I know that maybe a newbie would try to follow or to apply these setups 
without having knowledge or capabilities and that "Gurus" probably don't 
need those indications but these are, imo, "bare" system choices.

Friendly,
Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Default filesystem

[Luca]

TheOldFellow ha scritto:
> Dan Nicholson wrote:
>   
>> On 2/3/07, TheOldFellow <[EMAIL PROTECTED]> wrote:
>> 
>>> What I need is something it can't handle, like Udev for several months a
>>> year ago, or a new booting scheme...
>>>   

Hi.

I think, but not sure about, something not handled could be LVM, Flash 
devices, dual boots (I managed a dual boot between LFS and Solaris with 
ZFS filesystem) etc... too.

Right, some things require an "advanced" setup as said by Alexander, 
this is true, but at least there could be some examples or some hints 
pointers or notes...

I know that maybe a newbie would try to follow or to apply these setups 
without having knowledge or capabilities and that "Gurus" probably don't 
need those indications but these are, imo, "bare" system choices.

Friendly,
Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Default filesystem

[Luca]

Hi Dan.

I didn't mean that it is said you *must* or some editor's preference or 
else I simply mean another thing, here reported some of his words 
(Alexader) in a private conversation:

"Anyway, I am afraid that any attempt to build LFS on any filesystem 
other than ext3 is now considered an unforgivable deviation from the 
book (reason for such thought: for a long time, reiserfsprogs failed to 
build, and xfsprogs page contained a dead link - but both issues are 
fixed now)."

This led me to such reflection; I mean, if it is considered an " 
unforgivable deviation" from the book it could imply that Ext3 is 
officially supported while others not.

I hope that now what I meant is clearer...

Friendly,
Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Default filesystem

[Luca]

Hi.

Only a reflection.
LFS officially supports Ext3 as default file-system and in BLFS book we 
find under File Systems ReiserFS and XFS progs. These filesystems are 
judged stable (Reiser4 is not judgeable as it is too young but it's 
faster than those; I found only a bug after testing it for some months, 
a temporary disk freeze - minutes - after some working hours) so why not 
adding official support for Ext2 (too old and replaced by Ext3), Ext3 
(to be replaced by Ext4), ReiserFS and XFS as possible default filesystem?
It should be possible to add experimental support for Reiser4 too (as 
stated by Alexander and me it works well with LFS-6.2; anyway I started 
experimenting it some months ago with lfs-svn versions) but it has some 
required pre-requisites and some extra packages need to be added in 
LFS-book - this is valid for ReiserFS/XFS too.
I, for a "project" of mine, tried LFS using other file-systems too: IBM 
JFS, Axis JFFS and Red Hat JFFS2.

Friendly,
Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Wiki registration

[Luca]

Matthew Burgess ha scritto:
> Sorry about that, Luca.  Should be fixed now.
>
> Regards,
>
> Matt.
>   

Hi Matt.

Thanks, it now worked :)

Friendly,
L.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Wiki registration

[Luca]

Hi.

I just tried to create an account for lfs-wiki ended up in an error, 
here reported:


Oops…
Trac detected an internal error:

If you think this really should work and you can reproduce it, you 
should consider reporting this problem to the Trac team.

Go to http://trac.edgewall.org/ and create a new ticket where you 
describe the problem, how to reproduce it. Don't forget to include the 
Python traceback found below.

TracGuide — The Trac User and Administration Guide
Python Traceback

Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 387, in 
dispatch_request
dispatcher.dispatch(req)
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 237, in 
dispatch
resp = chosen_handler.process_request(req)
  File "build/bdist.linux-i686/egg/acct_mgr/web_ui.py", line 302, in 
process_request
  File "build/bdist.linux-i686/egg/acct_mgr/web_ui.py", line 53, in 
_create_user
  File "build/bdist.linux-i686/egg/acct_mgr/api.py", line 98, in 
set_password
  File "build/bdist.linux-i686/egg/acct_mgr/htfile.py", line 70, in 
set_password
  File "build/bdist.linux-i686/egg/acct_mgr/htfile.py", line 121, in 
_update_file
IOError: [Errno 2] No such file or directory: 
u'/usr/local/trac/LFS/lfs.htpasswd'

Friendly,
L.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Wiki prob

[Luca]

Luca ha scritto:
> Hi.
>
> Just a (maybe, but not intentional) provocatory question:
>
> Since yesterday I can't login anymore in blfs-wiki; tried several times 
> but nothing, tried creating another "profile" but ended up in trac errors.
> So, now the question: is it a trac problem? a censorship? a ban? a boycott?
>
> In case of an answer I *want* the truth.
>
> Friendly,
> L.
>   
Please don't feel offended or whatever else (anyway I clarified 
privately with Bruce)...
As I said him I have no will in starting a flamewar or what... but 
because of some things I had some thinkings and I have no probs in 
saying this in public... it may not be polite (sorry for this) but I 
simply and honestly asked... it wasn't accusation or else... (not my 
intention)

In case, as said in way off-topic, if the community would like to accept 
apologies here are mine.


Friendly,
L.
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: FAQ bit rot

[Luca]

Alexander E. Patrakov ha scritto:
>
>
> Conclusion: reiser4 filesystem works just fine for LFS-6.2 build.
>
>   

Hi Alex.

May I ask you eventual build-order changes or what? I tried installing 
on reiser4 without adding glibc-headers and worked the same.

L.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: FAQ bit rot

[Luca]

Luca ha scritto:
>> Host system should support Reiser4 file-system (latest official patch
>> for Reiser4 is for linux kernel 2.6.18.3

No more true; I just looked at namesys site and latest official 
reiser4-for-2.6 patch is reiser4-for-2.6.19-2.

L.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: FAQ bit rot

[Luca]

Alexander E. Patrakov ha scritto:
> I used ums.usu.ru because it is faster than my home computer, has more disk 
> space, zero-cost Internet access, and because nobody objects to its noise. 
> However, this is a remote (5 km away from me) server with 24/7 uptime 
> requirement, thus, I had to use virtualization.
>
>   

It wasn't an objection or a critic... (sorry if misunderstood)
I simply added some extra infos about my trying with reiser4, nothing else.


Friendly,
L.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: FAQ bit rot

[Luca]

Alexander E. Patrakov ha scritto:
> Luca wrote:
>
>   
>> In Faq, point General compilation errors there's a "Glibc compilation
>> errors out due to a missing nss.h header file".
>> Following the link points to:
>>
>> Glibc compilation errors out due to a missing nss.h header file
>>
>> This usually indicates that you are compiling LFS onto a Reiser4
>> partition. Unfortunately, there is currently no known solution, other
>> than to use a different type of filesystem.
>> 
>
> Just in order to test this, I created a VMware virtual machine (based on LFS 
> LiveCD 6.2-5) on ums.usu.ru. The virtual disk is formatted as reiser4. Let 
> jhalfs run for the night, and tomorrow I'll see if this FAQ item is valid.
>
> OTOH,
>
> 1) the NASM requirement for LILO (mentioned in the FAQ) is no longer valid.
> 2) The locale example in the "Why does less (and therefore man) print  
> instead of hyphens?" item is horribly wrong.
> 3) "Glibc fails and mentions BEGIN and END" mentions static linking, which 
> applies to the old book only, and only confuses the reader who doesn't know 
> all the LFS history.
> 4) "... it is normal to compile GNU libc with the `linuxthreads' add-on..." 
> - again, old book.
>
> So there is enough bit rot :(
>
>   
>> Actually this answer is not fully correct. It's possible to compile LFS
>> natively on a Reiser4 partition at some extra costs:
>>
>> Host system should support Reiser4 file-system (latest official patch
>> for Reiser4 is for linux kernel 2.6.18.3, in case booting with grub of
>> host-system, libaal, reiser4progs and libreiser4 must be installed, grub
>> must be re-installed after patching it to support Reiser4 (patch found
>> at official NAMESYS site), reiser4progs needed, if a Reiser4 partition
>> was created with mkfs.reiser4 version < 1.0.0, must be run
>> debugfs.reiser4 -C device, fsck.reiser4 device.
>> 
>
> Let's hope that the only incorrect bit above is that the reiser4 patch 
> works. The fact is that it causes unacceptable regression for all other 
> filesystems (that's why I had to release LFS LiveCD 6.2-5). The "fix" is to 
> set CFLAGS to "-O0" or "-O1" while compiling GRUB.
>
>   
Hi Alex.

Well, at that time I used this way to build LFS natively on reiser4, not 
virtualizing or whatever else; I added support for Reiser4 in the 
host-system and formatted lfs-partition to reiser4. Then started 
building there and everything worked; then just to be sure, since I had 
some extra unused space on disk, I booted lfs-reiser4 with its own grub 
(compiled with CFLAGS set to "-00") created the reiser4 partition from 
there and installed a new lfs all (host and new lfs) on reiser4 and 
everything worked without errors.

L.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: [Fwd: LFS natively on Reiser4]

[Luca]

Luca ha scritto:
> Here's attached the original email I sent to faq list.
>
> With best wishes,
> Friendly,
> Luca
>

Sorry, forgot to say that I reposted here because of a suggestion from Alex.

L.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

[Fwd: LFS natively on Reiser4]

[Luca]

Here's attached the original email I sent to faq list.

With best wishes,
Friendly,
Luca
--- Begin Message ---
Hi all!

In Faq, point General compilation errors there's a "Glibc compilation
errors out due to a missing nss.h header file".
Following the link points to:

Glibc compilation errors out due to a missing nss.h header file

This usually indicates that you are compiling LFS onto a Reiser4
partition. Unfortunately, there is currently no known solution, other
than to use a different type of filesystem.


Actually this answer is not fully correct. It's possible to compile LFS
natively on a Reiser4 partition at some extra costs:

Host system should support Reiser4 file-system (latest official patch
for Reiser4 is for linux kernel 2.6.18.3, in case booting with grub of
host-system, libaal, reiser4progs and libreiser4 must be installed, grub
must be re-installed after patching it to support Reiser4 (patch found
at official NAMESYS site), reiser4progs needed, if a Reiser4 partition
was created with mkfs.reiser4 version < 1.0.0, must be run
debugfs.reiser4 -C device, fsck.reiser4 device.
After that the build order must be changed a little:

Chapter 5. Constructing a Temporary System:
Linux-Headers
Binutils-2.17 - Pass 1
Glibc-Headers
GCC-4.1.1 - Pass1
Glibc-2.5
and then proceeding normally.

LFS-kernel must be patched for Reiser4.
If booting from LFS-grub libaal, reiser4progs and libreiser4 must be
installed before grub and grub must be patched to support Reiser4.

Just to be sure Glibc-Headers could be installed after linux-headers on
final system.

Following this way I'm building all my LFS systems natively on Reiser4
partitions; anyway, obviously, before, eventually, modifying the FAQ
feel free to try and test.


Bye,
Luca

--- End Message ---
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: KDE and dbus

[Luca]

Bruce Dubbs ha scritto:
> What I still don't understand is why one could get into
> the situation that "packages install a D-Bus  .service file outside of
> the standard /usr/share/dbus-1/services directory".  Have you run in
> that situation?
>
>
>   -- Bruce
>   

Hi Bruce.

I don't know if it can be compared or what but I've ran into the same 
situation of .service files outside /usr/share/dbus-1/services 
installing Gnome-2.14.2 and Gnome-2.16.0 (not in the book) as per book.

In the specific .service files are:

/opt/gnome-2.14.2/share/dbus-1/services
/{net.ekiga.helper.service,net.ekiga.instance.service,org.gnome.Epiphany.service,org.gnome.SettingsDaemon.service}

and for Gnome-2.16.0, in addition to ones above

/opt/gnome-2.16.0/share/dbus-1/services/gnome-vfs-daemon.service.

I simply added the two servicedirs in session-local.conf.

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

Re: Book rendering

[Luca]

M.Canales.es wrote:
> Yes, it's broken. In the first xsltproc command the --xinclude option is 
> missing. And when generating the blfs-book.tex file the parsing fails with:
>
> compilation error: 
> file /usr/share/docbook/db2latex-xsl-0.8pre1/xsl/qandaset.mod.xsl line 366 
> element template
> xsl:template: error duplicate name 'question.answer.label'
>
> That is due a bug in db2latex that could be avoided by commenting out the 
> line 
>
> 
>
> in db2latex-xsl-0.8pre1/xsl/docbook.xsl.
>
> The parsing will still output several errors but blfs-book.tex is created. I 
> don't know if that tex file can be compiled due that that don't have 
> installed TeX or LaTeX right now, but the last time I tried, more than 2 
> years ago, the PDF generated was bugy and very ugly.
>
>
>   
Thanks for the answer Manuel.

Now it's clearer; I'm not 100% sure but when I passed make tex maybe the
errors were others and not the one you mentioned, they should be
something like DB2Latex: Need to process XPath match book/xi:include but
as already said not sure.
I tried to process other tex files and it seems to work; dunno.
Debian uses db2lated with a patch of its own but don't know if it solves
the problem.

Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Book rendering

[Luca]

Luca wrote:
> Bruce Dubbs wrote:
>   
>> Why do you think the db2latex is required?  BLFS has teTeX.  The
>> makefile generates a TeX file (blfs-book.tex), not a LaTeX file.  To
>> create the TeX version of the book, just:
>>
>> tex blfs-book.tex
>>
>>   -- Bruce
>>   
>> 
> Hi Bruce.
>
> It's not that I think is required; when I tried passing "make tex" in
> book-sources it complained about missing db2latex with TeTex and LaTex
> installed.
> So that's the source of my question.
>
> Luca
>   
Forgot a PS.

The book-sources were old (and if I remember it was said "make tex" for
target) so maybe now has changed and I never tried again; I'll now try
with the tex blfs-book.tex.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Book rendering

[Luca]

Bruce Dubbs wrote:
>
>
> Why do you think the db2latex is required?  BLFS has teTeX.  The
> makefile generates a TeX file (blfs-book.tex), not a LaTeX file.  To
> create the TeX version of the book, just:
>
> tex blfs-book.tex
>
>   -- Bruce
>   
Hi Bruce.

It's not that I think is required; when I tried passing "make tex" in
book-sources it complained about missing db2latex with TeTex and LaTex
installed.
So that's the source of my question.

Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Book rendering

[Luca]

Hello again.

To Manuel:

A question about book rendering:

In blfs-book-sources Makefile there's the target "make tex" that has the
dependency of db2latex; the latter is not installed in blfs-book (I
installed it following the stylesheets installation); when I tried
passing "make tex" it broke (don't remember exactly the point).

Can you explain me about the possible tex target and not including in
blfs the required dependency?


Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Threads

[Luca]

Hi all.

I have a couple of question about thread support (one asked yesterday to
Alexander)


1) In LFS Perl-5.8.8 is installed without thread support. Can anyone
explain me the reasons? (Alexander told me something about breaking some
scripts)
2) To Randy: In All_of_gcc_during_lfs.txt hint MPFR is installed with
"--enable-thread-safe". Reason?

Thanks,
Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: LFS-Hash-Style

[Luca]

Hello and good afternoon to all.

As promised I tried to send the log-tarball of chapter 6, anyway the
message body is too big.

Note: this try-hash-style-lfs built natively on reiser4 file-system from
a non-capable hash-style host-system (another lfs).

CPU: Authentic AMD64 3300+
cpu MHz 2000.428
fpu : yes
fpu_exception   : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt
lm 3dnowext 3dnow up pni lahf_lm ts fid vid ttp tm stc
bogomips: 4005.69

Host-System
LD: GNU ld version 2.17
GCC: gcc (GCC) 4.1.1
GLIBC: GNU C Library development release version 2.4

Final-System
LD: GNU ld version 2.17.50 20061129
GCC: gcc (GCC) 4.3.0 20061205 (experimental)
GLIBC: GNU C Library development release version 2.5.90

Final-System GCC SPECS:
gcc -dumpspecs
*asm:
%{v:-V} %{Qy:} %{!Qn:-Qy} %{n} %{T} %{Ym,*} %{Yd,*} %{Wa,*:%*}

*asm_debug:
%{gstabs*:--gstabs}%{!gstabs*:%{g*:--gdwarf2}}

*asm_final:


*asm_options:
%a %Y %{c:%W{o*}%{!o*:-o %w%b%O}}%{!c:-o %d%w%u%O}

*invoke_as:
%{!S:-o %|.s |
 as %(asm_options) %|.s %A }

*cpp:
%{posix:-D_POSIX_SOURCE} %{pthread:-D_REENTRANT}

*cpp_options:
%(cpp_unique_options) %1 %{m*} %{std*&ansi&trigraphs} %{W*&pedantic*}
%{w} %{f*} %{g*:%{!g0:%{!fno-working-directory:-fworking-directory}}}
%{O*} %{undef} %{save-temps:-fpch-preprocess}

*cpp_debug_options:
%{d*}

*cpp_unique_options:
%{C|CC:%{!E:%eGCC does not support -C or -CC without -E}} %{!Q:-quiet}
%{nostdinc*} %{C} %{CC} %{v} %{I*&F*} %{P} %I %{MD:-MD
%{!o:%b.d}%{o*:%.d%*}} %{MMD:-MMD %{!o:%b.d}%{o*:%.d%*}} %{M} %{MM}
%{MF*} %{MG} %{MP} %{MQ*} %{MT*} %{!E:%{!M:%{!MM:%{MD|MMD:%{o*:-MQ
%*} %{remap} %{g3:-dD} %{H} %C %{D*&U*&A*} %{i*} %Z %i
%{fmudflap:-D_MUDFLAP -include mf-runtime.h} %{fmudflapth:-D_MUDFLAP
-D_MUDFLAPTH -include mf-runtime.h} %{E|M|MM:%W{o*}}

*trad_capable_cpp:
cc1 -E %{traditional|ftraditional|traditional-cpp:-traditional-cpp}

*cc1:
%(cc1_cpu) %{profile:-p}

*cc1_options:
%{pg:%{fomit-frame-pointer:%e-pg and -fomit-frame-pointer are
incompatible}} %1 %{!Q:-quiet} -dumpbase %B %{d*} %{m*} %{a*}
%{c|S:%{o*:-auxbase-strip %*}%{!o*:-auxbase %b}}%{!c:%{!S:-auxbase %b}}
%{g*} %{O*} %{W*&pedantic*} %{w} %{std*&ansi&trigraphs} %{v:-version}
%{pg:-p} %{p} %{f*} %{undef} %{Qn:-fno-ident} %{--help:--help}
%{--target-help:--target-help} %{!fsyntax-only:%{S:%W{o*}%{!o*:-o
%b.s}}} %{fsyntax-only:-o %j} %{-param*}
%{fmudflap|fmudflapth:-fno-builtin -fno-merge-constants}
%{coverage:-fprofile-arcs -ftest-coverage}

*cc1plus:


*link_gcc_c_sequence:
%{static:--start-group} %G %L %{static:--end-group}%{!static:%G}

*link_ssp:
%{fstack-protector:}

*endfile:
%{ffast-math|funsafe-math-optimizations:crtfastmath.o%s}  
%{shared|pie:crtendS.o%s;:crtend.o%s} crtn.o%s

*link:
%{!static:--eh-frame-hdr} -m %(link_emulation) --hash-style=gnu
%{shared:-shared}   %{!shared: %{!ibcs:   %{!static:  
%{rdynamic:-export-dynamic}%{!dynamic-linker:-dynamic-linker
%(dynamic_linker)}}%{static:-static}}}

*lib:
%{pthread:-lpthread}%{shared:-lc}%{!shared:%{mieee-fp:-lieee}
%{profile:-lc_p}%{!profile:-lc}}

*mfwrap:
 %{static: %{fmudflap|fmudflapth:  --wrap=malloc --wrap=free
--wrap=calloc --wrap=realloc --wrap=mmap --wrap=munmap --wrap=alloca}
%{fmudflapth: --wrap=pthread_create}} %{fmudflap|fmudflapth: --wrap=main}

*mflib:
%{fmudflap|fmudflapth: -export-dynamic}

*link_gomp:


*libgcc:
%{static|static-libgcc:-lgcc
-lgcc_eh}%{!static:%{!static-libgcc:%{!shared-libgcc:-lgcc --as-needed
-lgcc_s --no-as-needed}%{shared-libgcc:-lgcc_s%{!shared: -lgcc

*startfile:
%{!shared: %{pg|p|profile:gcrt1.o%s;pie:Scrt1.o%s;:crt1.o%s}}  
crti.o%s %{static:crtbeginT.o%s;shared|pie:crtbeginS.o%s;:crtbegin.o%s}

*switches_need_spaces:


*cross_compile:
0

*version:
4.3.0

*multilib:
. ;

*multilib_defaults:


*multilib_extra:


*multilib_matches:


*multilib_exclusions:


*multilib_options:


*linker:
collect2

*link_libgcc:
%D

*md_exec_prefix:


*md_startfile_prefix:


*md_startfile_prefix_1:


*startfile_prefix_spec:


*sysroot_spec:
--sysroot=%R

*sysroot_suffix_spec:


*sysroot_hdrs_suffix_spec:


*cc1_cpu:
%{!mtune*: %{m386:mtune=i386 %n`-m386' is deprecated. Use `-march=i386'
or `-mtune=i386' instead.
} %{m486:-mtune=i486 %n`-m486' is deprecated. Use `-march=i486' or
`-mtune=i486' instead.
} %{mpentium:-mtune=pentium %n`-mpentium' is deprecated. Use
`-march=pentium' or `-mtune=pentium' instead.
} %{mpentiumpro:-mtune=pentiumpro %n`-mpentiumpro' is deprecated. Use
`-march=pentiumpro' or `-mtune=pentiumpro' instead.
} %{mcpu=*:-mtune=%* %n`-mcpu=' is deprecated. Use `-mtune=' or
'-march=' instead.
}} %http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Autotools

[Luca]

Alexander E. Patrakov wrote:
> Luca wrote:
>> Another bug, manifested in grub-0.97, after applying reiser4 patch:
>> automake --add-missing
>>
>> docs/Makefile.am:3: compiling `kernel.c' with per-target flags requires
>> `AM_PROG_CC_C_O' in `configure.ac'
>> /usr/share/automake-1.10/am/depend2.am: am__fastdepCCAS does not appear
>> in AM_CONDITIONAL
>> /usr/share/automake-1.10/am/depend2.am:   The usual way to define
>> `am__fastdepCCAS' is to add `AM_PROG_AS'
>>   
> patch -Np1 -i ../grub-0.97-reiser4-20050808.diff
> # This will fail to add -fno-strict-aliasing to CFLAGS,
> # but this flag is already present on the CD. So ignore the reject.
> patch -Np1 -i ../grub-0.97-disk_geometry-1.patch || true
> # Fixes the incompatibility with new autotools
> sed -i 's/AM_INIT_AUTOMAKE/&\nAM_PROG_AS/' configure.ac
>
> autoreconf --force --install --verbose
> CFLAGS="-Os -s -pipe -fno-strict-aliasing" ./configure --prefix=/usr
> make
> make install
>
Hi Alex!

Yes, I know, already done, however strictly speaking it's a bug in automake.

Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Autotools

[Luca]

Luca wrote:
> Hello and good morning!
>
>
> Just a note about autotools.
>
> There's a bug that makes the "checking for working mktime..." loops
> for a while. I'm experiencing this with various packages, latest in
> timeline gawk-3.1.5 (others: bash, coreutils, findutils, just as examples).
>
>
> Luca
>   
Another bug, manifested in grub-0.97, after applying reiser4 patch:
automake --add-missing

docs/Makefile.am:3: compiling `kernel.c' with per-target flags requires
`AM_PROG_CC_C_O' in `configure.ac'
/usr/share/automake-1.10/am/depend2.am: am__fastdepCCAS does not appear
in AM_CONDITIONAL
/usr/share/automake-1.10/am/depend2.am:   The usual way to define
`am__fastdepCCAS' is to add `AM_PROG_AS'

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: Autotools

[Luca]

Hello and good morning!


Just a note about autotools.

There's a bug that makes the "checking for working mktime..." loops
for a while. I'm experiencing this with various packages, latest in
timeline gawk-3.1.5 (others: bash, coreutils, findutils, just as examples).


Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: LFS-Hash-Style

[Luca]

Luca wrote:
>
> Problems solved and a working toolchain is going to be finished in some
> time so I could post a tarball of testsuites logs for chapter6 today
> (probably this afternoon - timezone Europe/Rome).
>   

Good evening.

Sorry but my prevision can't be respected; chapter 6 testsuites still
run (now running automake-1.10 testsuites).
Just two notes: in gcc-4.3.0 testsuite no libmudflap FAILS, all tests
PASSED; glibc-2.5.90 testsuite produced 8 errors, which I have already
reported this morning but still no answer yet.

Then a curiosity:

gcc -shared -Wl,-soname,`basename ../lib/libformw.so.5.5
.5.5`.5,-stats,-lc -o ../lib/libformw.so.5.5 ../obj_s/fld_arg.o
../obj_s/fld_attr.o ../obj_s/fld_current.o ../obj_s/fld_def.o
../obj_s/fld_dup.o ../obj_s/fld_ftchoice.o ../obj_s/fld_ftlink.o
../obj_s/fld_info.o ../obj_s/fld_just.o ../obj_s/fld_link.o
../obj_s/fld_max.o ../obj_s/fld_move.o ../obj_s/fld_newftyp.o
../obj_s/fld_opts.o ../obj_s/fld_pad.o ../obj_s/fld_page.o
../obj_s/fld_stat.o ../obj_s/fld_type.o ../obj_s/fld_user.o
../obj_s/frm_cursor.o ../obj_s/frm_data.o ../obj_s/frm_def.o
../obj_s/frm_driver.o ../obj_s/frm_hook.o ../obj_s/frm_opts.o
../obj_s/frm_page.o ../obj_s/frm_post.o ../obj_s/frm_req_name.o
../obj_s/frm_scale.o ../obj_s/frm_sub.o ../obj_s/frm_user.o
../obj_s/frm_win.o ../obj_s/fty_alnum.o ../obj_s/fty_alpha.o
../obj_s/fty_enum.o ../obj_s/fty_int.o ../obj_s/fty_ipv4.o
../obj_s/fty_num.o ../obj_s/fty_regex.o -L../lib -lncursesw
/usr/bin/ld: total time in link: 0.196011
/usr/bin/ld: data size 2911036

Friendly,
Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: LFS-Hash-Style

[Luca]

Good morning.

Toolchain finished:

Book followed: LFS-SVN-20061201.

Variations:

Linux-Headers: 2.6.19;
Binutils-2.17.50-20061129;
Glibc-2.5.90;
Gcc-4.3.0-20061205.

Perl-5.8.8 slightly modified because of Autoconf-2.61 and Gcc-4.3.0.

Packages added to toolchain:
Autoconf-2.61;
Autogen-5.8.7;
Automake-1.10;
Bison-2.3;
Flex-2.5.33;
Gmp-4.2.1;
Gperf-3.0.2;
Guile-1.6.7;
Indent-2.2.9;
Libtool-1.5.22;
Libxml2-2.6.26;
Mpfr-2.2.1.

Now I'll start the final system.

Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: LFS-Hash-Style

[Luca]

Luca wrote:
> Hello; trying another toolchain I've been encumbered by the "old" cannot
> compute sizeof (long double), 77.
>
> Just a note not hash-style related:
>
> When compiling gcc with java language enabled for the awt to work
> correctly it should be passed "--enable-java-awt=[gtk,xlib,qt]".
>
> Luca
>
>   
Hello;

Problems solved and a working toolchain is going to be finished in some
time so I could post a tarball of testsuites logs for chapter6 today
(probably this afternoon - timezone Europe/Rome).
A behavior I just saw: gcc-4.3.0 uses bootstrap by default unless
specified "--disable-bootstrap" in configure. I configured gcc-pass2
with "--disable-bootstrap" and while the specs tell it uses exclusively
"--hash-style=gnu" it didn't compile itself with hash-style (which
happens when bootstrapping). For the make the choices are the "standard"
ones: make, make bootstrap or make profiledbootstrap.
Bootstrap phase consists of: creating a prev-gcc (xgcc) to use to
compiling itself and the bootstrap uses stage{2,3} and compiles finally
in stage4.
Note: as I already reported to re-compile gcc after gcc-pass1 gmp/mpfr
needed otherwise it broke during configure.
Note2: For the testsuites I'll check but I didn't find yet
testsuites-results on native reiser4 file-systems so I don't have much
to compare except for results on other file-systems.

To Bruce, Randy or other of blfs team:
Note: about gcc compiled with java support: yesterday I posted the note
about the "--enable-jawa-awt=[gtk,xlib,qt]". Yesterday afternoon I
talked with Alexander and talked about a possible note in book to say,
for example:
If you would like to compile gcc-suite with java (gcj) language support,
for the awt to work correctly you have to re-install gcc after X, gtk,
qt, libart and pass to configure: "--with-x"
"--enable-java-awt=[gtk,xlib,qt]" "--enable-gtk-cairo"
"--with-libart-prefix=[prefix]".


Friendly,
Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: LFS-Hash-Style

[Luca]

Hello; trying another toolchain I've been encumbered by the "old" cannot
compute sizeof (long double), 77.

Just a note not hash-style related:

When compiling gcc with java language enabled for the awt to work
correctly it should be passed "--enable-java-awt=[gtk,xlib,qt]".

Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: LFS-Hash-Style

[Luca]

Hello and sorry if I didn't tell anything but had various problems.

Actually it seems that I found a working toolchain, but the script never
ended building it.

Note: Host system doesn't know "--hash-style".

Anyway here's the list:

Kernel-headers-2.6.19
Glibc-headers-2.5.90
Glibc-2.5.90
Binutils-Pass1-2.17.50-20061129
Gcc-Pass1-4.3.0-20061201
Adjusting the toolchain
Tcl-8.4.14-Pass1
Expect-5.43.0-Pass1
DejaGNU-1.4.4-Pass1
Gmp-4.2.1-Pass1
Mpfr-2.2.1-Pass1
Gcc-Pass2-4.3.0
Binutils-Pass2-2.17.50
Gcc-4.3.0-Pass3

Actually to overcome a problem I had to do an "export gcc="gcc -Xlinker
-I/tools/lib/ld-linux.so.2"" otherwise libgcc_s.so.1 and the other gcc
libraries uses host /lib/ld-linux.so.2 in spite of the fact the binaries
use /tools/lib/ld-linux.so.2.

Luca
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

LFS-Hash-Style

[Luca]

Hi to everyone!

I've started the build of LFS-hash-style since Bruce said he was interested.
Actually I've just installed gcc-pass1 in toolchain; building on a
native Reiser4 file-system.

Host-system: LFS-SVN-20060906 (with some updates).

Version-check:
bash, version 3.2.5(1)-release
Binutils: version 2.17
bzip2,  Version 1.0.3, 15-Feb-2005.
Coreutils:  6.4
diff (GNU diffutils) 2.8.1
GNU find version 4.2.28
GNU Awk 3.1.5
gcc (GCC) 4.1.1
GNU C Library development release version 2.4,
grep (grep GNU) 2.5.1
gzip 1.3.5
Linux version 2.6.18.3 (gcc version 4.1.1)
GNU Make 3.81
patch 2.5.4
GNU sed version 4.1.5
tar (GNU tar) 1.15.1

Actual list of packages used for toolchain:

Kernel-Headers-2.6.19; # Added some definitions removed
Binutils-cvs-2.17.50-20061129;
Glibc-cvs-2.5.90-20061109; # Applied Glibc-2.5-strlcpy_strlcat-1.patch
Gcc-cvs-4.3.0-20061201; # Applied hash-style patch
Gmp-4.2.1; # Needed for gcc compilation
Mpfr-2.2.1; # Needed for gcc compilation

Note1: Since the Reiser4 partition I first installed glibc-headers so no
complaining about nss.h missing file.
Note2: Gcc built in the hash-style needs a glibc supporting DT_GNU_HASH.
General-Notes: Gcc needs binutils supporting: -pie, omits dot symbols
and overlaps .opd (ppc64), -msecure-plt (ppc), .weakref,
--hash-style=gnu; mffgpr/mftgpr.
Pthread should not contain __thread tokens.
Glibc must support stack protector.
Glibc must support TFmode long double (ppc, ppc64, s390, s390x, sparc,
sparcv9, alpha).
For IA64 required: libunwind >= 0.98.
Needed: .eh_frame ld optimizations, visibility,
--as-needed/--no-as-needed; binutils that owns c++filt.
gdb < 5.1 (gdb must understand DW_FORM_strp).
Elfutils >= 0.72.

For Gcc-testsuite autogen is required (I installed 5.8.7); in native
build "bootstrap" is default; for gcc compilation needed gmp/mpfr.

Build-Order I used for now:
Kernel-Headers; Binutils-Pass1; Glibc-Headers; Glibc-Pass1; Gmp; Mpfr;
 Gcc-Pass1.

gcc -v:
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc/configure --prefix=/tools
--with-local-prefix=/tools --disable-nls --enable-shared
--enable-languages=c --with-mpfr=/tools --with-gmp=/tools
--with-mpfr-include=/tools/include --with-mpfr-lib=/tools/lib
--with-gmp-include=/tools/include --with-gmp-lib=/tools/lib
Thread model: posix
gcc version 4.3.0 20061201 (experimental)

gcc -dumpspecs:
*asm:
%{v:-V} %{Qy:} %{!Qn:-Qy} %{n} %{T} %{Ym,*} %{Yd,*} %{Wa,*:%*}

*asm_debug:
%{gstabs*:--gstabs}%{!gstabs*:%{g*:--gdwarf2}}

*asm_final:


*asm_options:
%a %Y %{c:%W{o*}%{!o*:-o %w%b%O}}%{!c:-o %d%w%u%O}

*invoke_as:
%{!S:-o %|.s |
 as %(asm_options) %|.s %A }

*cpp:
%{posix:-D_POSIX_SOURCE} %{pthread:-D_REENTRANT}

*cpp_options:
%(cpp_unique_options) %1 %{m*} %{std*&ansi&trigraphs} %{W*&pedantic*}
%{w} %{f*} %{g*:%{!g0:%{!fno-working-directory:-fworking-directory}}}
%{O*} %{undef} %{save-temps:-fpch-preprocess}

*cpp_debug_options:
%{d*}

*cpp_unique_options:
%{C|CC:%{!E:%eGCC does not support -C or -CC without -E}} %{!Q:-quiet}
%{nostdinc*} %{C} %{CC} %{v} %{I*&F*} %{P} %I %{MD:-MD
%{!o:%b.d}%{o*:%.d%*}} %{MMD:-MMD %{!o:%b.d}%{o*:%.d%*}} %{M} %{MM}
%{MF*} %{MG} %{MP} %{MQ*} %{MT*} %{!E:%{!M:%{!MM:%{MD|MMD:%{o*:-MQ
%*} %{remap} %{g3:-dD} %{H} %C %{D*&U*&A*} %{i*} %Z %i
%{fmudflap:-D_MUDFLAP -include mf-runtime.h} %{fmudflapth:-D_MUDFLAP
-D_MUDFLAPTH -include mf-runtime.h} %{E|M|MM:%W{o*}}

*trad_capable_cpp:
cc1 -E %{traditional|ftraditional|traditional-cpp:-traditional-cpp}

*cc1:
%(cc1_cpu) %{profile:-p}

*cc1_options:
%{pg:%{fomit-frame-pointer:%e-pg and -fomit-frame-pointer are
incompatible}} %1 %{!Q:-quiet} -dumpbase %B %{d*} %{m*} %{a*}
%{c|S:%{o*:-auxbase-strip %*}%{!o*:-auxbase %b}}%{!c:%{!S:-auxbase %b}}
%{g*} %{O*} %{W*&pedantic*} %{w} %{std*&ansi&trigraphs} %{v:-version}
%{pg:-p} %{p} %{f*} %{undef} %{Qn:-fno-ident} %{--help:--help}
%{--target-help:--target-help} %{!fsyntax-only:%{S:%W{o*}%{!o*:-o
%b.s}}} %{fsyntax-only:-o %j} %{-param*}
%{fmudflap|fmudflapth:-fno-builtin -fno-merge-constants}
%{coverage:-fprofile-arcs -ftest-coverage}

*cc1plus:


*link_gcc_c_sequence:
%{static:--start-group} %G %L %{static:--end-group}%{!static:%G}

*link_ssp:
%{fstack-protector:}

*endfile:
%{ffast-math|funsafe-math-optimizations:crtfastmath.o%s}   
%{shared|pie:crtendS.o%s;:crtend.o%s} crtn.o%s

*link:
%{!static:--eh-frame-hdr} -m %(link_emulation) --hash-style=gnu
%{shared:-shared}   %{!shared: %{!ibcs:   %{!static:   
%{rdynamic:-export-dynamic}%{!dynamic-linker:-dynamic-linker
%(dynamic_linker)}}%{static:-static}}}

*lib:
%{pthread:-lpthread}%{shared:-lc}%{!shared:%{mieee-fp:-lieee}
%{profile:-lc_p}%{!profile:-lc}}

*mfwrap:
 %{static: %{fmudflap|fmudflapth:  --wrap=malloc --wrap=free
--wrap=calloc --wrap=realloc --wrap=mmap --wrap=munmap --wrap=alloca}
%{fmudflapth: --wrap=pthread_create}} %{fmudflap|fmudflapth: --wrap=main}

*mflib:
%{fmudflap|fmudflapth: -export-dynamic}

*link_gomp:


*libgcc:
%{static|static-libgcc:-lgcc
-lgcc_eh}%{!static:%{!static-