Re: [lfs-dev] automake -1.15 test failures fixes
>> Personally, I don't find adding that handful of lines to my build >> scripts at all cumbersome. But, yes, if one is typing it all on the >> console line... Well, that's why I haven't done that since LFS-4.1! > >I take it you don't use jhalfs. How do you build your scripts? > >Alan I don't. I provided a sample template along with the hint I contributed for pio, to show how I use my package manager. You can find it there. -- Paul Rogers paulgrog...@fastmail.fm Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://www.fastmail.com - Does exactly what it says on the tin -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] automake -1.15 test failures fixes
On 5/7/2017 1:28 AM, Paul Rogers wrote: For automake, the process of removing the bad tests is cumbersome, but we do say: Four tests are known to fail. Personally, I don't find adding that handful of lines to my build scripts at all cumbersome. But, yes, if one is typing it all on the console line... Well, that's why I haven't done that since LFS-4.1! I take it you don't use jhalfs. How do you build your scripts? Alan -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] [Clfs-support] clfs-mbdd: 'the-end/whatnow': defunct 'freshmeat' link.
> Date: Sun, 07 May 2017 22:09:26 +0100 > From: lf...@cruziero.com (akhiezer) > [...] > Cc'd to lfs-dev re 'freecode', further below. s/free/fresh/ > [...] > http://freecode.com/users/esr ( - ~ignore that link). > [...] > akh -- -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
[lfs-dev] clfs-mbdd: 'the-end/whatnow': defunct 'freshmeat' link.
(
To: clfs-supp...@lists.clfs.org
Cc: lfs-dev@lists.linuxfromscratch.org
)
Cc'd to lfs-dev re 'freecode', further below.
Page 'the-end/whatnow' contains defunct 'freshmeat' link:
https://github.com/bradfa/clfs-embedded/blob/2017.04-fixes/BOOK/the-end/whatnow.xml
(bradfa/clfs-embedded.wcp.cz/render.2017.04-fixes.1/html)/x86/the-end/whatnow.html
http://clfs.org/view/clfs-embedded/x86/the-end/whatnow.html #
GIT-20161228-x86
==
"Freshmeat.net (http://freshmeat.net/)"
lnk('http://freshmeat.net/') == http://freshmeat.net/
===
And o/c:
freshmeat -> freecode ->
'Effective 2014-06-18 Freecode is no longer being updated (content
may be stale).'
So the clfs page likely shouldn't carry the link any more; clfs-sysv/d &
lfs no longer carry the link.
Is there a replacement for freshmeat/ ? Some websearching
using some 'likely strings/leads', threw up inter alia,
'freshcode.club'/'freshfoss.com' - apparently instigated via esr:
http://freshcode.club/
==
http://freshcode.club/feed
===
http://esr.ibiblio.org/?p=5948
http://freecode.com/users/esr
http://freshcode.club/links
Haven't used it for any length of time and so cannot vouch for it. But
may be worth keeping an eye on.
akh
--
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: [lfs-dev] automake -1.15 test failures fixes
> It would be useful to know which pages you consider a problem. I've > recently fixed glibc, vim, and am in the process of fixing the one in > flex via an updated patch. I also accepted a failure in my tar-1.28 fallback, sparse3 IIRC. AIUI it tries to allocate a huge file, but I'm building in a 15GB partition, for the moment. Ch6-8 are done and dusted, boots and runs. > For automake, the process of removing the bad tests is cumbersome, but > we do say: Four tests are known to fail. Personally, I don't find adding that handful of lines to my build scripts at all cumbersome. But, yes, if one is typing it all on the console line... Well, that's why I haven't done that since LFS-4.1! > Would it be sufficient to just name the failing tests? Indeed, that would be most helpful. The check12 fail was what Ken told me that gave me confidence to go on, not throwing it all away! I can't emphasize enough how important it is to have condifence in the reliability of the system we're building. Not knowing which failures have been accepted by the book developers, leaves doubt. I hope you do. -- Paul Rogers paulgrog...@fastmail.fm Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://www.fastmail.com - A no graphics, no pop-ups email service -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
