Sugar jhbuild bug
I'm trying to set up sugar-jhbuild on my OpenSuse 10.2 computer. When I was satisfying all the dependencies reported by the build option I noticed one that seemed very odd. It wanted automake 1.7. Open Suse installs automake 1.9, and I would have thought anything 1.7 or greater would work. I satisfied all the other dependencies first, hoping this would go away, but it stayed to the end and build would not budge until I fixed it. I downloaded automake 1.7.9 source and installed it in /usr/local/bin, and that seemed to be enough to get sugar-jhbuild working again. Then I got this message: configure.ac:8: require Automake 1.9, but have 1.7.9 autoreconf: automake failed with exit status: 1 That's a Catch-22 if I ever saw one. I let the build keep running, skipping over the modules that won't compile. It's pretty obvious that I won't have anything workable afterwards, though. I would guess there are a lot of sugar-jhbuild users on this list, and I'd appreciate any suggestions. I can easily uninstall automake 1.7.9, the question is what to do after that. Thanks, James Simmons ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Sugar jhbuild bug
On Wed, Mar 12, 2008 at 2:56 PM, James Simmons [EMAIL PROTECTED] wrote: I'm trying to set up sugar-jhbuild on my OpenSuse 10.2 computer. When I was satisfying all the dependencies reported by the build option I noticed one that seemed very odd. It wanted automake 1.7. Open Suse installs automake 1.9, and I would have thought anything 1.7 or greater would work. I satisfied all the other dependencies first, hoping this would go away, but it stayed to the end and build would not budge until I fixed it. I downloaded automake 1.7.9 source and installed it in /usr/local/bin, and that seemed to be enough to get sugar-jhbuild working again. Then I got this message: configure.ac:8: require Automake 1.9, but have 1.7.9 autoreconf: automake failed with exit status: 1 That's a Catch-22 if I ever saw one. I let the build keep running, skipping over the modules that won't compile. It's pretty obvious that I won't have anything workable afterwards, though. I would guess there are a lot of sugar-jhbuild users on this list, and I'd appreciate any suggestions. I can easily uninstall automake 1.7.9, the question is what to do after that. Hi, just in case it helps somehow in OpenSuse, here in ubuntu gutsy I installed automake 1.7.9 and 1.9 from the standard repos and things work fine. Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Sugar jhbuild bug
Hello all, Same problem in debian, fixed as tomeu stated. On Wed, Mar 12, 2008 at 10:22 AM, Tomeu Vizoso [EMAIL PROTECTED] wrote: On Wed, Mar 12, 2008 at 2:56 PM, James Simmons [EMAIL PROTECTED] wrote: I'm trying to set up sugar-jhbuild on my OpenSuse 10.2 computer. When I was satisfying all the dependencies reported by the build option I noticed one that seemed very odd. It wanted automake 1.7. Open Suse installs automake 1.9, and I would have thought anything 1.7 or greater would work. I satisfied all the other dependencies first, hoping this would go away, but it stayed to the end and build would not budge until I fixed it. I downloaded automake 1.7.9 source and installed it in /usr/local/bin, and that seemed to be enough to get sugar-jhbuild working again. Then I got this message: configure.ac:8: require Automake 1.9, but have 1.7.9 autoreconf: automake failed with exit status: 1 That's a Catch-22 if I ever saw one. I let the build keep running, skipping over the modules that won't compile. It's pretty obvious that I won't have anything workable afterwards, though. I would guess there are a lot of sugar-jhbuild users on this list, and I'd appreciate any suggestions. I can easily uninstall automake 1.7.9, the question is what to do after that. Hi, just in case it helps somehow in OpenSuse, here in ubuntu gutsy I installed automake 1.7.9 and 1.9 from the standard repos and things work fine. Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Rafael Enrique Ortiz Guerrero One Laptop Per Child [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Sugar jhbuild bug
Tomeu, The Suse repositories don't have RPMs for automake other than 1.9. However, you have given me an idea to try. I noticed that automake's executeable has a version number in it, and it is symlinked to automake. Maybe if I unlink automake in /usr/local/bin but leave everything else alone I can get the build to work. If it works I'll update the wiki page for Suse. I wasn't expecting to need two different versions of automake installed to do the build though. I've compiled a lot of source for Linux but I never ran into anything like this. I have another machine running xubuntu, which I believe is based on gutsy and has RPMs for Sugar. That has worked very well for me, but sharing with the Read activity is broken and since my app is a variant of Read and needs to do sharing I need a better test environment. I was hoping to get my openSuse box to be that environment, the build sugar-jhbuild on xubuntu after removing the sugar RPMs. James Simmons Tomeu Vizoso wrote: On Wed, Mar 12, 2008 at 2:56 PM, James Simmons [EMAIL PROTECTED] wrote: I'm trying to set up sugar-jhbuild on my OpenSuse 10.2 computer. When I was satisfying all the dependencies reported by the build option I noticed one that seemed very odd. It wanted automake 1.7. Open Suse installs automake 1.9, and I would have thought anything 1.7 or greater would work. I satisfied all the other dependencies first, hoping this would go away, but it stayed to the end and build would not budge until I fixed it. I downloaded automake 1.7.9 source and installed it in /usr/local/bin, and that seemed to be enough to get sugar-jhbuild working again. Then I got this message: configure.ac:8: require Automake 1.9, but have 1.7.9 autoreconf: automake failed with exit status: 1 That's a Catch-22 if I ever saw one. I let the build keep running, skipping over the modules that won't compile. It's pretty obvious that I won't have anything workable afterwards, though. I would guess there are a lot of sugar-jhbuild users on this list, and I'd appreciate any suggestions. I can easily uninstall automake 1.7.9, the question is what to do after that. Hi, just in case it helps somehow in OpenSuse, here in ubuntu gutsy I installed automake 1.7.9 and 1.9 from the standard repos and things work fine. Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Sugar jhbuild bug
On Wed, Mar 12, 2008 at 5:17 PM, James Simmons [EMAIL PROTECTED] wrote: Tomeu, The Suse repositories don't have RPMs for automake other than 1.9. However, you have given me an idea to try. I noticed that automake's executeable has a version number in it, and it is symlinked to automake. Maybe if I unlink automake in /usr/local/bin but leave everything else alone I can get the build to work. If it works I'll update the wiki page for Suse. I wasn't expecting to need two different versions of automake installed to do the build though. I've compiled a lot of source for Linux but I never ran into anything like this. In the hope it helps: [EMAIL PROTECTED]:~/sugar-jhbuild/source/sugar-tomeu$ ls -l /usr/bin/automake* lrwxrwxrwx 1 root root 26 2007-05-17 21:18 /usr/bin/automake - /etc/alternatives/automake -rwxr-xr-x 1 root root 270996 2006-06-26 13:01 /usr/bin/automake-1.7 -rwxr-xr-x 1 root root 221996 2006-12-06 16:55 /usr/bin/automake-1.9 [EMAIL PROTECTED]:~/sugar-jhbuild/source/sugar-tomeu$ ls -l /etc/alternatives/automake lrwxrwxrwx 1 root root 21 2007-05-17 21:18 /etc/alternatives/automake - /usr/bin/automake-1.9 I have another machine running xubuntu, which I believe is based on gutsy and has RPMs for Sugar. That has worked very well for me, but sharing with the Read activity is broken and since my app is a variant of Read and needs to do sharing I need a better test environment. I was hoping to get my openSuse box to be that environment, the build sugar-jhbuild on xubuntu after removing the sugar RPMs. You may want to run several instances of the sugar emulator in the same machine: http://wiki.laptop.org/go/Sugar_with_sugar-jhbuild#Running_multiple_instances Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
