Re: failure to compile libgnomeui on 2.18.0

[guenther <guenther rudersport de>]

According to the subject: If you get a build failure, we need the entire
error message to be able to help. Also, please include the exact command
you ran, and which dir you started it in.


>     about six weeks ago I tried garnome 2.17.92 this fired up on command 
> for me , after some shenanigans which ended up with a total rebuild . I 
> cannot now create a gnomesession without art _alloc type faults in it . 
> How do the under pinnings of the 2.17.92 differ at this point from the 
> 2.18.0 which fails to build a  'session

Since 2.17.92 was the last unstable release and the GNOME Release
Candidate, the differences should be negligible. With the notable
exception of Critical Warnings being crashers during the unstable cycle.
However, that usually results in issues with unstable releases, not with
the stable branch, so it doesn't apply here.

Other than that -- I am sorry, I do not understand your question.

Well, if libgnomeui really fails building, this would explain it. Since
gnome-session depends on it, it would not have been built as well. Did
you build GARNOME running 'make install' or paranoid-install? What dir
did you run that in?


> . changing the version upon the libbonoboui back to 2.17.94 does not 
> work and nether this or its successor appear faulty , in the build log .

What did you change exactly? Also, what do you mean by not "appear
faulty in the build log"? Does it build, or doesn't it?

Yours confused...

  guenther


-- 
char *t="\10pse\0r\0dtu\0  ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}