On Sun, 8 Jan 2006, Greg Schafer wrote:
Hmmm, AFAICS there is no easy way to fool configure into doing what we
need. This is the best I can come up with for now. After running
configure, do this:
echo '#define YYENABLE_NLS 1' >> config.h
I can confirm it fixes the ICA problem.
Indeed it does
"Alexander E. Patrakov" <[EMAIL PROTECTED]> writes:
> 3) links doesn't support UTF-8. So if you are using the en_US locale,
> everything is fine. But in en_US.UTF-8, you will have to change your
> preference.
and... links add extra space left to the text. so I can not cut and paste
from lfs book
Greg Schafer wrote:
> /* Define to 1 to internationalize bison runtime messages. */
> -/* #undef YYENABLE_NLS */
> +#define YYENABLE_NLS 1
>
> Bingo! This looks like the culprit.
> I'll try and figure out a good fix tomorrow..
Hmmm, AFAICS there is no easy way to fool configure into doing wh
On Sat, 7 Jan 2006, Greg Schafer wrote:
I've just managed to reproduce this in a DIY build by dropping M4, Bison
and Flex from the temptools phase. Hmm, this is a bizarre one... check
out the following..
By retaining the finished Bison build dirs from each iteration and diffing
them, I was
On Fri, 6 Jan 2006, Chris Staub wrote:
Or replace "creating" with "customizing".
Thanks, done.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information
On 1/7/06, Greg Schafer <[EMAIL PROTECTED]> wrote:
Wow, that's some serious analysis, dude. It also proves that my
earlier "flex must be before bison" is bogus. Seems that adding bison
back into Ch. 5 would do the trick, but maybe there's a better
solution. This has inspired me to work on the
Ken Moffat wrote:
> On Fri, 6 Jan 2006, Ken Moffat wrote:
>
>> On Thu, 5 Jan 2006, Dan Nicholson wrote:
>>
bison as Dan noted
>>>
>>> I think I've got this one figured out in the alphabetical builds.
>>> Circular dependencies between bison and flex. Requires adding bison
>>> to /tools, b
On 1/6/06, Ken Moffat <[EMAIL PROTECTED]> wrote:
> Dan, by adding bison to /tools [ in what is otherwise svn-20060103 with
> a bash-documentation cleanup per bug 1679 ] I get a clean build of bison
> in chapter 6. That is, it no longer differs when rebuilt in place.
>
> This means bison depend
Ken Moffat wrote:
/me raises his hat to Bryan, to salute him for reading the Perl
documentation.
Perhaps we shold move the creation of /etc/hosts to before we configure
perl, AND change the title of '7.11 Creating the /etc/hosts File' to
'7.11 The /etc/hosts File' ?
Ken
Or replace "creat
On Fri, 6 Jan 2006, Ken Moffat wrote:
On Thu, 5 Jan 2006, Dan Nicholson wrote:
bison as Dan noted
I think I've got this one figured out in the alphabetical builds.
Circular dependencies between bison and flex. Requires adding bison
to /tools, but the differences are gone now.
Dan, by
On Fri, 6 Jan 2006, Bryan Kadzban wrote:
Or actually, the Perl documentation[1] says it's part of the system that
allows programs to find out how Perl was configured. The command in the
string is supposed to "produce the text of the /etc/hosts file", but I'm
not sure what purpose that would ne
> echo "127.0.0.1 localhost $(hostname)" > /etc/hosts
>
> This will definitely be overwritten in 7.11. It also takes care of
> the perl testsuite case where it is needed.
>
> What do people think about adding the above command to Ch. 6.7?
>
> --
> Dan
Sounds good to me. :) No harm from it, f
On 1/6/06, Bryan Kadzban <[EMAIL PROTECTED]> wrote:
> Well, the perl Configure script used to have some verbiage in it about
> the gethostname() function not returning the correct hostname in all
> cases (something about "but it can't be changed for political reasons").
> In that case, it offered a
On Fri, Jan 06, 2006 at 12:57:01PM +, Ken Moffat wrote:
> On Thu, 5 Jan 2006, Dan Nicholson wrote:
>
> >Maybe. Do you know how the hostcat command is used in perl?
>
> No idea, and I'm not keen to dig into perl. The binaries are accepted
> after stripping and converting hte dates to token
On Thu, 5 Jan 2006, Dan Nicholson wrote:
On 1/5/06, Ken Moffat <[EMAIL PROTECTED]> wrote:
Files that differ, but with same code:
e2fsck, fsck.ext2, fsck.ext3 (the same file, by three names)
I can't figure out this bugger. Maybe the objdump -S can help.
The 'same code' message is because
On 1/5/06, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote:
> 2) I can change that to: #define WEB_BROWSER "exec /usr/bin/web-browser"
> and ask readers to make a symlink according to their preference. Is this
> acceptable?
No, that's fine, I think. Maybe a note could be added in BLFS browser
pag
Dan Nicholson wrote:
On 1/5/06, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote:
The third change accounts for programs that Man-DB should be able to find at
runtime, but that haven't been installed yet:
cat >>include/manconfig.h.in <<"EOF"
#define WEB_BROWSER "exec /usr/bin/lynx"
#define COL
On 1/5/06, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote:
> > The third change accounts for programs that Man-DB should be able to find
> > at runtime, but that haven't been installed yet:
> >
> > cat >>include/manconfig.h.in <<"EOF"
> > #define WEB_BROWSER "exec /usr/bin/lynx"
> > #define COL "
Dan Nicholson wrote:
/usr/bin/col is from util-linux. Like you say, though, let's see what
happens with man-db.
Quoting from the UTF-8 book:
The third change accounts for programs that Man-DB should be able to find at
runtime, but that haven't been installed yet:
cat >>include/manconfig.h
On 1/5/06, Ken Moffat <[EMAIL PROTECTED]> wrote:
I did the same thing on svn-20051223 a couple weeks ago. The farce I
used was older, so it doesn't output the same info. (BTW, I like the
additions, Ken.) My results can be seen here:
http://students.washington.edu/dbnichol/lfs/lfs-20051223-repo
20 matches
Mail list logo
