glibc-2.2.1 (?)

Jack Detrick vze24938 at verizon.net
Mon Jan 15 09:03:38 PST 2001


Looks like the necessary patches for Glibc-2.2 are also the necessary
patches for Glibc-2.2.1.  Specifically, you didn't patch GCC before
installing Ncurses...


Andy Goth wrote:
> 
> Has anyone else successfully built ncurses-5.2 with glibc-2.2.1?  I get:
> 
> cd ../obj_s;  c++ -I../c++ -I../include -I. -DHAVE_CONFIG_H  -DNDEBUG -I. -I../include -O9 -march=i686 -mcpu=i686 -fPIC -c ../c++/cursesf.cc
> In file included from /usr/include/g++/iostream.h:31,
>                  from /usr/include/g++/strstream.h:32,
>                  from ../c++/cursesw.h:17,
>                  from ../c++/cursesp.h:39,
>                  from ../c++/cursesf.h:39,
>                  from ../c++/cursesf.cc:34:
> /usr/include/g++/streambuf.h: In method `struct streampos streambuf::pubseekoff(long long int, ios::seek_dir, int = 3)':
> /usr/include/g++/streambuf.h:362: conversion from `__off64_t' to non-scalar type `streampos' requested
> /usr/include/g++/streambuf.h: In method `struct streampos streambuf::pubseekpos(_G_fpos64_t, int = 3)':
> /usr/include/g++/streambuf.h:364: `struct streampos' used where a `long long int' was expected
> make[1]: *** [../obj_s/cursesf.o] Error 1
> make[1]: Leaving directory `/usr/src/build/ncurses-5.2/c++'
> make: *** [all] Error 2
> 
> This doesn't look like a ncurses-specific problem (ncurses was the first C++-using package I encountered).  Rather it might be a bug in glibc-2.2.1, or whatever package holds the iostreams stuff.
> 
> Lemme check out the source.
> 
> Argh!  Too complicated for 3:30 a.m.!!
> --
> Andy Goth  |  unununium at openverse.org  |  uin: 35256413  |  aim: Un111
> 
> --
> Unsubscribe: send email to lfs-apps-request at linuxfromscratch.org
> and put unsubscribe in the subject header of the message

-- 
With no walls or fences on the internet, who needs Windows or Gates?

-- 
Unsubscribe: send email to lfs-apps-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message




More information about the blfs-support mailing list