On Wed, Jan 24, 2001 at 02:56:40PM +0100, Jean-Marc Lasgouttes wrote:
> >> Unfortunately STD_STRING_IS_GOOD can not tell us whether this is
> >> needed, since it is a run-time problem, not a compile-time one.
>
> Dekel> I know, but at least the workaround code will not be used when
> Dekel> usin
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
>> Unfortunately STD_STRING_IS_GOOD can not tell us whether this is
>> needed, since it is a run-time problem, not a compile-time one.
Dekel> I know, but at least the workaround code will not be used when
Dekel> using a good compiler.
Dek
Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Mon, Jan 22, 2001 at 03:19:30PM +0100, Jean-Marc Lasgouttes wrote:
| > > "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
| >
| > Dekel> Yes (in fact, I only tested it with egcs 1.0.x which is the
| > Dekel> compiler I use).
| >
| > Dekel> I can
On Mon, Jan 22, 2001 at 03:19:30PM +0100, Jean-Marc Lasgouttes wrote:
> > "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> Dekel> Yes (in fact, I only tested it with egcs 1.0.x which is the
> Dekel> compiler I use).
>
> Dekel> I can put the workaround code inside a #if
> Dekel> !defined
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> Yes (in fact, I only tested it with egcs 1.0.x which is the
Dekel> compiler I use).
Dekel> I can put the workaround code inside a #if
Dekel> !defined(USE_INCLUDED_STRING) && !defined(STD_STRING_IS_GOOD)
Dekel> .. #endif
Unfortunatel
On Mon, Jan 22, 2001 at 03:06:08PM +0100, Jean-Marc Lasgouttes wrote:
> Dekel> Jeremy's problem was that the std::string of his compiler (gcc
> Dekel> 2.8.1) is bad, and compiling --with-included-string fixed his
> Dekel> problem.
> >> Do you know what was bad about it?
>
> Dekel> string::find_l
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii
Dekel> On Fri, Jan 19, 2001 at 05:20:37PM +0100, Jean-Marc Lasgouttes
Dekel> wrote:
>> > "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
>>
Dekel> Jeremy's problem
On Fri, Jan 19, 2001 at 05:20:37PM +0100, Jean-Marc Lasgouttes wrote:
> > "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> Dekel> Jeremy's problem was that the std::string of his compiler (gcc
> Dekel> 2.8.1) is bad, and compiling --with-included-string fixed his
> Dekel> problem.
>
> D
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> Jeremy's problem was that the std::string of his compiler (gcc
Dekel> 2.8.1) is bad, and compiling --with-included-string fixed his
Dekel> problem.
Do you know what was bad about it?
JMarc
On Fri, Jan 19, 2001 at 04:13:51PM +0100, Jean-Marc Lasgouttes wrote:
> > "Jeremy" == Jeremy Fox <[EMAIL PROTECTED]> writes:
> Jeremy> 1. No matter what, I get lots of errors like the following in
> Jeremy> my xterm.
>
> Jeremy> LyX: Bad integer `0' [around line 14 of file
> Jeremy> /usr/loca
> "Jeremy" == Jeremy Fox <[EMAIL PROTECTED]> writes:
Jeremy> Hi. I am a lowly user, but I've had a lot of trouble with
Jeremy> 1.1.6:
Jeremy, and all other people who experienced locale related problems
(like the 2,17 problem), could you try the following patch and tell me
whether it helps?
> "Jeremy" == Jeremy Fox <[EMAIL PROTECTED]> writes:
Jeremy> Hi. I am a lowly user, but I've had a lot of trouble with
Jeremy> 1.1.6:
Jeremy> 1. No matter what, I get lots of errors like the following in
Jeremy> my xterm.
Jeremy> LyX: Bad integer `0' [around line 14 of file
Jeremy> /usr/loc
On Sun, Jan 14, 2001 at 06:42:09PM -0800, Jeremy Fox wrote:
> Hi.
>
> I am a lowly user, but I've had a lot of trouble with 1.1.6:
>
> I have experienced other problems I can't remember and am going to
> reinstall 1.1.5fix2. I am using Solaris 2.6. Previous versions of LyX
> have always work
13 matches
Mail list logo
