Re: [Cegcc-devel] Breakage with libsupc++ & write()

Kevin O'Connor escreveu: > On Thu, Nov 16, 2006 at 02:17:53PM +, Pedro Alves wrote: > >> Pedro Alves wrote: >> >>> Paul Sokolovsky wrote: >>> >>> But still, liboldname-ce would rather not export non-existent functions. >>> Oh, you are right, t

Re: [Cegcc-devel] Breakage with libsupc++ & write()

On Thu, Nov 16, 2006 at 02:17:53PM +, Pedro Alves wrote: > Pedro Alves wrote: > >Paul Sokolovsky wrote: > > > >> But still, liboldname-ce would rather not export non-existent > >>functions. > >> > >> > >Oh, you are right, that was indeed a big thinko on my part. > >There is indeed a thin wri

Re: [Cegcc-devel] Breakage with libsupc++ & write()

Paul Sokolovsky wrote: > Hello cegcc-devel, > > I'm building HaRET with cegcc/mingw32ce trunk: > > $ svn info > Path: . > URL: https://svn.sourceforge.net/svnroot/cegcc/trunk/cegcc > Repository Root: https://svn.sourceforge.net/svnroot/cegcc > Repository UUID: d7810a3d-100a-0410-8641-c3624a9c1

Re: [Cegcc-devel] Breakage with libsupc++ & write()

Pedro Alves wrote: Paul Sokolovsky wrote: But still, liboldname-ce would rather not export non-existent functions. Oh, you are right, that was indeed a big thinko on my part. There is indeed a thin write implementation in libmingwex.a, but you are right in that liboldname should not ex

[Cegcc-devel] Breakage with libsupc++ & write()

Hello cegcc-devel, I'm building HaRET with cegcc/mingw32ce trunk: $ svn info Path: . URL: https://svn.sourceforge.net/svnroot/cegcc/trunk/cegcc Repository Root: https://svn.sourceforge.net/svnroot/cegcc Repository UUID: d7810a3d-100a-0410-8641-c3624a9c11f1 Revision: 807 Node Kind: directory S