Unidentified subject!

1999-01-16 Thread Huntley Eshenroder
unsubscribe

Re: glib 1.1.12, gtk1.1.12 for debian/ppc

1999-01-16 Thread Sven LUTHER
On Sat, Jan 16, 1999 at 10:26:00PM +0200, Konstantinos Margaritis wrote: > On Sat, 16 Jan 1999, Sven LUTHER wrote: > > > I don't understand you, ... first you complain that the gtk package is too > > old, > > then you say it is because of a known egcs buug, and there is no solution > > apart >

Re: glib 1.1.12, gtk1.1.12 for debian/ppc

1999-01-16 Thread Konstantinos Margaritis
On Sat, 16 Jan 1999, Sven LUTHER wrote: > I don't understand you, ... first you complain that the gtk package is too > old, > then you say it is because of a known egcs buug, and there is no solution > apart > from no compiling the test program that cause problem, and then you said it is > not

Re: glib 1.1.12, gtk1.1.12 for debian/ppc

1999-01-16 Thread Sven LUTHER
On Fri, Jan 15, 1999 at 05:17:52PM +0200, Konstantinos Margaritis wrote: > On Fri, 15 Jan 1999, luther sven wrote: > > > i think in this case the correct thing to do is to fill a bug against this > > package, did you do it ? > > you state there that the package don't compile, because of so and s

Re: glib 1.1.12, gtk1.1.12 for debian/ppc

1999-01-16 Thread Konstantinos Margaritis
On Fri, 15 Jan 1999, Daniel Jacobowitz wrote: > OK, it's not schedule-insns2 then. Try a few others if you can find > them in the docs. yep, you were right. it's -O -fschedule-insns that causes the bug to appear. > 62 lines is great. But, can you grab the bare minimum of the necessary > defi

Re: glib 1.1.12, gtk1.1.12 for debian/ppc

1999-01-16 Thread Daniel Jacobowitz
On Sat, Jan 16, 1999 at 01:17:39AM +0200, Konstantinos Margaritis wrote: > well, maybe you are right, but I found out that it is part of the problem. > Removing it removed the bug. And as you can see I have chopped off 99% of > the code. I could not remove anything more, because whatever I did fixe