On 8/12/05, Chris Staub <[EMAIL PROTECTED]> wrote:
> The installation instructions for Texinfo give an "optional" step for a
> "TeX" installation, but it doesn't say why you would need it or what
> programs might require it. Some kind of additional description should be
> there (even if it's nothin
Chris Staub wrote these words on 08/12/05 23:20 CST:
> The installation instructions for Texinfo give an "optional" step for a
> "TeX" installation, but it doesn't say why you would need it or what
> programs might require it. Some kind of additional description should be
> there (even if it's n
On 8/13/05, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> Chris Staub wrote these words on 08/12/05 23:20 CST:
> > The installation instructions for Texinfo give an "optional" step for a
> > "TeX" installation, but it doesn't say why you would need it or what
> > programs might require it. Some kind
Randy McMurchy wrote:
Andrew Benton wrote these words on 08/13/05 10:23 CST:
It seems that /usr/include/glob.h does not contain the string rk_glob
andy:~$ grep rk_glob /mnt/lfs/usr/include/glob.h
andy:~$
Wait a minute. I'm afraid I don't understand why you are grepping
in /mnt/lfs. I was und
Doug,
Think I found the issue, check your gcc-static build and see if you
passed --enable-languages=c,c++ it should only be c.
--
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
LFS User # 2577
Registered Linux User # 299986
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://w
Andrew Benton wrote these words on 08/13/05 12:17 CST:
> It's not finished, I'm still only halfway through Gnome so I keep rebooting
> the google for patches. It was easier to run the grep from the host
> (gcc-3.4.4) system.
That makes sense. Andrew, thanks for your help earlier. I figured out
On 8/12/05, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
> IMO, we shole stay with the "release that has demonstrated itself as
> being reliable in real world environments."
>
> 2.2.6.
>
Minor typo, that's 2.2.26.
Another question, what is the version name that is used. For stable
releases, instead o
Tushar Teredesai wrote these words on 08/13/05 15:04 CST:
> Another question, what is the version name that is used. For stable
> releases, instead of using naming it 2.2.26, they use stable-20050429.
> IMO we should use their terminology. Two reasons:
> (1) We are not at odds with the versioning
On 8/13/05, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>
> Not sure if you saw my previous post about the --enable-dynamic
> parameter. Any thoughts?
>
I use --enable-dynamic in my builds too. I think it is only used for
the slapd backends. i.e. whether to link them in dynamic or static. I
am run
Tushar Teredesai wrote these words on 08/13/05 15:28 CST:
> I use --enable-dynamic in my builds too. I think it is only used for
> the slapd backends. i.e. whether to link them in dynamic or static. I
> am running a build without the dynamic. Lets see what the difference
> is.
My understanding (f
On 8/13/05, Jim Gifford <[EMAIL PROTECTED]> wrote:
> Doug,
> Think I found the issue, check your gcc-static build and see if you
> passed --enable-languages=c,c++ it should only be c.
Not unless it was in the book (I was cutting and pasting). However,
this latest time through I didn't run in
Chris Staub wrote:
The installation instructions for Texinfo give an "optional" step for a
"TeX" installation, but it doesn't say why you would need it or what
programs might require it. Some kind of additional description should be
there (even if it's nothing more than "if you don't know what
On 8/11/05, DJ Lucas <[EMAIL PROTECTED]> wrote:
> Matthew Burgess wrote:
> > Archaic wrote:
> >
> >> That just seems silly. Warn was much nicer and still allowed things to
> >> proceed.
> >
> >
> > Can we not still warn, but just leave the exit status as '0'. The spec
> > (from the quote given) do
Actually I found two causes for that error during my testing.
1 - --enable-languages=c,c++ will cause that error, don't understand why
though
2 - When LFS_HOST and LFS_TARGET32 are the same. (Verified thanx to Matt
Darcy)
I will be adding a third option to the variables page to correct the
se
Hello,
Bugs when a packahe uses some HAVE_XXX macro in its source and the
./configura script doesn't sefine that in config.h are pretty common
nowadays:
http://archives.linuxfromscratch.org/mail-archives/blfs-dev/2005-June/010153.html
http://www.diy-linux.org/pipermail/diy-linux-dev/2005-July
On 8/13/05, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>
> I'll be interested in what you find out doing the build you are doing
> right now.
>
The option --enable-dynamic passes the option -static to libtool when
linking. This makes the executables installed by openldap link
statically against
Alexander E. Patrakov wrote:
When adding a "version update" comment to Bugzilla, please also add
the output of the following checker script:
That seems reasonable to me. The script could be added to the faq in
the section "There's a new version of package Foo." as well, so that
others outsi
17 matches
Mail list logo
