Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Mon, Mar 18, 2002 at 12:14:38PM +0100, Yann MORERE wrote:
>> Should i update my gcc?
>
| Probably the best thing to do.
>
| I don't think supporting anything older than 2.95 is worthwhile.
And now even Linux Kernel require at least 2.95.3.
In a yea
Yann MORERE <[EMAIL PROTECTED]> writes:
| Hello,
>
| another problem compiling lyx cvs on a suse6.3 box with egcs-2.91.66
>
| lyxdevel@Qui-GonJinn:~/cvs/lyx-devel > gcc -v
| Reading specs from /usr/lib/gcc-lib/i486-linux/egcs-2.91.66/specs
| gcc version egcs-2.91.66 19990314/Li
On Mon, Mar 18, 2002 at 12:14:38PM +0100, Yann MORERE wrote:
> Should i update my gcc?
Probably the best thing to do.
I don't think supporting anything older than 2.95 is worthwhile.
Andre'
--
André Pönitz .. [EMAIL PROTECTED]
Hello,
another problem compiling lyx cvs on a suse6.3 box with egcs-2.91.66
lyxdevel@Qui-GonJinn:~/cvs/lyx-devel > gcc -v
Reading specs from /usr/lib/gcc-lib/i486-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
lyxdevel@Qui-GonJinn:~/cvs/lyx-de
On Tue, Mar 12, 2002 at 12:16:48PM +0100, Lars Gullik Bjønnes wrote:
> Ok, so 2.95.3 has push_back... how bad is it of us to require gcc >=
> 2.95.3?
_My_ 2.95.2 has it, too. It seems to be unchanged from SuSE's
libgpp-2.95.2-149 build on Fri Jan 19 07:09:01 2001.
Andre'
--
André Pönitz ..
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Ok, so 2.95.3 has push_back... how bad is it of us to require
Lars> gcc >= 2.95.3?
It would be bad if it is just for convenience. What does push_back do?
Why don't you use
word += c;
as everybody in his right mind would do?
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> I wonder if 2.95.3 has push_back?
>
| I'm not shure if this is the right information. I have gcc 2.95.3 and this is a
| part from /usr/include/g++/std/bastring.h:
>
| void push_back(charT __c)
| { append(1, __c);
Lars Gullik Bjønnes wrote:
> I wonder if 2.95.3 has push_back?
I'm not shure if this is the right information. I have gcc 2.95.3 and this is a
part from /usr/include/g++/std/bastring.h:
void push_back(charT __c)
{ append(1, __c); }
basic_string& assign (const basic_string& str, size_type p
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 12-Mar-2002 Lars Gullik Bjønnes wrote:
>
>> The (unwanted) solution is to use:
>>
>> string::append(int, char);
>
| Why not just do ./configure --with-included-string
>
| and you use lyxstring which should have all function you need.
We want to
On 12-Mar-2002 Lars Gullik Bjønnes wrote:
> The (unwanted) solution is to use:
>
> string::append(int, char);
Why not just do ./configure --with-included-string
and you use lyxstring which should have all function you need.
Jug
--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-
Yann MORERE <[EMAIL PROTECTED]> writes:
| Ce Tue, 12 Mar 2002 09:49:03 +0100
| [EMAIL PROTECTED] (Lars Gullik Bjønnes) a écrit :
>
| LGB>
| LGB> I thought that compiler had the string class more or less correctly
| LGB> implemented.
| LGB>
| LGB> Can you find the bastring.h header on your syste
Yann MORERE <[EMAIL PROTECTED]> writes:
| Hello,
>
| On my linux box debian 2.2r3 sparc, i try to compile lyx cvs.
>
| I had no problem with last wee releases, but last friday, and yesterday
| i get this
>
| g++ -DHAVE_CONFIG_H -I. -I. -I. -I.. -I.. -I../boost -I./xforms
| -isystem /usr/X11R6/
Hello,
On my linux box debian 2.2r3 sparc, i try to compile lyx cvs.
I had no problem with last wee releases, but last friday, and yesterday
i get this
g++ -DHAVE_CONFIG_H -I. -I. -I. -I.. -I.. -I../boost -I./xforms
-isystem /usr/X11R6/include -O -fno-rtti -fno-exceptions -W -Wall -c
buffer
13 matches
Mail list logo
