[gentoo-embedded] problem cross-emerging minicom

[gentoo-embedded] problem cross-emerging minicom

[Jakub Ladman]

Hello dear friends

For bebugging a serial comunication i need to build minicom terminal for my 
SH4 system.
Ebuild has not the sh keyword and it fails even if i have copied ebuild to 
portage overlay and add the keyword.

I get this error message: 

sh4-pc-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I..   -I../lib  -Os -pipe -fPIC -I../intl -Wall -W -c 
dial.c
sh4-pc-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I..   -I../lib  -Os -pipe -fPIC -I../intl -Wall -W -c 
window.c
window.c: In function `_gotoxy':
window.c:325: error: `BC' undeclared (first use in this function)
window.c:325: error: (Each undeclared identifier is reported only once
window.c:325: error: for each function it appears in.)
window.c: In function `win_init':
window.c:1925: error: `BC' undeclared (first use in this function)
make[2]: *** [window.o] Error 1
make[2]: Leaving directory 
`/var/tmp/portage/minicom-2.1-r2/work/minicom-2.1/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/minicom-2.1-r2/work/minicom-2.1'
make: *** [all-recursive-am] Error 2


I do not udestand the problem.
Can you help me?

Best regards
Jakub Ladman
-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] problem cross-emerging minicom

[Jakub Ladman]

Hi
Is this a reason, why i got no answer to my question, that by keywords is the 
application ebuild incompatible with my system and then it is "Off topic" 
here in gentoo embedded ml?
If yes, tell me the right place, or recommend me please any other simple 
terminal, usable to serial line communications. I do not need modem 
functions, i do not need kermit, zmodem nor any other file transfer.
I need terminal for embedded linux machine which has console on serial line 
and terminal for testing embedded modules (gprs module, gps module, bt 
module) to run inside the embedded system.
I do not want to write it, because i am sure that it must exist.
Thank you
Jakub Ladman



Dne pátek 14 červenec 2006 14:24 Jakub Ladman napsal(a):
> Hello dear friends
>
> For bebugging a serial comunication i need to build minicom terminal for my
> SH4 system.
> Ebuild has not the sh keyword and it fails even if i have copied ebuild to
> portage overlay and add the keyword.
>
> I get this error message:
>
> sh4-pc-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I..   -I../lib  -Os -pipe
> -fPIC -I../intl -Wall -W -c dial.c
> sh4-pc-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I..   -I../lib  -Os -pipe
> -fPIC -I../intl -Wall -W -c window.c
> window.c: In function `_gotoxy':
> window.c:325: error: `BC' undeclared (first use in this function)
> window.c:325: error: (Each undeclared identifier is reported only once
> window.c:325: error: for each function it appears in.)
> window.c: In function `win_init':
> window.c:1925: error: `BC' undeclared (first use in this function)
> make[2]: *** [window.o] Error 1
> make[2]: Leaving directory
> `/var/tmp/portage/minicom-2.1-r2/work/minicom-2.1/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/var/tmp/portage/minicom-2.1-r2/work/minicom-2.1' make: ***
> [all-recursive-am] Error 2
>
>
> I do not udestand the problem.
> Can you help me?
>
> Best regards
> Jakub Ladman

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] problem cross-emerging minicom

[Ned Ludd]

On Mon, 2006-07-17 at 11:18 +0200, Jakub Ladman wrote:
> Hi
> Is this a reason, why i got no answer to my question, that by keywords is the 
> application ebuild incompatible with my system and then it is "Off topic" 
> here in gentoo embedded ml?

It's semi the right place. bugs.gentoo.org is probably better.
However chances are that nobody else encountered this bug you have on 
the arch that you have and can't really comment on it.

Taking a quick peek at the code we see that BC is defined on line 
65 of src/window.c ; static char *BC, *CR, *NL;
And is not wrapped within any sort of #ifdef so you really should not be
hitting that bug unless the sh4 has problems with static char *

Anyway this is embedded and tends to require problem solving by 
all parties involved.


> If yes, tell me the right place, or recommend me please any other simple 
> terminal, usable to serial line communications. I do not need modem 
> functions, i do not need kermit, zmodem nor any other file transfer.
> I need terminal for embedded linux machine which has console on serial line 
> and terminal for testing embedded modules (gprs module, gps module, bt 
> module) to run inside the embedded system.
> I do not want to write it, because i am sure that it must exist.
> Thank you
> Jakub Ladman
> 
> 
> 
> Dne pátek 14 červenec 2006 14:24 Jakub Ladman napsal(a):
> > Hello dear friends
> >
> > For bebugging a serial comunication i need to build minicom terminal for my
> > SH4 system.
> > Ebuild has not the sh keyword and it fails even if i have copied ebuild to
> > portage overlay and add the keyword.
> >
> > I get this error message:
> >
> > sh4-pc-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I..   -I../lib  -Os -pipe
> > -fPIC -I../intl -Wall -W -c dial.c
> > sh4-pc-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I..   -I../lib  -Os -pipe
> > -fPIC -I../intl -Wall -W -c window.c
> > window.c: In function `_gotoxy':
> > window.c:325: error: `BC' undeclared (first use in this function)
> > window.c:325: error: (Each undeclared identifier is reported only once
> > window.c:325: error: for each function it appears in.)
> > window.c: In function `win_init':
> > window.c:1925: error: `BC' undeclared (first use in this function)
> > make[2]: *** [window.o] Error 1
> > make[2]: Leaving directory
> > `/var/tmp/portage/minicom-2.1-r2/work/minicom-2.1/src'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory
> > `/var/tmp/portage/minicom-2.1-r2/work/minicom-2.1' make: ***
> > [all-recursive-am] Error 2
> >
> >
> > I do not udestand the problem.
> > Can you help me?
> >
> > Best regards
> > Jakub Ladman
> 
-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] problem cross-emerging minicom

[Ned Ludd]

On Mon, 2006-07-17 at 07:32 -0400, Ned Ludd wrote:
> On Mon, 2006-07-17 at 11:18 +0200, Jakub Ladman wrote:
> > Hi
> > Is this a reason, why i got no answer to my question, that by keywords is the 
> > application ebuild incompatible with my system and then it is "Off topic" 
> > here in gentoo embedded ml?
> 
> It's semi the right place. bugs.gentoo.org is probably better.
> However chances are that nobody else encountered this bug you have on 
> the arch that you have and can't really comment on it.
> 
> Taking a quick peek at the code we see that BC is defined on line 
> 65 of src/window.c ; static char *BC, *CR, *NL;
> And is not wrapped within any sort of #ifdef so you really should not be
> hitting that bug unless the sh4 has problems with static char *
> 
> Anyway this is embedded and tends to require problem solving by 
> all parties involved.
> 

Also maybe worth noting is that ncurses provides a symbol named BC

qlist -eo ncurses | scanelf -s +BC -f - -q


> 
> > If yes, tell me the right place, or recommend me please any other simple 
> > terminal, usable to serial line communications. I do not need modem 
> > functions, i do not need kermit, zmodem nor any other file transfer.
> > I need terminal for embedded linux machine which has console on serial line 
> > and terminal for testing embedded modules (gprs module, gps module, bt 
> > module) to run inside the embedded system.
> > I do not want to write it, because i am sure that it must exist.
> > Thank you
> > Jakub Ladman
> > 
> > 
> > 
> > Dne pátek 14 červenec 2006 14:24 Jakub Ladman napsal(a):
> > > Hello dear friends
> > >
> > > For bebugging a serial comunication i need to build minicom terminal for my
> > > SH4 system.
> > > Ebuild has not the sh keyword and it fails even if i have copied ebuild to
> > > portage overlay and add the keyword.
> > >
> > > I get this error message:
> > >
> > > sh4-pc-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I..   -I../lib  -Os -pipe
> > > -fPIC -I../intl -Wall -W -c dial.c
> > > sh4-pc-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I..   -I../lib  -Os -pipe
> > > -fPIC -I../intl -Wall -W -c window.c
> > > window.c: In function `_gotoxy':
> > > window.c:325: error: `BC' undeclared (first use in this function)
> > > window.c:325: error: (Each undeclared identifier is reported only once
> > > window.c:325: error: for each function it appears in.)
> > > window.c: In function `win_init':
> > > window.c:1925: error: `BC' undeclared (first use in this function)
> > > make[2]: *** [window.o] Error 1
> > > make[2]: Leaving directory
> > > `/var/tmp/portage/minicom-2.1-r2/work/minicom-2.1/src'
> > > make[1]: *** [all-recursive] Error 1
> > > make[1]: Leaving directory
> > > `/var/tmp/portage/minicom-2.1-r2/work/minicom-2.1' make: ***
> > > [all-recursive-am] Error 2
> > >
> > >
> > > I do not udestand the problem.
> > > Can you help me?
> > >
> > > Best regards
> > > Jakub Ladman
> > 
-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] problem cross-emerging minicom

[Jakub Ladman]

Thanx for answers.
I have not qlist binary on my system, from which ebuild it comes?
Jakub Ladman
Dne pondělí 17 červenec 2006 13:35 Ned Ludd napsal(a):
> On Mon, 2006-07-17 at 07:32 -0400, Ned Ludd wrote:
> > On Mon, 2006-07-17 at 11:18 +0200, Jakub Ladman wrote:
> > > Hi
> > > Is this a reason, why i got no answer to my question, that by keywords
> > > is the application ebuild incompatible with my system and then it is
> > > "Off topic" here in gentoo embedded ml?
> >
> > It's semi the right place. bugs.gentoo.org is probably better.
> > However chances are that nobody else encountered this bug you have on
> > the arch that you have and can't really comment on it.
> >
> > Taking a quick peek at the code we see that BC is defined on line
> > 65 of src/window.c ; static char *BC, *CR, *NL;
> > And is not wrapped within any sort of #ifdef so you really should not be
> > hitting that bug unless the sh4 has problems with static char *
> >
> > Anyway this is embedded and tends to require problem solving by
> > all parties involved.
>
> Also maybe worth noting is that ncurses provides a symbol named BC
>
> qlist -eo ncurses | scanelf -s +BC -f - -q
>
> > > If yes, tell me the right place, or recommend me please any other
> > > simple terminal, usable to serial line communications. I do not need
> > > modem functions, i do not need kermit, zmodem nor any other file
> > > transfer. I need terminal for embedded linux machine which has console
> > > on serial line and terminal for testing embedded modules (gprs module,
> > > gps module, bt module) to run inside the embedded system.
> > > I do not want to write it, because i am sure that it must exist.
> > > Thank you
> > > Jakub Ladman
> > >
> > > Dne pátek 14 červenec 2006 14:24 Jakub Ladman napsal(a):
> > > > Hello dear friends
> > > >
> > > > For bebugging a serial comunication i need to build minicom terminal
> > > > for my SH4 system.
> > > > Ebuild has not the sh keyword and it fails even if i have copied
> > > > ebuild to portage overlay and add the keyword.
> > > >
> > > > I get this error message:
> > > >
> > > > sh4-pc-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I..   -I../lib  -Os
> > > > -pipe -fPIC -I../intl -Wall -W -c dial.c
> > > > sh4-pc-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I..   -I../lib  -Os
> > > > -pipe -fPIC -I../intl -Wall -W -c window.c
> > > > window.c: In function `_gotoxy':
> > > > window.c:325: error: `BC' undeclared (first use in this function)
> > > > window.c:325: error: (Each undeclared identifier is reported only
> > > > once window.c:325: error: for each function it appears in.)
> > > > window.c: In function `win_init':
> > > > window.c:1925: error: `BC' undeclared (first use in this function)
> > > > make[2]: *** [window.o] Error 1
> > > > make[2]: Leaving directory
> > > > `/var/tmp/portage/minicom-2.1-r2/work/minicom-2.1/src'
> > > > make[1]: *** [all-recursive] Error 1
> > > > make[1]: Leaving directory
> > > > `/var/tmp/portage/minicom-2.1-r2/work/minicom-2.1' make: ***
> > > > [all-recursive-am] Error 2
> > > >
> > > >
> > > > I do not udestand the problem.
> > > > Can you help me?
> > > >
> > > > Best regards
> > > > Jakub Ladman
>
> --
> Ned Ludd <solar@gentoo.org>
> Gentoo Linux

-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] problem cross-emerging minicom

[Ned Ludd]

On Mon, 2006-07-17 at 16:27 +0200, Jakub Ladman wrote:
> Thanx for answers.
> I have not qlist binary on my system, from which ebuild it comes?


http://www.gentoo.org/doc/en/portage-utils.xml


> Jakub Ladman
> Dne pondělí 17 červenec 2006 13:35 Ned Ludd napsal(a):
> > On Mon, 2006-07-17 at 07:32 -0400, Ned Ludd wrote:
> > > On Mon, 2006-07-17 at 11:18 +0200, Jakub Ladman wrote:
> > > > Hi
> > > > Is this a reason, why i got no answer to my question, that by keywords
> > > > is the application ebuild incompatible with my system and then it is
> > > > "Off topic" here in gentoo embedded ml?
> > >
> > > It's semi the right place. bugs.gentoo.org is probably better.
> > > However chances are that nobody else encountered this bug you have on
> > > the arch that you have and can't really comment on it.
> > >
> > > Taking a quick peek at the code we see that BC is defined on line
> > > 65 of src/window.c ; static char *BC, *CR, *NL;
> > > And is not wrapped within any sort of #ifdef so you really should not be
> > > hitting that bug unless the sh4 has problems with static char *
> > >
> > > Anyway this is embedded and tends to require problem solving by
> > > all parties involved.
> >
> > Also maybe worth noting is that ncurses provides a symbol named BC
> >
> > qlist -eo ncurses | scanelf -s +BC -f - -q
> >
> > > > If yes, tell me the right place, or recommend me please any other
> > > > simple terminal, usable to serial line communications. I do not need
> > > > modem functions, i do not need kermit, zmodem nor any other file
> > > > transfer. I need terminal for embedded linux machine which has console
> > > > on serial line and terminal for testing embedded modules (gprs module,
> > > > gps module, bt module) to run inside the embedded system.
> > > > I do not want to write it, because i am sure that it must exist.
> > > > Thank you
> > > > Jakub Ladman
> > > >
> > > > Dne pátek 14 červenec 2006 14:24 Jakub Ladman napsal(a):
> > > > > Hello dear friends
> > > > >
> > > > > For bebugging a serial comunication i need to build minicom terminal
> > > > > for my SH4 system.
> > > > > Ebuild has not the sh keyword and it fails even if i have copied
> > > > > ebuild to portage overlay and add the keyword.
> > > > >
> > > > > I get this error message:
> > > > >
> > > > > sh4-pc-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I..   -I../lib  -Os
> > > > > -pipe -fPIC -I../intl -Wall -W -c dial.c
> > > > > sh4-pc-linux-uclibc-gcc -DHAVE_CONFIG_H -I. -I. -I..   -I../lib  -Os
> > > > > -pipe -fPIC -I../intl -Wall -W -c window.c
> > > > > window.c: In function `_gotoxy':
> > > > > window.c:325: error: `BC' undeclared (first use in this function)
> > > > > window.c:325: error: (Each undeclared identifier is reported only
> > > > > once window.c:325: error: for each function it appears in.)
> > > > > window.c: In function `win_init':
> > > > > window.c:1925: error: `BC' undeclared (first use in this function)
> > > > > make[2]: *** [window.o] Error 1
> > > > > make[2]: Leaving directory
> > > > > `/var/tmp/portage/minicom-2.1-r2/work/minicom-2.1/src'
> > > > > make[1]: *** [all-recursive] Error 1
> > > > > make[1]: Leaving directory
> > > > > `/var/tmp/portage/minicom-2.1-r2/work/minicom-2.1' make: ***
> > > > > [all-recursive-am] Error 2
> > > > >
> > > > >
> > > > > I do not udestand the problem.
> > > > > Can you help me?
> > > > >
> > > > > Best regards
> > > > > Jakub Ladman
> >
> > --
> > Ned Ludd <solar@gentoo.org>
> > Gentoo Linux
> 
-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux

-- 
gentoo-embedded@gentoo.org mailing list

[gentoo-embedded] OT: Clock-Counter on an embedded board?

[andreas.sumper]

[-- Attachment #1: Type: text/plain, Size: 502 bytes --]

Hi List!

I know, this some kind of OT, but maybe someone here can help me out.

I am just wondering, if there is a possibility to use some sort of 
cpu-counter on an embedded board, running with linux 2.6.14?
I have a mips-architecture here and we want to figure out, which parts of 
our application need most of the time and cpu. That´s why we want to 
implement some kind of profiler, which should count the cpu-ticks.

Any help would be great!

thanks in advance!

Kind regards,
Andy

[-- Attachment #2: Type: text/html, Size: 860 bytes --]

Re: [gentoo-embedded] OT: Clock-Counter on an embedded board?

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 586 bytes --]

On Monday 17 July 2006 11:39, andreas.sumper@cnsystems.at wrote:
> I know, this some kind of OT, but maybe someone here can help me out.

again with the thread hijacking ... please write a new e-mail, dont simply 
respond to an existing one and change the subject

> I am just wondering, if there is a possibility to use some sort of
> cpu-counter on an embedded board, running with linux 2.6.14?

this is really architecture specific more than anything else ... see if your 
CPU provides any useful instructions (blackfin provides a CYCLES instruction 
for example)
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

Re: [gentoo-embedded] problem cross-emerging minicom

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 632 bytes --]

On Monday 17 July 2006 05:18, Jakub Ladman wrote:
> Is this a reason, why i got no answer to my question

maybe because no one knows ?  you cant really expect people to jump up and 
down answering your question simply because you asked something ... 
especially when it comes to embedded systems where you're more "on your own" 
than your typical linux system

that said, minicom-2.1 cross-compiles just fine over here for sh4
$ file src/minicom
src/minicom: ELF 32-bit LSB executable, Renesas SH, version 1 (SYSV), for 
GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, 
not stripped
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]