greetings,
this was originally started as;
+++ Subject: PIK microcontroller development issues From: Les hlhowell@pacbell.net To: fedora-list@redhat.com Date: Sat, 26 Dec 2009 15:33:56 -0800 Message-Id: <1261870436.14301.19.camel@localhost.localdomain +++
where in les howell had a problem with linking of libraries when using gpsim.
a suggestion was made by chitlesh
sdcc has its binaries in /usr/libexec/sdcc in order not to create conflicts with other general software.
can you create a file "/etc/profile.d/mypiklab.sh" and add the following contents #-------- export PATH=$PATH:/usr/libexec/sdcc #------
Then reboot and try piklab again. If you still have issues with it, please post an example (on FEL's mailing list) so that we can reproduce this error.
here are my results and errors are same as what les howell reported.
++++ **note** 1) there is a duplicating of "/usr/lib/alliance/man" in both "MANPATH"s 2) use of line break "" insertion
{ after adding '/etc/profile.d/mypiklab.sh' and reboot }
[root@argospappous ~]# uname -a Linux argospappous.ciee.lab 2.6.31.5-127.fc12.i686 #1 SMP \ Sat Nov 7 21:41:45 EST 2009 i686 i686 i386 GNU/Linux
[root@argospappous ~]# cat /etc/profile.d/mypiklab.sh ## fn= mypklab.sh v .2009.1229.0426 # as recommended by chitlesh
#-------- export PATH=$PATH:/usr/libexec/sdcc #------
[root@argospappous ~]# env|grep PATH MANPATH=:/usr/lib/alliance/man:/usr/local/share/man:/usr/share/man: \ /usr/lib/alliance/man:/usr/lib/alliance/man LD_LIBRARY_PATH=/usr/lib/alliance/lib PATH=/root/bin:/root/scripts:/home/users/scripts:/sbin:/usr/sbin:/bin: \ /usr/bin:/usr/X11R6/bin WINDOWPATH=7 QT_PLUGIN_PATH=/root/.kde/lib/kde4/plugins/:/usr/lib/kde4/plugins/ [root@argospappous ~]#
{ after 2nd reboot }
[geo@argospappous ~]$ env|grep PATH MANPATH=:/usr/lib/alliance/man:/usr/local/share/man:/usr/share/man: \ /usr/lib/alliance/man:/usr/lib/alliance/man LD_LIBRARY_PATH=/usr/lib/alliance/lib PATH=/home/geo-f/bin:/home/geo-f/scripts:/home/users/scripts:/bin: \ /usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin WINDOWPATH=7 QT_PLUGIN_PATH=/home/geo-f/.kde/lib/kde4/plugins/:/usr/lib/kde4/plugins/ [geo@argospappous ~]$ gpsim
gpsim - the GNUPIC simulator version: Release 0.24.0
type help for help **gpsim> SimulationMode:52 The font "Courier Roman 14" does not support all the required character \ sets for the current locale "LC_CTYPE=en_US.UTF-8;LC_NUMERIC=C; \ LC_TIME=en_US.UTF-8; LC_COLLATE=en_US.UTF-8;LC_MONETARY=en_US.UTF-8; \ LC_MESSAGES=en_US.UTF-8;LC_PAPER=en_US.UTF-8;LC_NAME=en_US.UTF-8; \ LC_ADDRESS=en_US.UTF-8;LC_TELEPHONE=en_US.UTF-8;LC_MEASUREMENT=en_US.UTF-8; \ LC_IDENTIFICATION=en_US.UTF-8" (Missing character set "ISO8859-1") (Missing character set "ISO8859-1") (Missing character set "ISO8859-2") (Missing character set "ISO8859-3") (Missing character set "ISO8859-4") (Missing character set "ISO8859-5") (Missing character set "KOI8-R") (Missing character set "ISO8859-7") (Missing character set "ISO8859-9") (Missing character set "ISO8859-13") (Missing character set "ISO8859-14") (Missing character set "ISO8859-15") (Missing character set "JISX0208.1983-0") (Missing character set "KSC5601.1987-0") (Missing character set "GB2312.1980-0") (Missing character set "JISX0201.1976-0") (Missing character set "ISO10646-1") The font "Courier Bold 14" does not support all the required character \ sets for the current locale "LC_CTYPE=en_US.UTF-8;LC_NUMERIC=C; \ LC_TIME=en_US.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=en_US.UTF-8; \ LC_MESSAGES=en_US.UTF-8;LC_PAPER=en_US.UTF-8;LC_NAME=en_US.UTF-8; \ LC_ADDRESS=en_US.UTF-8;LC_TELEPHONE=en_US.UTF-8;LC_MEASUREMENT=en_US.UTF-8; \ LC_IDENTIFICATION=en_US.UTF-8" (Missing character set "ISO8859-1") (Missing character set "ISO8859-1") (Missing character set "ISO8859-2") (Missing character set "ISO8859-3") (Missing character set "ISO8859-4") (Missing character set "ISO8859-5") (Missing character set "KOI8-R") (Missing character set "ISO8859-7") (Missing character set "ISO8859-9") (Missing character set "ISO8859-13") (Missing character set "ISO8859-14") (Missing character set "ISO8859-15") (Missing character set "JISX0208.1983-0") (Missing character set "KSC5601.1987-0") (Missing character set "GB2312.1980-0") (Missing character set "JISX0201.1976-0") (Missing character set "ISO10646-1") The font "Courier Bold 14" does not support all the required character \ sets for the current locale "LC_CTYPE=en_US.UTF-8;LC_NUMERIC=C; \ LC_TIME=en_US.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=en_US.UTF-8; \ LC_MESSAGES=en_US.UTF-8;LC_PAPER=en_US.UTF-8;LC_NAME=en_US.UTF-8; \ LC_ADDRESS=en_US.UTF-8;LC_TELEPHONE=en_US.UTF-8;LC_MEASUREMENT=en_US.UTF-8; \ LC_IDENTIFICATION=en_US.UTF-8" (Missing character set "ISO8859-1") (Missing character set "ISO8859-1") (Missing character set "ISO8859-2") (Missing character set "ISO8859-3") (Missing character set "ISO8859-4") (Missing character set "ISO8859-5") (Missing character set "KOI8-R") (Missing character set "ISO8859-7") (Missing character set "ISO8859-9") (Missing character set "ISO8859-13") (Missing character set "ISO8859-14") (Missing character set "ISO8859-15") (Missing character set "JISX0208.1983-0") (Missing character set "KSC5601.1987-0") (Missing character set "GB2312.1980-0") (Missing character set "JISX0201.1976-0") (Missing character set "ISO10646-1") FIXME gui_breadboard.cc Build Warning gp or gp->cpu == NULL in TraceWindow_update Exiting gpsim ++++
besides having a duplicating of "/usr/lib/alliance/man", which is not related, there is no path "/usr/libexec/sdcc" being added.
with out trying, i a wondering if "/usr/libexec/sdcc" should better be applied to "/etc/bashrc". or would this only effect user's path and not effect a program's path for gpsim to find it's libraries?
or, should "/usr/libexec/sdcc" "export PATH=$PATH:/usr/libexec/sdcc" be changed to;
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/libexec/sdcc export QT_PLUGIN_PATH=$QT_PLUGIN_PATH:/usr/libexec/sdcc
when les howell gets his Christmas lights down, i am sure that he will be adding to this post or starting a new post.
tia.
Hi,
--- On Tue, Dec 29, 2009 at 12:40 PM, g geleem@bellsouth.net wrote: | 1) there is a duplicating of "/usr/lib/alliance/man" in both "MANPATH"s --
Yes.
$ echo $MANPATH :/usr/lib/alliance/man:/usr/local/share/man:/usr/share/man/en:/usr/share/man:/usr/lib/alliance/man:/usr/local/man:/usr/lib/alliance/man
--- | 2) use of line break "" insertion --
Sorry, where?
--- | { after adding '/etc/profile.d/mypiklab.sh' and reboot } --
I already have /usr/libexec/sdcc in my PATH on Fedora 12.
$ echo $PATH /usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/lib/alliance/bin:/usr/libexec/sdcc:/home/shaks/bin:/usr/lib/alliance/bin:/usr/libexec/sdcc
--- | [root@argospappous ~]# uname -a | Linux argospappous.ciee.lab 2.6.31.5-127.fc12.i686 #1 SMP \ --
Same kernel here.
--- | [root@argospappous ~]# cat /etc/profile.d/mypiklab.sh | ## fn= mypklab.sh v .2009.1229.0426 | # as recommended by chitlesh | | #-------- | export PATH=$PATH:/usr/libexec/sdcc | #------ --
I didn't create this file.
--- | **gpsim> SimulationMode:52 | The font "Courier Roman 14" does not support all the required character \ | sets for the current locale "LC_CTYPE=en_US.UTF-8;LC_NUMERIC=C; \ | LC_TIME=en_US.UTF-8; LC_COLLATE=en_US.UTF-8;LC_MONETARY=en_US.UTF-8; \ | ... | (Missing character set "KSC5601.1987-0") | (Missing character set "GB2312.1980-0") | (Missing character set "JISX0201.1976-0") | (Missing character set "ISO10646-1") | FIXME gui_breadboard.cc Build | Warning gp or gp->cpu == NULL in TraceWindow_update | Exiting gpsim --
I don't get these warnings when starting gpsim on gnome-terminal:
$ rpm -qa | grep gpsim gpsim-0.24.0-1.fc12.i686
$ rpm -qa | grep gnome-terminal gnome-terminal-2.28.1-1.fc12.i686
--- | besides having a duplicating of "/usr/lib/alliance/man", which is not related, | there is no path "/usr/libexec/sdcc" being added. --
I didn't use a /etc/profile.d/mypiklab.sh file. Do you have a sample test input for gpsim, that I can use for testing?
SK
Shakthi Kannan wrote:
- there is a duplicating of "/usr/lib/alliance/man" in both "MANPATH"s
Yes.
$ echo $MANPATH
not relevant to problem. mentioned only because it is a problem with 'alliance' and a poster not using 'alliance' might comment regarding.
- use of line break "" insertion
Sorry, where?
look at my post again and you will see it in gpsim's error listing i posted. [probably not noticeable to you with your quoting.]
{ after adding '/etc/profile.d/mypiklab.sh' and reboot }
I already have /usr/libexec/sdcc in my PATH on Fedora 12.
how did "/usr/libexec/sdcc" get in your "$PATH"?
[root@argospappous ~]# uname -a Linux argospappous.ciee.lab 2.6.31.5-127.fc12.i686 #1 SMP \
Same kernel here.
then you are 2 kernel updates behind.
I didn't create this file.
how did "/usr/libexec/sdcc" get in your "$PATH"?
I don't get these warnings when starting gpsim on gnome-terminal:
because you have "/usr/libexec/sdcc" in your "$PATH".
Do you have a sample test input for gpsim, that I can use for testing?
not relevant to problem.
in addition; 1) please use "compliant email quoting" in your replies. your non-compliant "|" and "\ ---" quoting makes for garbaged replies when eliminating long line wrapping. 2) please reply only to list and not include my email address in replies.
thank you.
On Tue, Dec 29, 2009 at 10:03 AM, g <> wrote:
{ after adding '/etc/profile.d/mypiklab.sh' and reboot }
I already have /usr/libexec/sdcc in my PATH on Fedora 12.
how did "/usr/libexec/sdcc" get in your "$PATH"?
Hello there, The reason why Shakthi has /usr/libexec/sdcc in hjs PATH is certainly because he has ktechlab installed while g doesn't have ktechlab installed.
I have added /etc/profile.d/ktechlab.sh to set the sdcc path for ktechlab. If this is a "sdcc path" concern for piklab too, then the best solution in terms of default PATH setting would be to : * remove /etc/profile.d/ktechlab.sh from ktechlab * don't provide a /etc/profile.d/piklab.sh for piklab * provide a /etc/profile.d/sdcc.sh with sdcc directly.
But the issue here is rather to know why gpsim is giving character set warnings. Can you please : * create a _new_ user "test" * login into that user * post the output of $ echo $PATH * gpsim
Are you using gnome or kde ?
If you still have a problem then the fedora maintainer (who is gpsim's upstream) of gpsim should have a look at it.
Chitlesh
Chitlesh GOORAH wrote:
On Tue, Dec 29, 2009 at 10:03 AM, g <> wrote:
{ after adding '/etc/profile.d/mypiklab.sh' and reboot }
I already have /usr/libexec/sdcc in my PATH on Fedora 12.
how did "/usr/libexec/sdcc" get in your "$PATH"?
Hello there, The reason why Shakthi has /usr/libexec/sdcc in hjs PATH is certainly because he has ktechlab installed while g doesn't have ktechlab installed.
sounds 50% reasonable. g does have ktechlab installed also. see attachments: cad-eda.0011
- create a _new_ user "test"
- login into that user
- post the output of
$ echo $PATH
- gpsim
created. logged in. see attachment "path.test". same errors.
Are you using gnome or kde ?
kde. see attachment: cad-eda.0011
If you still have a problem then the fedora maintainer (who is gpsim's upstream) of gpsim should have a look at it.
sounds like he needs to have a look.
in addition:: after have run as user 'test' and looking at '.bashrc', it hit me as to why i may not have additional directories in my $PATH.
when i logged back in as my normal user, i checked my '.bashrc' and found at some time in past years of using same '.bashrc' and making mods and additions, somehow or what ever, "PATH=$PATH:custom/paths" got changed to "PATH=custom/paths".
i inserted "$PATH:" back in, logged out, logged back in, "env|grep PATH" to insure that default "$PATH" was there and it was. see attachment "newpath.geo.0001"
started 'kde', opened a terminal window and entered "gpsim<cr>".
failed with same libraries missing as reported in 1st post of this thread.
so, where/who to now?
electronic-lab@lists.fedoraproject.org