Thread: Re: [Emile-devel] Compiling EMILE Errors
Status: Beta
Brought to you by:
lvivier
Menu
▾
▴
emile-devel
|
From: <la...@lv...> - 2008-08-13 14:31:23
|
Hi, install docbook-to-man, docbook2man is not able to manage two suffixes (i.e. ".conf.sgml"). Regards, Laurent Hi All, I tried to compile EMILE 0.12, but I get these errors when it's processing the man pages: make -C docs all docbook2man emile.conf.sgml Using catalogs: /etc/sgml/catalog Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print Working on: /home/g1powermac/Desktop/emile-0.12/docs/emile.conf.sgml <La...@lv...> LaurentVivier2008Laurent VivierJuly 22, 2008Done. gzip -9f emile.conf.5 gzip: emile.conf.5: No such file or directory make[1]: *** [emile.conf.5.gz] Error 1 make: *** [docs] Error 2 emile.conf.5 does not exist in the docs directory, only emile.5. Anyone know how to fix this? Thanks, J Silverman |
|
From: J S. <g1p...@ya...> - 2008-08-13 16:05:27
|
Hi Laurent,
Yup, that fixed it. It now gets into the actual code compiling before it errors out again:
load.o: In function `load_ramdisk':
load.c:(.text+0x284): undefined reference to `__stdout'
load.c:(.text+0x2e2): undefined reference to `fputc'
load.c:(.text+0x2f2): undefined reference to `__fputc_unlocked'
/home/g1powermac/Desktop/emile-0.12/second/../libui/libui.a(progressbar.o): In function `emile_progressbar_value':
progressbar.c:(.text+0x5a): undefined reference to `__stdout'
progressbar.c:(.text+0x82): undefined reference to `__fputc_unlocked'
progressbar.c:(.text+0x90): undefined reference to `fputc'
/home/g1powermac/Desktop/emile-0.12/second/../libui/libui.a(progressbar.o): In function `emile_progressbar_create':
progressbar.c:(.text+0x14e): undefined reference to `__stdout'
progressbar.c:(.text+0x174): undefined reference to `__fputc_unlocked'
progressbar.c:(.text+0x182): undefined reference to `fputc'
/home/g1powermac/Desktop/emile-0.12/second/../libui/libui.a(scrolllist.o): In function `display_list':
scrolllist.c:(.text+0x6e): undefined reference to `__stdout'
scrolllist.c:(.text+0xc2): undefined reference to `__fputc_unlocked'
scrolllist.c:(.text+0xd0): undefined reference to `fputc'
scrolllist.c:(.text+0xea): undefined reference to `__stdout'
scrolllist.c:(.text+0x110): undefined reference to `__fputc_unlocked'
scrolllist.c:(.text+0x11e): undefined reference to `fputc'
/home/g1powermac/Desktop/emile-0.12/second/../libui/libui.a(edit.o): In function `emile_edit':
edit.c:(.text+0xb8): undefined reference to `__stdout'
edit.c:(.text+0xda): undefined reference to `__fputc_unlocked'
edit.c:(.text+0xe6): undefined reference to `fputc'
edit.c:(.text+0x17e): undefined reference to `__stdout'
edit.c:(.text+0x1c6): undefined reference to `__stdout'
edit.c:(.text+0x1ec): undefined reference to `__fputc_unlocked'
edit.c:(.text+0x1fa): undefined reference to `fputc'
edit.c:(.text+0x210): undefined reference to `__stdout'
edit.c:(.text+0x236): undefined reference to `__fputc_unlocked'
edit.c:(.text+0x246): undefined reference to `fputc'
edit.c:(.text+0x25c): undefined reference to `__stdout'
edit.c:(.text+0x282): undefined reference to `__fputc_unlocked'
edit.c:(.text+0x290): undefined reference to `fputc'
edit.c:(.text+0x2c2): undefined reference to `__stdout'
edit.c:(.text+0x2ec): undefined reference to `__fputc_unlocked'
edit.c:(.text+0x2fa): undefined reference to `fputc'
/home/g1powermac/Desktop/emile-0.12/second/../libui/libui.a(window.o): In function `emile_window':
window.c:(.text+0x42): undefined reference to `__stdout'
window.c:(.text+0x6c): undefined reference to `__fputc_unlocked'
window.c:(.text+0x7a): undefined reference to `fputc'
window.c:(.text+0xa8): undefined reference to `__fputc_unlocked'
window.c:(.text+0xb6): undefined reference to `fputc'
window.c:(.text+0xc4): undefined reference to `__stdout'
window.c:(.text+0xee): undefined reference to `__fputc_unlocked'
window.c:(.text+0xfc): undefined reference to `fputc'
window.c:(.text+0x13a): undefined reference to `__fputc_unlocked'
window.c:(.text+0x148): undefined reference to `fputc'
window.c:(.text+0x15c): undefined reference to `__stdout'
window.c:(.text+0x184): undefined reference to `__fputc_unlocked'
window.c:(.text+0x192): undefined reference to `fputc'
window.c:(.text+0x1a2): undefined reference to `__stdout'
window.c:(.text+0x1de): undefined reference to `__fputc_unlocked'
window.c:(.text+0x1ec): undefined reference to `fputc'
window.c:(.text+0x21a): undefined reference to `__fputc_unlocked'
window.c:(.text+0x228): undefined reference to `fputc'
window.c:(.text+0x232): undefined reference to `__stdout'
window.c:(.text+0x25c): undefined reference to `__fputc_unlocked'
window.c:(.text+0x26a): undefined reference to `fputc'
make[2]: *** [second.o] Error 1
make[1]: *** [m68k-linux-floppy/second] Error 2
make: *** [second/m68k-linux-floppy/second] Error 2
I am using my own custom built toolchain using buildroot. It is using gcc 4.1.2 and uClibc 0.9.29.
Thanks,
J Silverman
--- On Wed, 8/13/08, la...@lv... <la...@lv...> wrote:
From: la...@lv... <la...@lv...>
Subject: RE: [Emile-devel] Compiling EMILE Errors
To: emi...@li..., g1p...@ya...
Date: Wednesday, August 13, 2008, 10:31 AM
Hi,
install docbook-to-man, docbook2man is not able to manage two suffixes (i.e. ".conf.sgml").
Regards,
Laurent
Hi All,
I tried to compile EMILE 0.12, but I get these errors when it's processing the man pages:
make -C docs all
docbook2man emile.conf.sgml
Using catalogs: /etc/sgml/catalog
Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
Working on: /home/g1powermac/Desktop/emile-0.12/docs/emile.conf.sgml
<La...@lv...>
LaurentVivier2008Laurent VivierJuly 22, 2008Done.
gzip -9f emile.conf.5
gzip: emile.conf.5: No such file or directory
make[1]: *** [emile.conf.5.gz] Error 1
make: *** [docs] Error 2
emile.conf.5 does not exist in the docs directory, only emile.5. Anyone know how to fix this?
Thanks,
J Silverman
|
|
From: Laurent V. <la...@lv...> - 2008-08-13 16:49:32
|
Le 13 août 08 à 17:18, J Silverman a écrit : > I am using my own custom built toolchain using buildroot. It is > using gcc 4.1.2 and uClibc 0.9.29. Use gcc3, EMILE doesn't work when compiled with gcc4 (perhaps a problem in the optimisation, some "barriers" could solves the problem...). And if with gcc3 it doesn't compile, use libc6, EMILE depends on libc headers (perhaps it's not a good choice...) BTW, I'm on vacation from tomorrow to the 1st september without internet access... Laurent ----------------------- Laurent Vivier ---------------------- "The best way to predict the future is to invent it." - Alan Kay |
|
From: J S. <g1p...@ya...> - 2008-08-14 12:26:14
|
Hi All, Alright, I got some progress to report on! Since EMILE needs glibc, I decided to try out compiling it using a crosstools build of gcc (http://www.kegel.com/crosstool/). After a bit of hacking, I was able to get EMILE to compile using the latest m68k toolchain available (which uses gcc 4.10). All that was needed to be done to the EMILE source was change the '.cpu 68000' pseudo op in any of the assembly source files that contain it to '.chip 68000'. I have not tested to see if this build works yet, which actually leads me to my next question. Which kernel do you guys put in the floppy image? I'm wanting to try to see if I can get a 2.6.x kernel in it, though not sure how possible it is with the size constraint. Thanks, J Silverman --- On Wed, 8/13/08, Laurent Vivier <la...@lv...> wrote: > From: Laurent Vivier <la...@lv...> > Subject: Re: [Emile-devel] Compiling EMILE Errors > To: "J Silverman" <g1p...@ya...> > Cc: emi...@li... > Date: Wednesday, August 13, 2008, 12:47 PM > Le 13 août 08 à 17:18, J Silverman a écrit : > > > I am using my own custom built toolchain using > buildroot. It is > > using gcc 4.1.2 and uClibc 0.9.29. > > > Use gcc3, EMILE doesn't work when compiled with gcc4 > (perhaps a > problem in the optimisation, some "barriers" > could solves the > problem...). > And if with gcc3 it doesn't compile, use libc6, EMILE > depends on libc > headers (perhaps it's not a good choice...) > > BTW, I'm on vacation from tomorrow to the 1st september > without > internet access... > > Laurent > ----------------------- Laurent Vivier > ---------------------- > "The best way to predict the future is to invent > it." > - Alan Kay |
|
From: J S. <g1p...@ya...> - 2008-08-14 18:40:16
|
Hi All, Alright, I was able to make up a floppy image using the test kernel and ramdisk up on the EMILE site and write it to a floppy. EMILE loads fine, however the second it goes to load the kernel I get the sad mac with the following error codes: 0000000F 00000001. Anyone might have a guess as to whats going on? Thanks, J Silverman --- On Thu, 8/14/08, J Silverman <g1p...@ya...> wrote: > From: J Silverman <g1p...@ya...> > Subject: Re: [Emile-devel] Compiling EMILE Errors > To: "Laurent Vivier" <la...@lv...> > Cc: emi...@li... > Date: Thursday, August 14, 2008, 8:26 AM > Hi All, > > Alright, I got some progress to report on! Since EMILE > needs glibc, I decided to try out compiling it using a > crosstools build of gcc (http://www.kegel.com/crosstool/). > After a bit of hacking, I was able to get EMILE to compile > using the latest m68k toolchain available (which uses gcc > 4.10). All that was needed to be done to the EMILE source > was change the '.cpu 68000' pseudo op in any of the > assembly source files that contain it to '.chip > 68000'. I have not tested to see if this build works > yet, which actually leads me to my next question. Which > kernel do you guys put in the floppy image? I'm wanting > to try to see if I can get a 2.6.x kernel in it, though not > sure how possible it is with the size constraint. > > Thanks, > J Silverman > > > --- On Wed, 8/13/08, Laurent Vivier > <la...@lv...> wrote: > > > From: Laurent Vivier <la...@lv...> > > Subject: Re: [Emile-devel] Compiling EMILE Errors > > To: "J Silverman" > <g1p...@ya...> > > Cc: emi...@li... > > Date: Wednesday, August 13, 2008, 12:47 PM > > Le 13 août 08 à 17:18, J Silverman a écrit : > > > > > I am using my own custom built toolchain using > > buildroot. It is > > > using gcc 4.1.2 and uClibc 0.9.29. > > > > > > Use gcc3, EMILE doesn't work when compiled with > gcc4 > > (perhaps a > > problem in the optimisation, some "barriers" > > could solves the > > problem...). > > And if with gcc3 it doesn't compile, use libc6, > EMILE > > depends on libc > > headers (perhaps it's not a good choice...) > > > > BTW, I'm on vacation from tomorrow to the 1st > september > > without > > internet access... > > > > Laurent > > ----------------------- Laurent Vivier > > ---------------------- > > "The best way to predict the future is to invent > > it." > > - Alan Kay > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move > Developer's challenge > Build the coolest Linux based applications with Moblin SDK > & win great prizes > Grand prize is a trip for two to an Open Source event > anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Emile-devel mailing list > Emi...@li... > https://lists.sourceforge.net/lists/listinfo/emile-devel |
|
From: J S. <g1p...@ya...> - 2008-08-14 18:57:15
|
Hi All, Nevermind, I found the problem. Even though EMILE compiled fine with the crosstool's build of gcc-4.10, it's what actually caused the error. I rebuilt it with gcc-3.4.5, and it booted the test kernel perfectly. Now I just need to figure out how to build my own 2.6 kernel that'll fit on a floppy and still boot. . . Thanks, J Silverman --- On Thu, 8/14/08, J Silverman <g1p...@ya...> wrote: > From: J Silverman <g1p...@ya...> > Subject: Re: [Emile-devel] Compiling EMILE Errors > To: "Laurent Vivier" <la...@lv...> > Cc: emi...@li... > Date: Thursday, August 14, 2008, 2:40 PM > Hi All, > > Alright, I was able to make up a floppy image using the > test kernel and ramdisk up on the EMILE site and write it to > a floppy. EMILE loads fine, however the second it goes to > load the kernel I get the sad mac with the following error > codes: 0000000F 00000001. Anyone might have a guess as to > whats going on? > > Thanks, > J Silverman > > > --- On Thu, 8/14/08, J Silverman > <g1p...@ya...> wrote: > > > From: J Silverman <g1p...@ya...> > > Subject: Re: [Emile-devel] Compiling EMILE Errors > > To: "Laurent Vivier" > <la...@lv...> > > Cc: emi...@li... > > Date: Thursday, August 14, 2008, 8:26 AM > > Hi All, > > > > Alright, I got some progress to report on! Since > EMILE > > needs glibc, I decided to try out compiling it using a > > crosstools build of gcc > (http://www.kegel.com/crosstool/). > > After a bit of hacking, I was able to get EMILE to > compile > > using the latest m68k toolchain available (which uses > gcc > > 4.10). All that was needed to be done to the EMILE > source > > was change the '.cpu 68000' pseudo op in any > of the > > assembly source files that contain it to '.chip > > 68000'. I have not tested to see if this build > works > > yet, which actually leads me to my next question. > Which > > kernel do you guys put in the floppy image? I'm > wanting > > to try to see if I can get a 2.6.x kernel in it, > though not > > sure how possible it is with the size constraint. > > > > Thanks, > > J Silverman > > > > > > --- On Wed, 8/13/08, Laurent Vivier > > <la...@lv...> wrote: > > > > > From: Laurent Vivier <la...@lv...> > > > Subject: Re: [Emile-devel] Compiling EMILE Errors > > > To: "J Silverman" > > <g1p...@ya...> > > > Cc: emi...@li... > > > Date: Wednesday, August 13, 2008, 12:47 PM > > > Le 13 août 08 à 17:18, J Silverman a écrit : > > > > > > > I am using my own custom built toolchain > using > > > buildroot. It is > > > > using gcc 4.1.2 and uClibc 0.9.29. > > > > > > > > > Use gcc3, EMILE doesn't work when compiled > with > > gcc4 > > > (perhaps a > > > problem in the optimisation, some > "barriers" > > > could solves the > > > problem...). > > > And if with gcc3 it doesn't compile, use > libc6, > > EMILE > > > depends on libc > > > headers (perhaps it's not a good choice...) > > > > > > BTW, I'm on vacation from tomorrow to the 1st > > september > > > without > > > internet access... > > > > > > Laurent > > > ----------------------- Laurent Vivier > > > ---------------------- > > > "The best way to predict the future is to > invent > > > it." > > > - Alan Kay > > > > > > > > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move > > Developer's challenge > > Build the coolest Linux based applications with Moblin > SDK > > & win great prizes > > Grand prize is a trip for two to an Open Source event > > anywhere in the world > > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > Emile-devel mailing list > > Emi...@li... > > > https://lists.sourceforge.net/lists/listinfo/emile-devel > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move > Developer's challenge > Build the coolest Linux based applications with Moblin SDK > & win great prizes > Grand prize is a trip for two to an Open Source event > anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Emile-devel mailing list > Emi...@li... > https://lists.sourceforge.net/lists/listinfo/emile-devel |
Thanks for helping keep SourceForge clean.
X