Author Topic: Compiling Problems... (Read 6969 times)

conundrum · « **on:** February 01, 2005, 04:39:32 am »

Hi all, I'm a bit of a Linux noob so please bare with me.

I just upgraded to RC9 from RC8, and this problem is persistent. I have had a shell on a friend of mine's machine for a while, so there are some command line programs I have become quite fond of. Pico is one of them (I was able to compile this with no problems since RC5, and had no problems on RC9), as is screen (which would not compile properly on RC8, but does on RC9). The last program on my (for now) short list of desired command line programs is epic. I know bitchx is availible, but I am very, very stubborn.

When I try to compile epic (after running configure, mounting the dev img and trying "make") everything seems to compile fine up until dcc.c. I don't really know how to copy the output from the terminal (I was told to select it, and then right click, which did not work), but the errors came from undefine functions (I think) withint dcc.c. If anyone else could test or confirm this, or even tell me how to get output from the terminal that would be great.

Link to epic: http://www.epicsol.org/

pgas · « **Reply #1 on:** February 01, 2005, 05:11:55 am »

To copy text in X:

* select the text

* click the middle button (or the action that emulates middle button for you in pdaxrom)
in, say, a text editor a text area or whatever.

To have the output of the compilation saved in a file, run make like this:

Code: [Select]

make > make.log 2>&1
This will write all the compilation message to a file named make.log.
(you can use whatever name you want not just make.log, this works with
any commands not juste make)

conundrum · « **Reply #2 on:** February 01, 2005, 05:29:35 am »

Thanks pgas, I will get the errors up later today. I was told that make wouldn't work like other commands do with > [output file], guess I need to yell at some friends of mine.

pgas · « **Reply #3 on:** February 01, 2005, 06:35:59 am »

The important part is the 2>&1, in unix you have 3 standard streams one input stream, one standard output and one standard error.

You see both error and output mixed on your terminal, but when you output to a file with > file.log only the standard output is redirected to the file. The 2>&1 is there to say redirect the standard error to the standard output.

And as the bash man page says "Note that the order of redirections is significant"

lardman · « **Reply #4 on:** February 01, 2005, 07:22:45 am »

:-)

Of course you could just do:

Code: [Select]

make &> make.log
Which does the same thing (with less key presses ;-))

Si

pgas · « **Reply #5 on:** February 01, 2005, 07:39:58 am »

Hey, who told you to read the man page that far!

conundrum · « **Reply #6 on:** February 01, 2005, 03:07:19 pm »

Thanks guys, here are the error messages:

Code: [Select]

gcc -g -O  -I./../include -I../include -c dcc.c
dcc.c: In function `dcc_connected':
dcc.c:709: error: `NI_NUMERICHOST' undeclared (first use in this function)
dcc.c:709: error: (Each undeclared identifier is reported only once
dcc.c:709: error: for each function it appears in.)
dcc.c: In function `dcc_send_booster_ctcp':
dcc.c:967: error: `NI_NUMERICHOST' undeclared (first use in this function)
dcc.c: In function `register_dcc_offer':
dcc.c:2151: error: `AI_NUMERICHOST' undeclared (first use in this function)
dcc.c:2163: error: `NI_NUMERICHOST' undeclared (first use in this function)
dcc.c: In function `process_dcc_chat_connection':
dcc.c:2576: error: `NI_NUMERICHOST' undeclared (first use in this function)
dcc.c: In function `process_dcc_send_connection':
dcc.c:2888: error: `NI_NUMERICHOST' undeclared (first use in this function)
dcc.c: In function `dccctl':
dcc.c:3586: error: `NI_NUMERICHOST' undeclared (first use in this function)
make[1]: *** [dcc.o] Error 1
make[1]: Leaving directory `/mnt/card/epic4-2.0/source'
make: *** [epic] Error 2

titus · « **Reply #7 on:** February 01, 2005, 04:38:45 pm »

hi conundrum,

i think there are some header files missing...

i have just compiled epic4-2.2 fpr pdaxrom rc9...

i never packed an ipk, so i first have to get a howto ;-)

but you can take the archiv from my server an put it all to /usr... it should work

if i succeeded in packaging i put an new one to the server.

Download:

http://complab.de/zaurus/pdaxrom/rc9/unsta...pic4-2.2.tar.gz

have fun!

titus

conundrum · « **Reply #8 on:** February 01, 2005, 05:15:09 pm »

Well titus, I have the GCC headers, so unless the packages provided by Laze and the pdaXrom team are incomplete (), I don't know what the problem could be. Thanks for sharing!

titus · « **Reply #9 on:** February 01, 2005, 05:25:41 pm »

Quote

Well titus, I have the GCC headers, so unless the packages provided by Laze and the pdaXrom team are incomplete (), I don't know what the problem could be. Thanks for sharing!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=64992\"][{POST_SNAPBACK}][/a][/div]

i didn't use the gcc.img from pdaxrom.org website but the ipks in the feed... i don't know what is really needed, i maybe added some packages from the personal feeds listed in the pinned feed thread... when my zaur is ready with the actual compiling i can have a look on my packages...

but i was only able to compile epic after removing of flex... other sources seems to need flex, i don't know what's the matter...

titus

conundrum · « **Reply #10 on:** February 02, 2005, 03:02:04 pm »

Ah, you cross compiled this? Perhaps that's the issue, something native only to pdaXrom. Can someone else spare some processor time try and compile epic natively? I can provide quick instructions if need be.

Hopefully the problem lies with me, not pdaXrom or the native compiling image.

pgas · « **Reply #11 on:** February 02, 2005, 03:50:22 pm »

the missings identifiers seems to be defined in include/gailib.h from the epic source from what I can see...

I don't know why the compiler can find them in your case...
Did you modify something?

titus · « **Reply #12 on:** February 02, 2005, 08:19:12 pm »

Quote

Ah, you cross compiled this? Perhaps that's the issue, something native only to pdaXrom. Can someone else spare some processor time try and compile epic natively?

no, i've compiled it on zaurus... i don't know this programm... so i didn't tested the compilation in all matters...
i think it is more than a simple irc client, or you could use one of the gtk clients from feed...

is it working in all kinds?

titus · « **Reply #13 on:** February 02, 2005, 08:36:35 pm »

something else:

i wasn't able to compile wzdftpd with my system... without flex it couldn't compile and with flex i've got parsing errors on unicode expressions as far as i undertood...

is there an better to handle replace for flex or what else i may did wrong?

titus

conundrum · « **Reply #14 on:** February 03, 2005, 02:19:54 am »

pgas, no not a thing. Does it matter that I install all my compiling stuff on the SD card because of it's considerable size?

News:

Author Topic: Compiling Problems... (Read 6969 times)