23.0.60 bootstrap fails for maemo

23.0.60 bootstrap fails for maemo

[Thomas Baumann]

I'm trying to compile emacs23 for os2008 using the maemo-4.0 sdk but
somehow the bootstrap fails. I'm working with a fresh copy of the cvs
files checked out today. 

The problem looks very much like the emacs23/cygwin problem discussed
earlier, but I was not able to test all of the possible solutions
mentioned there.

Any help is highly appreciated.

BTW emacs 22.1 compiles fine and runs nicely but with very tiny fonts...

Here are the relevant parts my bootstrap

./configure --without-gif --without-xpm --enable-font-backend


gcc -Demacs -DHAVE_CONFIG_H -DUSE_GTK  -I. -I/tmp/emacs/src -D_BSD_SOURCE -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/freetype2 -I/usr/include/alsa  -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -g -O2  -Wl,-znocombreloc  /tmp/emacs/src/prefix-args.c -o prefix-args
echo "dispnew.o frame.o scroll.o xdisp.o xmenu.o window.o charset.o coding.o category.o ccl.o character.o chartab.o cm.o term.o terminal.o xfaces.o xterm.o xfns.o xselect.o xrdb.o fontset.o xsmfns.o fringe.o image.o gtkutil.o dbusbind.o emacs.o keyboard.o macros.o keymap.o sysdep.o buffer.o filelock.o insdel.o marker.o minibuf.o fileio.o dired.o filemode.o cmds.o casetab.o casefiddle.o indent.o search.o regex.o undo.o alloc.o data.o doc.o editfns.o callint.o eval.o floatfns.o fns.o print.o lread.o syntax.o unexelf.o bytecode.o process.o callproc.o region-cache.o sound.o atimer.o doprnt.o strftime.o intervals.o textprop.o composite.o md5.o    font.o xfont.o ftfont.o xftfont.o ftxfont.o terminfo.o lastfile.o   vm-limit.o   " > buildobj.lst
gcc -nostdlib `./prefix-args -Xlinker  -z nocombreloc` -Wl,-znocombreloc  -o temacs pre-crt0.o /usr/lib/crt1.o /usr/lib/crti.o dispnew.o frame.o scroll.o xdisp.o xmenu.o window.o charset.o coding.o category.o ccl.o character.o chartab.o cm.o term.o terminal.o xfaces.o xterm.o xfns.o xselect.o xrdb.o fontset.o xsmfns.o fringe.o image.o gtkutil.o dbusbind.o emacs.o keyboard.o macros.o keymap.o sysdep.o buffer.o filelock.o insdel.o marker.o minibuf.o fileio.o dired.o filemode.o cmds.o casetab.o casefiddle.o indent.o search.o regex.o undo.o alloc.o data.o doc.o editfns.o callint.o eval.o floatfns.o fns.o print.o lread.o syntax.o unexelf.o bytecode.o process.o callproc.o region-cache.o sound.o atimer.o doprnt.o strftime.o intervals.o textprop.o composite.o md5.o    font.o xfont.o ftfont.o xftfont.o ftxfont.o terminfo.o lastfile.o   vm-limit.o       -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lpthread -lSM -lICE -ltiff -ljpeg -lpng -lz -lm -lX11 -lXft -lfontconfig -lasound  -ldbus-1 -lncurses   -lm -lgcc -lc -lgcc /usr/lib/crtn.o 
RUNEMACS="`/bin/pwd`/temacs"; cd /tmp/emacs/src/../admin/unidata; make -w RUNEMACS="${RUNEMACS}" DSTDIR=/tmp/emacs/src/../lisp/international
make[3]: Entering directory `/tmp/emacs/admin/unidata'
/tmp/emacs/src/temacs -batch -f batch-byte-compile unidata-gen.el
Loading loadup.el (source)...
Using load-path (/tmp/emacs/lisp /tmp/emacs/lisp/emacs-lisp /tmp/emacs/lisp/language /tmp/emacs/lisp/international /tmp/emacs/lisp/textmodes)
Loading emacs-lisp/byte-run (source)...
Loading emacs-lisp/backquote (source)...
Loading subr (source)...
Loading version.el (source)...
Loading widget (source)...
Loading custom (source)...
Loading emacs-lisp/map-ynp (source)...
Loading cus-start (source)...
Loading international/mule (source)...
Loading international/mule-conf.el (source)...
qemu: uncaught target signal 11 (Segmentation fault) - exiting
make[3]: *** [unidata-gen.elc] Error 245
make[3]: Leaving directory `/tmp/emacs/admin/unidata'
make[2]: *** [/tmp/emacs/src/../lisp/international/charprop.el] Error 2
make[2]: Leaving directory `/tmp/emacs/src'
make[1]: *** [bootstrap-build] Error 2
make[1]: Leaving directory `/tmp/emacs'
make: *** [bootstrap] Error 2
[sbox-CHINOOK_ARMEL: /tmp/emacs] > native-gdb src/temacs
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "arm-linux-gnueabi"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run -batch -f batch-byte-compile unidata-gen.el
Starting program: /tmp/emacs/src/temacs -batch -f batch-byte-compile unidata-gen.el
qemu: Unsupported syscall: 26
Loading loadup.el (source)...
Using load-path (/tmp/emacs/lisp /tmp/emacs/lisp/emacs-lisp /tmp/emacs/lisp/language /tmp/emacs/lisp/international /tmp/emacs/lisp/textmodes)
Loading emacs-lisp/byte-run (source)...
Loading emacs-lisp/backquote (source)...
Loading subr (source)...
Loading version.el (source)...
Loading widget (source)...
Loading custom (source)...
Loading emacs-lisp/map-ynp (source)...
Loading cus-start (source)...
Loading international/mule (source)...
Loading international/mule-conf.el (source)...
qemu: uncaught target signal 11 (Segmentation fault) - exiting
qemu: Unsupported syscall: 26
Could not open /proc/1785/status
(gdb) bt
qemu: Unsupported syscall: 26
warning: Unable to fetch general register.
qemu: Unsupported syscall: 26
qemu: Unsupported syscall: 26
qemu: Unsupported syscall: 26
qemu: Unsupported syscall: 26
qemu: Unsupported syscall: 26
qemu: Unsupported syscall: 26
qemu: Unsupported syscall: 26
qemu: Unsupported syscall: 26
qemu: Unsupported syscall: 26
qemu: Unsupported syscall: 26

Re: 23.0.60 bootstrap fails for maemo

[Dan Nicolaescu]

Thomas Baumann <dtbaumann@yahoo.de> writes:


  > [sbox-CHINOOK_ARMEL: /tmp/emacs] > native-gdb src/temacs
  > GNU gdb 6.6-debian
  > Copyright (C) 2006 Free Software Foundation, Inc.
  > GDB is free software, covered by the GNU General Public License, and you are
  > welcome to change it and/or distribute copies of it under certain conditions.
  > Type "show copying" to see the conditions.
  > There is absolutely no warranty for GDB.  Type "show warranty" for details.
  > This GDB was configured as "arm-linux-gnueabi"...
  > Using host libthread_db library "/lib/libthread_db.so.1".
  > (gdb) run -batch -f batch-byte-compile unidata-gen.el
  > Starting program: /tmp/emacs/src/temacs -batch -f batch-byte-compile unidata-gen.el
  > qemu: Unsupported syscall: 26
  > Loading loadup.el (source)...
  > Using load-path (/tmp/emacs/lisp /tmp/emacs/lisp/emacs-lisp /tmp/emacs/lisp/language /tmp/emacs/lisp/international /tmp/emacs/lisp/textmodes)
  > Loading emacs-lisp/byte-run (source)...
  > Loading emacs-lisp/backquote (source)...
  > Loading subr (source)...
  > Loading version.el (source)...
  > Loading widget (source)...
  > Loading custom (source)...
  > Loading emacs-lisp/map-ynp (source)...
  > Loading cus-start (source)...
  > Loading international/mule (source)...
  > Loading international/mule-conf.el (source)...
  > qemu: uncaught target signal 11 (Segmentation fault) - exiting
  > qemu: Unsupported syscall: 26
  > Could not open /proc/1785/status
  > (gdb) bt
  > qemu: Unsupported syscall: 26

What syscall is 26 on that platform? From the warnings it sounds like it
might be ptrace.  If it is, then debugging will be challenging... 
Do you get the same problems if you try on the real hardware instead of
the simulator?

Re: 23.0.60 bootstrap fails for maemo

[Thomas Baumann]

Dan Nicolaescu <dann@ics.uci.edu> writes:

> Thomas Baumann <dtbaumann@yahoo.de> writes:
>
>
>   > qemu: Unsupported syscall: 26
>   > Could not open /proc/1785/status
>   > (gdb) bt
>   > qemu: Unsupported syscall: 26
>
> What syscall is 26 on that platform? From the warnings it sounds like it
> might be ptrace.  If it is, then debugging will be challenging... 
> Do you get the same problems if you try on the real hardware instead of
> the simulator?

I guess you're right with syscall 26 and I'm sorry, there are no
development packages installed on the device itself (yet). I just tried
to connect with ddd but without success. strace is all I can offer:

[sbox-CHINOOK_ARMEL: /tmp/emacs] > strace src/temacs -batch -f batch-byte-compile unidata-gen.el
execve("src/temacs", ["src/temacs", "-batch", "-f", "batch-byte-compile", "unidata-gen.el"], [/* 45 vars */]) = 0
uname({sys="Linux", node="norvel", ...}) = 0
brk(0)                                  = 0x80b2000
brk(0x80d3000)                          = 0x80d3000
open("/targets/links/scratchbox.config", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0664, st_size=1141, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40000000
read(3, "# Automatically generated config"..., 4096) = 1141
read(3, "", 4096)                       = 0
close(3)                                = 0
munmap(0x40000000, 4096)                = 0
open("/tmp/cputransp_tb.log", O_WRONLY|O_APPEND|O_CREAT, 0666) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=527861, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40001000
fstat64(3, {st_mode=S_IFREG|0644, st_size=527861, ...}) = 0
_llseek(3, 527861, [527861], SEEK_SET)  = 0
stat64(".", {st_mode=S_IFDIR|0755, st_size=1192, ...}) = 0
stat64("/tmp/emacs", {st_mode=S_IFDIR|0755, st_size=1192, ...}) = 0
gettimeofday({1202673636, 341111}, NULL) = 0
open("/scratchbox/etc/localtime", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=2295, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40002000
read(4, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\10\0\0\0\10\0"..., 4096) = 2295
close(4)                                = 0
munmap(0x40002000, 4096)                = 0
getpid()                                = 23296
open("/scratchbox/etc/scratchbox-version", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=38, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40000000
read(4, "1.0.8\nWed,  1 Aug 2007 15:05:22 "..., 4096) = 38
close(4)                                = 0
munmap(0x40000000, 4096)                = 0
open("src/temacs", O_RDONLY)            = 4
fstat64(4, {st_mode=S_IFREG|0775, st_size=21222617, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40002000
read(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\2\0(\0\1\0\0\0\310C\1\000"..., 4096) = 4096
close(4)                                = 0
munmap(0x40002000, 4096)                = 0
write(3, "[2008-02-10 20:00:36 23296] meth"..., 184) = 184
rt_sigaction(SIGCHLD, {0x8048bb0, [], SA_RESTORER, 0x80499b8}, NULL, 8) = 0
rt_sigaction(SIGTERM, {0x8048bc0, [], SA_RESTORER, 0x80499b8}, NULL, 8) = 0
rt_sigaction(SIGHUP, {0x8048bc0, [], SA_RESTORER, 0x80499b8}, NULL, 8) = 0
rt_sigaction(SIGINT, {0x8048bc0, [], SA_RESTORER, 0x80499b8}, NULL, 8) = 0
fork()                                  = 23297
waitpid(23297, Loading loadup.el (source)...
Using load-path (/tmp/emacs/lisp /tmp/emacs/lisp/emacs-lisp /tmp/emacs/lisp/language /tmp/emacs/lisp/international /tmp/emacs/lisp/textmodes)
Loading emacs-lisp/byte-run (source)...
Loading emacs-lisp/backquote (source)...
Loading subr (source)...
Loading version.el (source)...
Loading widget (source)...
Loading custom (source)...
Loading emacs-lisp/map-ynp (source)...
Loading cus-start (source)...
Loading international/mule (source)...
Loading international/mule-conf.el (source)...
qemu: uncaught target signal 11 (Segmentation fault) - exiting
[{WIFEXITED(s) && WEXITSTATUS(s) == 245}], 0) = 23297
--- SIGCHLD (Child exited) @ 0 (0) ---
sigreturn()                             = ? (mask now [RTMIN])
gettimeofday({1202673637, 380009}, NULL) = 0
getpid()                                = 23296
write(3, "[2008-02-10 20:00:37 23296] rc: "..., 52) = 52
munmap(0x40001000, 4096)                = 0
exit_group(245)                         = ?

Re: 23.0.60 bootstrap fails for maemo

[Jason Rumney]

Thomas Baumann wrote:
> BTW emacs 22.1 compiles fine and runs nicely but with very tiny fonts...
>   
The screens on those Nokia tablets are about 230dpi IIRC, so if they 
only have the usual 100dpi fonts installed, that is to be expected.

Re: 23.0.60 bootstrap fails for maemo

[Thomas Baumann]

Jason Rumney <jasonr@gnu.org> writes:

> Thomas Baumann wrote:
>> BTW emacs 22.1 compiles fine and runs nicely but with very tiny fonts...
>>   
> The screens on those Nokia tablets are about 230dpi IIRC, so if they
> only have the usual 100dpi fonts installed, that is to be expected.

well, this is the main reason to try to get emacs23 up and running on
the tablet. os2008 doesn't seem to support old-style fonts but xft is
well supported.

Re: 23.0.60 bootstrap fails for maemo

[Dan Nicolaescu]

Thomas Baumann <dtbaumann@yahoo.de> writes:

  > I'm trying to compile emacs23 for os2008 using the maemo-4.0 sdk but
  > somehow the bootstrap fails. I'm working with a fresh copy of the cvs
  > files checked out today. 
  > 
  > The problem looks very much like the emacs23/cygwin problem discussed
  > earlier, but I was not able to test all of the possible solutions
  > mentioned there.
  > 
  > Any help is highly appreciated.

Not sure if this helps, but first try to bootstrap on the host so that
you have all the .elc files, and then configure for the target again and
just run make. (If the problem you are facing is the byte compiler
encoding bug that's been discussed here, you might be able to get over
it this way)...

Re: 23.0.60 bootstrap fails for maemo

[Thomas Baumann]

Dan Nicolaescu <dann@ics.uci.edu> wrote:

> Thomas Baumann <dtbaumann@yahoo.de> writes:
> 
>   > I'm trying to compile emacs23 for os2008 using the maemo-4.0 sdk but
>   > somehow the bootstrap fails. I'm working with a fresh copy of the cvs
>   > files checked out today. 
>   > 
>   > The problem looks very much like the emacs23/cygwin problem discussed
>   > earlier, but I was not able to test all of the possible solutions
>   > mentioned there.
>   > 
>   > Any help is highly appreciated.
> 
> Not sure if this helps, but first try to bootstrap on the host so that
> you have all the .elc files, and then configure for the target again and
> just run make. (If the problem you are facing is the byte compiler
> encoding bug that's been discussed here, you might be able to get over
> it this way)...
> 

I think I tried this before - configure with CHINOOK_X86 and compile
(works ok). configure with CHINOOK_ARMEL... and a new error...

if i delete and recompile pre-crt0.o for the target I get the same error
as before

The same occurs when I byte-compile on i686 and for maemo
afterwards. Any ideas where I can help to resolve this issue?

gcc -nostdlib `./prefix-args -Xlinker  -z nocombreloc` -Wl,-znocombreloc  -o temacs pre-crt0.o /usr/lib/crt1.o /usr/lib/crti.o dispnew.o frame.o scroll.o xdisp.o xmenu.o window.o charset.o coding.o category.o ccl.o character.o chartab.o cm.o term.o terminal.o xfaces.o xterm.o xfns.o xselect.o xrdb.o fontset.o xsmfns.o fringe.o image.o gtkutil.o dbusbind.o emacs.o keyboard.o macros.o keymap.o sysdep.o buffer.o filelock.o insdel.o marker.o minibuf.o fileio.o dired.o filemode.o cmds.o casetab.o casefiddle.o indent.o search.o regex.o undo.o alloc.o data.o doc.o editfns.o callint.o eval.o floatfns.o fns.o print.o lread.o syntax.o unexelf.o bytecode.o process.o callproc.o region-cache.o sound.o atimer.o doprnt.o strftime.o intervals.o textprop.o composite.o md5.o    font.o xfont.o ftfont.o xftfo
 nt.o ftxfont.o terminfo.o lastfile.o   vm-limit.o       -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lgli
 b-2.0 -lpthread -lSM -lICE -ltiff -ljpeg -lpng -lz -lm -lX11 -lXft -lfontconfig -lasound  -ldbus-1 -lncurses   -lm -lgcc -lc -lgcc /usr/lib/crtn.o 
/scratchbox/compilers/cs2005q3.2-glibc2.5-arm/bin/../lib/gcc/arm-none-linux-gnueabi/3.4.4/../../../../arm-none-linux-gnueabi/bin/ld: pre-crt0.o: Relocations in generic ELF (EM: 3)
/scratchbox/compilers/cs2005q3.2-glibc2.5-arm/bin/../lib/gcc/arm-none-linux-gnueabi/3.4.4/../../../../arm-none-linux-gnueabi/bin/ld: pre-crt0.o: Relocations in generic ELF (EM: 3)
pre-crt0.o: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
make[1]: *** [temacs] Error 1
make[1]: Leaving directory `/tmp/emacs/src'
make: *** [src] Error 2

Re: 23.0.60 bootstrap fails for maemo

[Dan Nicolaescu]

Thomas Baumann <dtbaumann@yahoo.de> writes:

  > Dan Nicolaescu <dann@ics.uci.edu> wrote:
  > 
  > > Thomas Baumann <dtbaumann@yahoo.de> writes:
  > > 
  > >   > I'm trying to compile emacs23 for os2008 using the maemo-4.0 sdk but
  > >   > somehow the bootstrap fails. I'm working with a fresh copy of the cvs
  > >   > files checked out today. 
  > >   > 
  > >   > The problem looks very much like the emacs23/cygwin problem discussed
  > >   > earlier, but I was not able to test all of the possible solutions
  > >   > mentioned there.
  > >   > 
  > >   > Any help is highly appreciated.
  > > 
  > > Not sure if this helps, but first try to bootstrap on the host so that
  > > you have all the .elc files, and then configure for the target again and
  > > just run make. (If the problem you are facing is the byte compiler
  > > encoding bug that's been discussed here, you might be able to get over
  > > it this way)...
  > > 
  > 
  > I think I tried this before - configure with CHINOOK_X86 and compile
  > (works ok). configure with CHINOOK_ARMEL... and a new error...

Sorry, no other ideas.  
Maybe when you can run on the target, you could try debugging to see
what is actually going on...

Re: 23.0.60 bootstrap fails for maemo

[Thomas Baumann]

> Dan Nicolaescu <dann@ics.uci.edu> wrote:
>
>> Thomas Baumann <dtbaumann@yahoo.de> writes:
>> 
>>   > I'm trying to compile emacs23 for os2008 using the maemo-4.0 sdk but
>>   > somehow the bootstrap fails. I'm working with a fresh copy of the cvs
>>   > files checked out today. 
>>   > 
>>   > The problem looks very much like the emacs23/cygwin problem discussed
>>   > earlier, but I was not able to test all of the possible solutions
>>   > mentioned there.
>>   > 
>>   > Any help is highly appreciated.
>> 
>> Not sure if this helps, but first try to bootstrap on the host so that
>> you have all the .elc files, and then configure for the target again and
>> just run make. (If the problem you are facing is the byte compiler
>> encoding bug that's been discussed here, you might be able to get over
>> it this way)...
>> 
>
> I think I tried this before - configure with CHINOOK_X86 and compile
> (works ok). configure with CHINOOK_ARMEL... and a new error...
>
> if i delete and recompile pre-crt0.o for the target I get the same error
> as before
>

After days of testing and trying to debug the bootstrap I finally
compiled the byte-compile parts of bootstrap directly on the N810: and
it works :-) Strange and not a permanent solution, though. 

In summary, byte compilation segfaults during bootstrap using the maemo
SDK.

1. the symptoms are the same mentioned in the "windows bootsrap failure
   thread". If someone could send me the things changed there or maybe
   have a look at what's necessary to implement the same changes for the
   arm target. 

2. charprop.el, uni-*.el (and maybe others) always have to be
   regenerated, thus raising the mentioned errors regardless if all the
   other lisp files are already compiled.

3. compilation is possible on the target itself: the build directory has
   to be mounted with nfs and make has to be installed on the
   device. Compile emacs until the first error occurs, continue on the
   target and finally make install and build the package on the host.

Re: 23.0.60 bootstrap fails for maemo

[Jason Rumney]

Thomas Baumann wrote:
> 1. the symptoms are the same mentioned in the "windows bootsrap failure
>    thread". If someone could send me the things changed there or maybe
>    have a look at what's necessary to implement the same changes for the
>    arm target.

There was a problem reported for Cygwin that might have been on that 
thread that could be relevant. The same problem was reported for 
GNUStep, I think and affects all CANNOT_DUMP platforms.

> 2. charprop.el, uni-*.el (and maybe others) always have to be
>    regenerated, thus raising the mentioned errors regardless if all the
>    other lisp files are already compiled.
>   

You need to update from CVS. Those files are no longer generated during 
bootstrap.

Re: 23.0.60 bootstrap fails for maemo

[Leo]

On 2008-02-17 18:55 +0000, Thomas Baumann wrote:
> After days of testing and trying to debug the bootstrap I finally
> compiled the byte-compile parts of bootstrap directly on the N810: and
> it works :-) Strange and not a permanent solution, though. 

I wonder if there is any developer like to improve the support for
maemo. We probably could propose to Nokia and ask them to donate a few
N810s for our developers.

Best,
-- 
.:  Leo  :.  [ sdl.web AT gmail.com ]  .:  [ GPG Key: 9283AA3F ]  :.

          Use the best OS -- http://www.fedoraproject.org/

Re: 23.0.60 bootstrap fails for maemo

[T Baumann]

--- Leo <sdl.web@gmail.com> schrieb:

> On 2008-02-17 18:55 +0000, Thomas Baumann wrote:
> > After days of testing and trying to debug the
> bootstrap I finally
> > compiled the byte-compile parts of bootstrap
> directly on the N810: and
> > it works :-) Strange and not a permanent solution,
> though. 
> 
> I wonder if there is any developer like to improve
> the support for
> maemo. We probably could propose to Nokia and ask
> them to donate a few
> N810s for our developers.
> 

:-)

Of course I'd like to improve support for maemo, a
hildonized interface would be cool. But, I already
paid for my N810....


      Lesen Sie Ihre E-Mails jetzt einfach von unterwegs.
www.yahoo.de/go

Re: 23.0.60 bootstrap fails for maemo

[T Baumann]

--- Jason Rumney <jasonr@gnu.org> schrieb:

> Thomas Baumann wrote:
> > 1. the symptoms are the same mentioned in the
> "windows bootsrap failure
> >    thread". If someone could send me the things
> changed there or maybe
> >    have a look at what's necessary to implement
> the same changes for the
> >    arm target.
> 
> There was a problem reported for Cygwin that might
> have been on that 
> thread that could be relevant. The same problem was
> reported for 
> GNUStep, I think and affects all CANNOT_DUMP
> platforms.
> 

Apart from changes to sheap.c (which are not
applicable to arm) and compiling w/o gtk (which makes
no sense for N810) I did not find any hints in that
thread or in the ChangeLogs.

I'm going to give it another try this evening with
fresh CVS files...

> > 2. charprop.el, uni-*.el (and maybe others) always
> have to be
> >    regenerated, thus raising the mentioned errors
> regardless if all the
> >    other lisp files are already compiled.
> >   
> 
> You need to update from CVS. Those files are no
> longer generated during 
> bootstrap.
> 
> 



      Jetzt Mails schnell in einem Vorschaufenster überfliegen. Dies und viel mehr bietet das neue Yahoo! Mail - www.yahoo.de/mail

Re: 23.0.60 bootstrap fails for maemo

[Thomas Baumann]

> I wonder if there is any developer like to improve the support for
> maemo. We probably could propose to Nokia and ask them to donate a few
> N810s for our developers.

:-)

Of course I'd like to improve support for maemo, a
hildonized interface would be cool. But, I already
paid for my N810....

Re: 23.0.60 bootstrap fails for maemo

[Thomas Baumann]

Jason Rumney <jasonr@gnu.org> writes:

>
> You need to update from CVS. Those files are no longer generated
> during bootstrap.

CVS checked out a few minutes ago:
     make bootstrap on host, make-dist on host,
     configure and make in scratchbox 
     still segfaults during the dump step.

LC_ALL=C `/bin/pwd`/temacs -batch -l loadup dump
Loading loadup.el (source)...
Using load-path (/tmp/emacstb/lisp)
Loading emacs-lisp/byte-run...
Loading emacs-lisp/backquote...
Loading subr...
Loading version.el (source)...
Loading widget...
Loading custom (compiled; note, source file is newer)...
Loading emacs-lisp/map-ynp...
Loading cus-start (compiled; note, source file is newer)...
Loading international/mule...
Loading international/mule-conf.el (source)...
qemu: uncaught target signal 11 (Segmentation fault) - exiting
make[1]: *** [emacs] Error 245
make: *** [src] Error 2

Re: 23.0.60 bootstrap fails for maemo

[Dan Nicolaescu]

Thomas Baumann <dtbaumann@yahoo.de> writes:

  > > Dan Nicolaescu <dann@ics.uci.edu> wrote:
  > >
  > >> Thomas Baumann <dtbaumann@yahoo.de> writes:
  > >> 
  > >>   > I'm trying to compile emacs23 for os2008 using the maemo-4.0 sdk but
  > >>   > somehow the bootstrap fails. I'm working with a fresh copy of the cvs
  > >>   > files checked out today. 
  > >>   > 
  > >>   > The problem looks very much like the emacs23/cygwin problem discussed
  > >>   > earlier, but I was not able to test all of the possible solutions
  > >>   > mentioned there.
  > >>   > 
  > >>   > Any help is highly appreciated.
  > >> 
  > >> Not sure if this helps, but first try to bootstrap on the host so that
  > >> you have all the .elc files, and then configure for the target again and
  > >> just run make. (If the problem you are facing is the byte compiler
  > >> encoding bug that's been discussed here, you might be able to get over
  > >> it this way)...
  > >> 
  > >
  > > I think I tried this before - configure with CHINOOK_X86 and compile
  > > (works ok). configure with CHINOOK_ARMEL... and a new error...
  > >
  > > if i delete and recompile pre-crt0.o for the target I get the same error
  > > as before
  > >
  > 
  > After days of testing and trying to debug the bootstrap I finally
  > compiled the byte-compile parts of bootstrap directly on the N810: and
  > it works :-) Strange and not a permanent solution, though. 
  > 
[snip]
  > 3. compilation is possible on the target itself: the build directory has
  >    to be mounted with nfs and make has to be installed on the
  >    device. Compile emacs until the first error occurs, continue on the
  >    target and finally make install and build the package on the host.

So it seems that building works on real hardware, but it fails when
using the cross-compiler + simulator. That would point out to a problem
in that setup, maybe a bug in the simulator.

Re: 23.0.60 bootstrap fails for maemo

[Thomas Baumann]

Dan Nicolaescu <dann@ics.uci.edu> writes:

> Thomas Baumann <dtbaumann@yahoo.de> writes:
>
>   > > Dan Nicolaescu <dann@ics.uci.edu> wrote:
>   > >
>   > >> Thomas Baumann <dtbaumann@yahoo.de> writes:
>   > >> 
>   > >>   > I'm trying to compile emacs23 for os2008 using the maemo-4.0 sdk but
>   > >>   > somehow the bootstrap fails. I'm working with a fresh copy of the cvs
>   > >>   > files checked out today. 
>   > >>   > 
>   > >>   > The problem looks very much like the emacs23/cygwin problem discussed
>   > >>   > earlier, but I was not able to test all of the possible solutions
>   > >>   > mentioned there.
>   > >>   > 
>   > >>   > Any help is highly appreciated.
>   > >> 
>   > >> Not sure if this helps, but first try to bootstrap on the host so that
>   > >> you have all the .elc files, and then configure for the target again and
>   > >> just run make. (If the problem you are facing is the byte compiler
>   > >> encoding bug that's been discussed here, you might be able to get over
>   > >> it this way)...
>   > >> 
>   > >
>   > > I think I tried this before - configure with CHINOOK_X86 and compile
>   > > (works ok). configure with CHINOOK_ARMEL... and a new error...
>   > >
>   > > if i delete and recompile pre-crt0.o for the target I get the same error
>   > > as before
>   > >
>   > 
>   > After days of testing and trying to debug the bootstrap I finally
>   > compiled the byte-compile parts of bootstrap directly on the N810: and
>   > it works :-) Strange and not a permanent solution, though. 
>   > 
> [snip]
>   > 3. compilation is possible on the target itself: the build directory has
>   >    to be mounted with nfs and make has to be installed on the
>   >    device. Compile emacs until the first error occurs, continue on the
>   >    target and finally make install and build the package on the host.
>
> So it seems that building works on real hardware, but it fails when
> using the cross-compiler + simulator. That would point out to a problem
> in that setup, maybe a bug in the simulator.

I think the latter, as the setup was installed from scratch. Debugging,
however, is beyond my current debbuging skills. All I can offer is to
test possible solutions.

Another observation: Currently only emacs23 (bootstrap and make) and clisp
compilation fail. Other programs (emacs22, ocaml, R, unison, ...) are
fine.

Re: 23.0.60 bootstrap fails for maemo

[Dan Nicolaescu]

Thomas Baumann <dtbaumann@yahoo.de> writes:

  > Dan Nicolaescu <dann@ics.uci.edu> writes:
  > 
  > > Thomas Baumann <dtbaumann@yahoo.de> writes:
  > >
  > >   > > Dan Nicolaescu <dann@ics.uci.edu> wrote:
  > >   > >
  > >   > >> Thomas Baumann <dtbaumann@yahoo.de> writes:
  > >   > >> 
  > >   > >>   > I'm trying to compile emacs23 for os2008 using the maemo-4.0 sdk but
  > >   > >>   > somehow the bootstrap fails. I'm working with a fresh copy of the cvs
  > >   > >>   > files checked out today. 
  > >   > >>   > 
  > >   > >>   > The problem looks very much like the emacs23/cygwin problem discussed
  > >   > >>   > earlier, but I was not able to test all of the possible solutions
  > >   > >>   > mentioned there.
  > >   > >>   > 
  > >   > >>   > Any help is highly appreciated.
  > >   > >> 
  > >   > >> Not sure if this helps, but first try to bootstrap on the host so that
  > >   > >> you have all the .elc files, and then configure for the target again and
  > >   > >> just run make. (If the problem you are facing is the byte compiler
  > >   > >> encoding bug that's been discussed here, you might be able to get over
  > >   > >> it this way)...
  > >   > >> 
  > >   > >
  > >   > > I think I tried this before - configure with CHINOOK_X86 and compile
  > >   > > (works ok). configure with CHINOOK_ARMEL... and a new error...
  > >   > >
  > >   > > if i delete and recompile pre-crt0.o for the target I get the same error
  > >   > > as before
  > >   > >
  > >   > 
  > >   > After days of testing and trying to debug the bootstrap I finally
  > >   > compiled the byte-compile parts of bootstrap directly on the N810: and
  > >   > it works :-) Strange and not a permanent solution, though. 
  > >   > 
  > > [snip]
  > >   > 3. compilation is possible on the target itself: the build directory has
  > >   >    to be mounted with nfs and make has to be installed on the
  > >   >    device. Compile emacs until the first error occurs, continue on the
  > >   >    target and finally make install and build the package on the host.
  > >
  > > So it seems that building works on real hardware, but it fails when
  > > using the cross-compiler + simulator. That would point out to a problem
  > > in that setup, maybe a bug in the simulator.
  > 
  > I think the latter, as the setup was installed from scratch. Debugging,
  > however, is beyond my current debbuging skills. All I can offer is to
  > test possible solutions.

Then, probably the best option is to forward this to the simulator's
maintainers.