tilp-devel — This list is intended to TiLP's developers, contributors and advanced users.

[TiLP-devel] Compiling Tilp on OSX

[John S. <mi...@ya...>]

I've been working on compiling TiLP on OSX.  It almost
compiles by setting CFLAGS='-D __MACOSX__' (isn't
there a way to get configure to set that
automatically?).  However, I get an error compiling
timodules.c:

 gcc -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\"
-I. -I. -I.. -I.. -I/usr/include -I../intl -I../intl
-DPREFIX=\"/usr\" -I. -D__MACOSX__ -Wall -D_REENTRANT
-MT timodules.lo -MD -MP -MF .deps/timodules.Tpo -c
timodules.c  -fno-common -DPIC -o .libs/timodules.o
timodules.c:24:17: io.h: No such file or directory

The error is removed by adding " ||
defined(__MACOSX__)" to the end of line 21.  Can you
make that change, or do I need to submit a patch sumewhere?

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

Re: [TiLP-devel] Compiling TiLP Libraries on OS X

[Tijl C. <ti...@ul...>]

On Wed, 22 Oct 2003 17:55:04 -0500, Stephen Mitchell wrote:

> I need to compile TiLP so I can use the libraries for a project I'm 
> working on.  However, I've got some compile errors.
> 
> libtifiles builds fine.  When I compile libiticables, I get this
> error:

You need to define __MACOSX__ during build. That counts for all other
libs and tilp itself too btw.

[TiLP-devel] Compiling TiLP Libraries on OS X

[Stephen M. <ste...@le...>]

I need to compile TiLP so I can use the libraries for a project I'm 
working on.  However, I've got some compile errors.

libtifiles builds fine.  When I compile libiticables, I get this error:

---------------------------
  gcc -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I. -I. -I.. 
-I.. -I/usr/include -I../intl -I../intl -DPREFIX=\"/usr\" -I. -g -O2 
-Wall -D_REENTRANT -MT tig_link.lo -MD -MP -MF .deps/tig_link.Tpo -c 
tig_link.c  -fno-common -DPIC -o .libs/tig_link.o
tig_link.c:530: error: parse error before "data"
tig_link.c:535: error: parse error before '*' token
tig_link.c: In function `tig_supported':
tig_link.c:584: error: `SUPPORT_OFF' undeclared (first use in this 
function)
tig_link.c:584: error: (Each undeclared identifier is reported only once
tig_link.c:584: error: for each function it appears in.)
make[2]: *** [tig_link.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
scum@scum libticables-3.7.7 $
---------------------------

It seems to be redeclaring a function (?).  Is there another version of 
the source that compiles for OS X?

Thanks,
Stephen

P.S. Is the mailing list broken?  I can't get subscribed to it (I never 
the the subscription confirmation email), and the Archives give an 
error when I try to view them on the web.

[TiLP-devel] Re: Compiling TiLP on Win32

[John S. <mi...@ya...>]

Ok.. I need to compile it, cause I need to link a
python module I'm writing against it.

I got MinGW, but I have run into some errors compiling
libticables.  First, it throws an error about
LOCALEDIR (line 87 in intrface.c).  I think it's a
defined variable (from the gcc command line options). 
By commenting out line 87, it compiles, but I don't
know if that's introducing all sorts of bugs.

After that, it builds, but I get these errors about
gettext.  I believe I have it installed, but I'm not
sure if it needs a gcc command line option to link
against it or something.

Thanks for any help!

John

-------------------------------------

Creating library file: .libs/libticables.dll.a
.libs/ioports.o(.text+0x2f8): In function `io_open':
c:/legalstuff/2/libticables-3.7.7/src/ioports.c:402:
undefined reference to `dgettext'
.libs/slv_link.o(.text+0x31e): In function `slv_init':
c:/legalstuff/2/libticables-3.7.7/src/slv_link.c:338:
undefined reference to `dgettext'
.libs/slv_link.o(.text+0x397):c:/legalstuff/2/libticables-3.7.7/src/slv_link.c:360:
undefined reference to `dgettext'
.libs/slv_link.o(.text+0x4dc):c:/legalstuff/2/libticables-3.7.7/src/slv_link.c:348:
undefined reference to `dgettext'
.libs/tie_link.o(.text+0x51e): In function `tie_init':
c:/legalstuff/2/libticables-3.7.7/src/tie_link.c:299:
undefined reference to `dgettext'
.libs/vti_link.o(.text+0x1a1):c:/legalstuff/2/libticables-3.7.7/src/vti_link.c:364:
more undefined references to `dgettext' follow
.libs/intrface.o(.text+0xda): In function
`ticable_init':
c:/legalstuff/2/libticables-3.7.7/src/intrface.c:103:
undefined reference to `bindtextdomain'
.libs/intrface.o(.text+0xfb):c:/legalstuff/2/libticables-3.7.7/src/intrface.c:106:
undefined reference to `textdomain'
.libs/intrface.o(.text+0x10f):c:/legalstuff/2/libticables-3.7.7/src/intrface.c:108:
undefined reference to `dgettext'
.libs/intrface.o(.text+0x978): In function
`ticable_set_cable':
c:/legalstuff/2/libticables-3.7.7/src/intrface.c:592:
undefined reference to `dgettext'
.libs/intrface.o(.text+0x98f):c:/legalstuff/2/libticables-3.7.7/src/intrface.c:594:
undefined reference to `dgettext'
.libs/intrface.o(.text+0x9a7):c:/legalstuff/2/libticables-3.7.7/src/intrface.c:595:
undefined reference to `dgettext'
.libs/intrface.o(.text+0x9be):c:/legalstuff/2/libticables-3.7.7/src/intrface.c:596:
undefined reference to `dgettext'
.libs/intrface.o(.text+0xac3):c:/legalstuff/2/libticables-3.7.7/src/intrface.c:660:
more undefined references to `dgettext' follow
.libs/probe.o(.text+0x19c2): In function
`probe_io_resources':
c:/legalstuff/2/libticables-3.7.7/src/probe.c:1096:
undefined reference to `StartPortTalkDriver'
.libs/timodules.o(.text+0x23a): In function
`search_for_tiusb_node':
c:/legalstuff/2/libticables-3.7.7/src/timodules.c:72:
undefined reference to `dgettext'
.libs/timodules.o(.text+0x29c): In function
`search_for_tipar_node':
c:/legalstuff/2/libticables-3.7.7/src/timodules.c:89:
undefined reference to `dgettext'
.libs/timodules.o(.text+0x2fe): In function
`search_for_tiser_node':
c:/legalstuff/2/libticables-3.7.7/src/timodules.c:106:
undefined reference to `dgettext'
make[2]: *** [libticables.la] Error 1
make[2]: Leaving directory
`/c/legalstuff/2/libticables-3.7.7/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/c/legalstuff/2/libticables-3.7.7'
make: *** [all] Error 2

--- Romain LIEVIN <rom...@wa...> wrote:
> Hi,
> 
> John Spiegel a écrit :
> > I'm having problems getting tilp compiled on
> windows. 
> > It keeps looking for "inttypes.h".  I'm not sure
> what
> > provides that for windows.  Any help would be
> > appreciated.
> 
> If you want to compile TiLP on Windows, you should
> not use the TiLP SDK. The SDK is provided for
> building apps against libs.
> 
> The best thing to do: retrieve source code of 3 libs
> and TiLP. Uncompress them and rebuild. But, do you
> really want to do that  ? It may be a bit tedious...
> 
> > 
> > JOhn
> > 
> > -----------------------------------------
> > Compiling...
> > Avr_link.c
> > c:\program
> files\tilp-sdk\cables\src\cabl_def.h(30) :
> > fatal error C1083:
> > Cannot open include file: 'inttypes.h': No such
> file
> > or directory
> > Dev_link.c
> > c:\program
> files\tilp-sdk\cables\src\cabl_def.h(30) :
> > fatal error C1083:
> > Cannot open include file: 'inttypes.h': No such
> file
> > or directory
> > dfl_link.c
> > c:\program
> files\tilp-sdk\cables\src\dfl_link.c(30) :
> > fatal error C1083:
> > Cannot open include file: 'inttypes.h': No such
> file
> > or directory
> > Par_link.c
> > c:\program
> files\tilp-sdk\cables\src\par_link.c(30) :
> > fatal error C1083:
> > Cannot open include file: 'inttypes.h': No such
> file
> > or directory
> > Ser_link.c
> > c:\program
> files\tilp-sdk\cables\src\cabl_def.h(30) :
> > fatal error C1083:
> > Cannot open include file: 'inttypes.h': No such
> file
> > or directory
> > slv_link.c
> > c:\program files\tilp-sdk\cables\src\intl.h(37) :
> > fatal error C1083: Cannot
> > open include file: 'libintl.h': No such file or
> > directory
> > Tie_link.c
> > c:\program files\tilp-sdk\cables\src\intl.h(37) :
> > fatal error C1083: Cannot
> > open include file: 'libintl.h': No such file or
> > directory
> > Tig_link.c
> > c:\program
> files\tilp-sdk\cables\src\cabl_def.h(30) :
> > fatal error C1083:
> > Cannot open include file: 'inttypes.h': No such
> file
> > or directory
> > Vti_link.c
> > c:\program files\tilp-sdk\cables\src\intl.h(37) :
> > fatal error C1083: Cannot
> > open include file: 'libintl.h': No such file or
> > directory
> > Vtl_link.c
> > c:\program
> files\tilp-sdk\cables\src\cabl_def.h(30) :
> > fatal error C1083:
> > Cannot open include file: 'inttypes.h': No such
> file
> > or directory
> > Error.c
> > c:\program files\tilp-sdk\cables\src\intl.h(37) :
> > fatal error C1083: Cannot
> > open include file: 'libintl.h': No such file or
> > directory
> > Intrface.c
> > c:\program files\tilp-sdk\cables\src\intl.h(37) :
> > fatal error C1083: Cannot
> > open include file: 'libintl.h': No such file or
> > directory
> > Ioports.c
> > c:\program
> files\tilp-sdk\cables\src\cabl_def.h(30) :
> > fatal error C1083:
> > Cannot open include file: 'inttypes.h': No such
> file
> > or directory
> > Logging.c
> > c:\program files\tilp-sdk\cables\src\intl.h(37) :
> > fatal error C1083: Cannot
> > open include file: 'libintl.h': No such file or
> > directory
> > porttalk.c
> > c:\program
> files\tilp-sdk\cables\src\cabl_def.h(30) :
> > fatal error C1083:
> > Cannot open include file: 'inttypes.h': No such
> file
> > or directory
> > Probe.c
> > c:\program files\tilp-sdk\cables\src\probe.c(38) :
> > fatal error C1083: Cannot
> > open include file: 'inttypes.h': No such file or
> > directory
> > timodules.c
> > c:\program files\tilp-sdk\cables\src\intl.h(37) :
> > fatal error C1083: Cannot
> > open include file: 'libintl.h': No such file or
> > directory
> > type2str.c
> > c:\program files\tilp-sdk\cables\src\intl.h(37) :
> > fatal error C1083: Cannot
> > open include file: 'libintl.h': No such file or
> > directory
> > verbose.c
> > c:\program
> files\tilp-sdk\cables\src\cabl_def.h(30) :
> > fatal error C1083:
> > Cannot open include file: 'inttypes.h': No such
> file
> > or directory
> > Error executing cl.exe.
> > 
> > ticables.dll - 19 error(s), 0 warning(s) 
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > The New Yahoo! Shopping - with improved product
> search
> > http://shopping.yahoo.com
> > 
> > 
> >
>
-------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback
> Program.
> > SourceForge.net hosts over 70,000 Open Source
> Projects.
> > See the people who have HELPED US provide better
> services:
> > Click here: http://sourceforge.net/supporters.php
> > _______________________________________________
> > TiLP-devel mailing list
> > TiL...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/tilp-devel
> > 
> 
> 
> -- 
> Romain Liévin, aka 'roms'  	<ro...@ti...>
> Site web 			<http://tilp.info>
> Messagerie instantanée (ICQ)    43585029
> "Linux, y'a moins bien mais c'est plus cher !"
> 
> 


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

[TiLP-devel] (no subject)

[Romain L. <rom...@wa...>]

Hi,

James Supancic a =E9crit :
> Im sorry for taking your time. If you are bussy dont bother replying.
> else
> {
> I need help. I want to use tilp on a Sharp Zaurus SL-C760. I want to=20
> cross compile. I run Qtopia on my Zaurus not X11. So ill need to compile=
=20
> with no GUI and for a Zaurus. I wont be able to use the install script.=
=20
> Im sure that you are more fermiler with tilp and its build/install=20
> presedure. I couldnt find the Makefile. Also, 3 libs are required. Are=20
> these dynamic libs or Do I have to build them first and then build tilp=
=20
> with them?

You will have to build the 3 libs at first and build tilp next. But, TiLP d=
epends on GTK even if you just want to use the command line (no GUI). There=
 is currenty no other way.

> }
> Thank you for you time,
> Arrummzen
>=20

roms

> _________________________________________________________________
> Send instant messages to anyone on your contact list with  MSN Messenger=
=20
> 6.0.  Try it now FREE!  http://msnmessenger-download.com
>=20
>=20

---
Romain Li=E9vin  =09                          <ro...@ti...>
Site web =09                             <http://rlievin.dyndns.org>
Messagerie instantan=E9e (ICQ)    43585029
"Linux, y'a moins bien mais c'est plus cher !"

[TiLP-devel] Compiling TiLP on Win32

[Romain L. <rom...@wa...>]

Hi,

John Spiegel a =E9crit :
> I'm having problems getting tilp compiled on windows.=20
> It keeps looking for "inttypes.h".  I'm not sure what
> provides that for windows.  Any help would be
> appreciated.

If you want to compile TiLP on Windows, you should not use the TiLP SDK. Th=
e SDK is provided for building apps against libs.

The best thing to do: retrieve source code of 3 libs and TiLP. Uncompress t=
hem and rebuild. But, do you really want to do that  ? It may be a bit tedi=
ous...

>=20
> JOhn
>=20
> -----------------------------------------
> Compiling...
> Avr_link.c
> c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
> fatal error C1083:
> Cannot open include file: 'inttypes.h': No such file
> or directory
> Dev_link.c
> c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
> fatal error C1083:
> Cannot open include file: 'inttypes.h': No such file
> or directory
> dfl_link.c
> c:\program files\tilp-sdk\cables\src\dfl_link.c(30) :
> fatal error C1083:
> Cannot open include file: 'inttypes.h': No such file
> or directory
> Par_link.c
> c:\program files\tilp-sdk\cables\src\par_link.c(30) :
> fatal error C1083:
> Cannot open include file: 'inttypes.h': No such file
> or directory
> Ser_link.c
> c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
> fatal error C1083:
> Cannot open include file: 'inttypes.h': No such file
> or directory
> slv_link.c
> c:\program files\tilp-sdk\cables\src\intl.h(37) :
> fatal error C1083: Cannot
> open include file: 'libintl.h': No such file or
> directory
> Tie_link.c
> c:\program files\tilp-sdk\cables\src\intl.h(37) :
> fatal error C1083: Cannot
> open include file: 'libintl.h': No such file or
> directory
> Tig_link.c
> c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
> fatal error C1083:
> Cannot open include file: 'inttypes.h': No such file
> or directory
> Vti_link.c
> c:\program files\tilp-sdk\cables\src\intl.h(37) :
> fatal error C1083: Cannot
> open include file: 'libintl.h': No such file or
> directory
> Vtl_link.c
> c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
> fatal error C1083:
> Cannot open include file: 'inttypes.h': No such file
> or directory
> Error.c
> c:\program files\tilp-sdk\cables\src\intl.h(37) :
> fatal error C1083: Cannot
> open include file: 'libintl.h': No such file or
> directory
> Intrface.c
> c:\program files\tilp-sdk\cables\src\intl.h(37) :
> fatal error C1083: Cannot
> open include file: 'libintl.h': No such file or
> directory
> Ioports.c
> c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
> fatal error C1083:
> Cannot open include file: 'inttypes.h': No such file
> or directory
> Logging.c
> c:\program files\tilp-sdk\cables\src\intl.h(37) :
> fatal error C1083: Cannot
> open include file: 'libintl.h': No such file or
> directory
> porttalk.c
> c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
> fatal error C1083:
> Cannot open include file: 'inttypes.h': No such file
> or directory
> Probe.c
> c:\program files\tilp-sdk\cables\src\probe.c(38) :
> fatal error C1083: Cannot
> open include file: 'inttypes.h': No such file or
> directory
> timodules.c
> c:\program files\tilp-sdk\cables\src\intl.h(37) :
> fatal error C1083: Cannot
> open include file: 'libintl.h': No such file or
> directory
> type2str.c
> c:\program files\tilp-sdk\cables\src\intl.h(37) :
> fatal error C1083: Cannot
> open include file: 'libintl.h': No such file or
> directory
> verbose.c
> c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
> fatal error C1083:
> Cannot open include file: 'inttypes.h': No such file
> or directory
> Error executing cl.exe.
>=20
> ticables.dll - 19 error(s), 0 warning(s)=20
>=20
>=20
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> TiLP-devel mailing list
> TiL...@li...
> https://lists.sourceforge.net/lists/listinfo/tilp-devel
>=20


--=20
Romain Li=E9vin, aka 'roms'  =09<ro...@ti...>
Site web =09=09=09<http://tilp.info>
Messagerie instantan=E9e (ICQ)    43585029
"Linux, y'a moins bien mais c'est plus cher !"

[TiLP-devel] Compiling Tilp

[John S. <mi...@ya...>]

I'm having problems getting tilp compiled on windows. 
It keeps looking for "inttypes.h".  I'm not sure what
provides that for windows.  Any help would be
appreciated.

JOhn

-----------------------------------------
Compiling...
Avr_link.c
c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
fatal error C1083:
Cannot open include file: 'inttypes.h': No such file
or directory
Dev_link.c
c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
fatal error C1083:
Cannot open include file: 'inttypes.h': No such file
or directory
dfl_link.c
c:\program files\tilp-sdk\cables\src\dfl_link.c(30) :
fatal error C1083:
Cannot open include file: 'inttypes.h': No such file
or directory
Par_link.c
c:\program files\tilp-sdk\cables\src\par_link.c(30) :
fatal error C1083:
Cannot open include file: 'inttypes.h': No such file
or directory
Ser_link.c
c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
fatal error C1083:
Cannot open include file: 'inttypes.h': No such file
or directory
slv_link.c
c:\program files\tilp-sdk\cables\src\intl.h(37) :
fatal error C1083: Cannot
open include file: 'libintl.h': No such file or
directory
Tie_link.c
c:\program files\tilp-sdk\cables\src\intl.h(37) :
fatal error C1083: Cannot
open include file: 'libintl.h': No such file or
directory
Tig_link.c
c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
fatal error C1083:
Cannot open include file: 'inttypes.h': No such file
or directory
Vti_link.c
c:\program files\tilp-sdk\cables\src\intl.h(37) :
fatal error C1083: Cannot
open include file: 'libintl.h': No such file or
directory
Vtl_link.c
c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
fatal error C1083:
Cannot open include file: 'inttypes.h': No such file
or directory
Error.c
c:\program files\tilp-sdk\cables\src\intl.h(37) :
fatal error C1083: Cannot
open include file: 'libintl.h': No such file or
directory
Intrface.c
c:\program files\tilp-sdk\cables\src\intl.h(37) :
fatal error C1083: Cannot
open include file: 'libintl.h': No such file or
directory
Ioports.c
c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
fatal error C1083:
Cannot open include file: 'inttypes.h': No such file
or directory
Logging.c
c:\program files\tilp-sdk\cables\src\intl.h(37) :
fatal error C1083: Cannot
open include file: 'libintl.h': No such file or
directory
porttalk.c
c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
fatal error C1083:
Cannot open include file: 'inttypes.h': No such file
or directory
Probe.c
c:\program files\tilp-sdk\cables\src\probe.c(38) :
fatal error C1083: Cannot
open include file: 'inttypes.h': No such file or
directory
timodules.c
c:\program files\tilp-sdk\cables\src\intl.h(37) :
fatal error C1083: Cannot
open include file: 'libintl.h': No such file or
directory
type2str.c
c:\program files\tilp-sdk\cables\src\intl.h(37) :
fatal error C1083: Cannot
open include file: 'libintl.h': No such file or
directory
verbose.c
c:\program files\tilp-sdk\cables\src\cabl_def.h(30) :
fatal error C1083:
Cannot open include file: 'inttypes.h': No such file
or directory
Error executing cl.exe.

ticables.dll - 19 error(s), 0 warning(s) 


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

[TiLP-devel] Re: TiLP Libraries for Visual Basic

[Romain L. <rom...@wa...>]

Hi,

Shaun Wendland a écrit :
> Greetings Romain,
> 
>       I am currently developing a Visual Basic program for programming 
> and transfer to TI calculators and was searching through the Internet on 
> TI calculator communication when I came across your site. I was set to 
> do all the development myself and was merely looking for a push in the 
> right direction, but as you seem to have a pretty incredible 
> understanding of how the TI's communicate and your site does say to 
> email you about specific builds, I would like to request a version of 
> your cable, calc, and file libraries that I can use with my Visual Basic 
> program. Obviously, you will be given full credit for your contribution 
> under the GPL and, as this will be mostly for personal use (and possibly 
> posted for free download on ticalc.org),  there will be no other legal 
> aspects as far as financial compensation. Many thanks for your time and 
> consideration in advance!

Visual Basic bindings have never been completed because I had not enough 
knowledges about VB. There is currently just 1 binding: the libticables 
one and it is in alpha stage.

I made several attempts to adapt my libs but they were unsuccessful.

I'm sorry for you !

> 
>       Sincerely,
>          Shaun Wendland
> 
> _________________________________________________________________
> Share your photos without swamping your Inbox.  Get Hotmail Extra 
> Storage today! http://join.msn.com/?PAGE=features/es
> 
> 

Romain.
-- 
Romain Liévin, aka 'roms'  	<ro...@ti...>
Site web 			<http://tilp.info>
Messagerie instantanée (ICQ)    43585029
"Linux, y'a moins bien mais c'est plus cher !"

Re: [TiLP-devel] Re: FreeBSD 5.1-C and TI V200

[Tijl C. <ti...@ul...>]

On Wed, 24 Sep 2003 08:28:32 +0200 (CEST), Romain LIEVIN wrote:

> > Error: usb_resetep: usb_clear_halt called, unimplemented on BSD
> > Error: usb_resetep: usb_resetep called, unimplemented on BSD
> > Error: usb_reset: usb_reset called, unimplemented on BSD
> 
> Argh, some important functions seem to be unimplemented on BSD...
> There are 2 ways: use a libusb which implement this call (but they
> seem to be BSD specific) or port the SilverLink kernel module to the
> BSD platform...

Is there a reason why usb_clear_halt is called? Do the endpoints have to
be reset?

Re: [TiLP-devel] FreeBSD 5.1-C and TI V200

[Tijl C. <ti...@ul...>]

On Wed, 24 Sep 2003 08:28:32 +0200 (CEST), Romain LIEVIN wrote:

> De : Pierrick Brossin <pbr...@sw...>
> 
> > and on the command line I can read:
> > 
> > --
> > Is calculator ready ?
> > Error: usb_resetep: usb_clear_halt called, unimplemented on BSD
> > Error: usb_resetep: usb_resetep called, unimplemented on BSD
> > Error: usb_reset: usb_reset called, unimplemented on BSD
> > --
> 
> Argh, some important functions seem to be unimplemented on BSD...

This is what I feared. The description for the libusb port says:

``The FreeBSD port [...] should still be considered "beta" (not all
calls implemented in the Linux port are available).''

> There are 2 ways: use a libusb which implement this call (but they
> seem to be BSD specific) or port the SilverLink kernel module to the
> BSD platform...

I'll look into fixing libusb first, but I can't give you a date on when
it'll be ready.

> > Here is the final point. Am I missing an option in the kernel or is
> > there an issue with the USB link with TiLP.

Unfortunately you can't do anything right now to get your cable working
under FreeBSD. I'll let you know when I have something. Hopefully that
won't take too long.

[TiLP-devel] Re: FreeBSD 5.1-C and TI V200

[Romain L. <rom...@wa...>]

Hi,

> Message du 23/09/03 21:35
> De : Pierrick Brossin <pbr...@sw...>
> A : ro...@ti...
> Copie =E0 :=20
> Objet : FreeBSD 5.1-C and TI V200
> Hi!
>=20
> I saw on your site you've done a huge work on the software. I want to
> first thank you. Me and other people (I hope) always appreciate when
> some skilled guys create programs to make more and more devices work
> under Linux/Unix. Windows is such a pain that I don't even use it
> anymore :)
>=20
> OK so here is the point, I'm using FreeBSD 5.1-C and I'm trying to use
> TiLP to connect my V200 through a USB link.
>=20
> I'm not asking my question on the mailing list because I guess it's more
> a bug or a kernel option missing than anything else. I'd be proud to

ok, but by using the tilp-devel mailing list, Tijl Coosemans (FreeBSD porte=
r) whould have got your mail. That's OK, I CC'ized it...

> help you to make it work under BSD (I mean the USB link).
> Maybe I didn't know how to make it work but here is what I've done:
>=20
> Connected the USB link to the computer (USB port #1).
> syslogd reports something has been connected as this:
>=20
> --
> Sep 23 21:21:38 beer kernel: ugen0: Texas Instruments TI-GRAPH LINK USB,
> rev 1.10/2.08, addr 2

good...

> --
>=20
> Now I ran TiLP as a normal user using sudo (to make sure they are no
> permission issues).
>=20
> --
> Sep 23 21:21:50 beer sudo:    dynek : TTY=3Dttyp2 ; PWD=3D/usr/home/dynek=
 ;
> USER=3Droot ; COMMAND=3D/usr/X11R6/bin/tilp
> --
>=20
> I setup (setup->communication) TiLP so it uses "USB TIGraphLink" as link
> then, I have no other choise then "USB port #1" for the communication
> port.
> In the "Calculator" tab I choose the V200 option and then I push OK
>=20
> On the command line I can read the following:
>=20
> --
> Libticables: current settings...
>   Link cable: SilverLink
>   Port: USB port #1
>   Method: automatic (direct access thru API)
>   Timeout value: 15
>   Delay value: 10
>   Baud-rate: 9600
>   Hardware flow control: on
>   I/O address: 0x2f8
>   Device name: none
> Libtifiles settings...
>   Calc type: V200
> Libticalcs settings...
>   Calc type: V200
> TIGL-USB found with libusb.

very good....

> --
>=20
> Unfortunately at the bottom of the window I can read "Status: not
> connected."

This change when you attempt an operation (such as Ready) with success. It =
has nothing to do with (un)plugging the cable.

> I thought I didn't plug the USB link in the right port so I tried all
> the other USB ports I have on the mobo but it wouldn't work either.
>=20
> When I try to list the directories I get:
>=20
> --
> Msg: Error while reseting USB endpoints.
> Cause: Your cable may be stalled. Unplug and replug it !.
> --
>=20
> and on the command line I can read:
>=20
> --
> Is calculator ready ?
> Error: usb_resetep: usb_clear_halt called, unimplemented on BSD
> Error: usb_resetep: usb_resetep called, unimplemented on BSD
> Error: usb_reset: usb_reset called, unimplemented on BSD

Argh, some important functions seem to be unimplemented on BSD...
There are 2 ways: use a libusb which implement this call (but they seem to =
be BSD specific) or port the SilverLink kernel module to the BSD platform..=
.

> --
>=20
> Here is the final point. Am I missing an option in the kernel or is
> there an issue with the USB link with TiLP.

Unfortunately, there is an issue with USB management under BSD

>=20
> Remember I'm there if you want to make tests!
>=20
> Regards
>=20
> --=20
> Pierrick Brossin <pbrossin .at. swissgeeks .dot. com>
> < http://www.swissgeeks.com >
> perl -e\
> 'print $i=3Dpack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
>=20

Regards, Romain
---
Romain Li=E9vin, aka 'roms'  =09    <ro...@ti...>
Site web =09=09=09             <http://tilp.info>
Messagerie instantan=E9e (ICQ)    43585029
"Linux, y'a moins bien mais c'est plus cher !"

Re: [TiLP-devel] grey link cable trouble

[Romain L. <rom...@wa...>]

Hi,

Tijl Coosemans a écrit :
> I found what the problem was, but I haven't solved it (yet).
> 
> The problem shows up when libxml2 is compiled with threads enabled. In
> Linux that means it is linked against libpthread(?), but in FreeBSD you
> have to add the -pthread flag to gcc so it will link against libc_r
> instead of libc (libc_r is the reentrant version of libc).
> 
> Because tilp depends on libxml2 (through libglade2), it is linked
> against libc_r too, which seems to give problems.

It's nasty...

> 
> Anybody an idea to solve this? Perhaps I should ask some freebsd
> hackers, because this is way over the top of my head...

Yes, I think.

> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> TiLP-devel mailing list
> TiL...@li...
> https://lists.sourceforge.net/lists/listinfo/tilp-devel
> 

roms
-- 
Romain Liévin, aka 'roms'  	<ro...@ti...>
Site web 			<http://tilp.info>
Messagerie instantanée (ICQ)    43585029
"Linux, y'a moins bien mais c'est plus cher !"

Re: [TiLP-devel] grey link cable trouble

[Tijl C. <ti...@ul...>]

I found what the problem was, but I haven't solved it (yet).

The problem shows up when libxml2 is compiled with threads enabled. In
Linux that means it is linked against libpthread(?), but in FreeBSD you
have to add the -pthread flag to gcc so it will link against libc_r
instead of libc (libc_r is the reentrant version of libc).

Because tilp depends on libxml2 (through libglade2), it is linked
against libc_r too, which seems to give problems.

Anybody an idea to solve this? Perhaps I should ask some freebsd
hackers, because this is way over the top of my head...

Re: [TiLP-devel] grey link cable trouble

[Tijl C. <ti...@ul...>]

On Thu, 18 Sep 2003 20:46:24 +0200, Romain Lievin wrote:

> > I got it working again, but I don't have a nice solution yet. What I
> > did is setting VMIN=1 en VTIME=0 in tig_open() in libticables, so it
> > waits indefinitely for a byte to read. VMIN=0 and VTIME=15 (normal
> > values) doesn't work and gives a timeout error almost immediately as
> > in, it doesn't wait 1,5 seconds. The strange thing is that the
> > gtk1version still works flawlessly without any of these
> > modifications. What's going on here? Are Linux versions affected
> > too?
> 
> Could you see whether the timeout value is passed fine to the lib. It 
> may explain your problem...

No problem there. Hardcoding the timeout value into the lib gives the
same problem, even if I set it to 50, "read" returns immediately with no
bytes read and thus giving a time out error. Does that mean it reads an
EOF?

> BTW, are you 'root' ?

yes.

Re: [TiLP-devel] grey link cable trouble

[Romain L. <rom...@wa...>]

Hi,

Tijl Coosemans a écrit :
> On Tue, 16 Sep 2003 18:13:36 +0200, Tijl Coosemans wrote:
> 
> 
>>I've ran into a problem with the grey serial cable on FreeBSD.
>>Apparently it got introduced with the switch to gtk2, because if I run
>>the latest versions (cables 3.7.7, files 0.5.7, calcs 4.4.7-4.5.1)
>>there's no problem in gtk12 mode (with tilp 6.09), but there is in the
>>gtk2 version (with tilp 6.52-6.68).
>>
>>Because there's no difference between the glib12 and glib2
>>versions of lcalcs, it appears to be with tilp itself. However, I
>>don't know the code that good and a lot has changed between 6.09 and
>>6.52, so does anybody have an idea what might be the problem?
>>
>>A little bit more in detail, most of the time I get a timeout error
>>while it's receiving the first byte, so sending seems to work and the
>>calc also turns on. Very rarely it all does work properly, but I
>>haven't found a way to reproduce that.
>>
>>Any clue?
>>
>>btw, who owns the project now roms left?
> 
> 
> I got it working again, but I don't have a nice solution yet. What I did
> is setting VMIN=1 en VTIME=0 in tig_open() in libticables, so it waits
> indefinitely for a byte to read. VMIN=0 and VTIME=15 (normal values)
> doesn't work and gives a timeout error almost immediately as in, it
> doesn't wait 1,5 seconds. The strange thing is that the gtk1version
> still works flawlessly without any of these modifications.
> What's going on here? Are Linux versions affected too?

Could you see whether the timeout value is passed fine to the lib. It 
may explain your problem... BTW, are you 'root' ?

> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> TiLP-devel mailing list
> TiL...@li...
> https://lists.sourceforge.net/lists/listinfo/tilp-devel
> 

roms.
-- 
Romain Liévin, aka 'roms'  	<ro...@ti...>
Site web 			<http://tilp.info>
Messagerie instantanée (ICQ)    43585029
"Linux, y'a moins bien mais c'est plus cher !"

Re: [TiLP-devel] grey link cable trouble

[Romain L. <rom...@wa...>]

Hi,

Tijl Coosemans a écrit :
> On Wed, 17 Sep 2003 19:56:28 +0200, Romain Lievin wrote:
> 
> 
>>Hi Tijl and mailing list users,
>>
>>Tijl Coosemans a écrit :
>>
>>>I've ran into a problem with the grey serial cable on FreeBSD.
>>>Apparently it got introduced with the switch to gtk2, because if I
>>>run the latest versions (cables 3.7.7, files 0.5.7, calcs
>>>4.4.7-4.5.1) there's no problem in gtk12 mode (with tilp 6.09), but
>>>there is in the gtk2 version (with tilp 6.52-6.68).
>>>
>>>Because there's no difference between the glib12 and glib2
>>>versions of lcalcs, it appears to be with tilp itself. However, I
>>>don't know the code that good and a lot has changed between 6.09 and
>>>6.52, so does anybody have an idea what might be the problem?
>>
>>If I remember well, I didn't modified libs when switching to GTK2 but
>>I may have done some (or too many ?) clean-up...
> 
> 
> I've made diffs from each version to the next and couldn't find
> anything. The fact that these libs work with TiLP 6.09 also confirms

Hmmm... Very strange ! Are you sure that tig_link.c support has not been 
modified ?

> this. This all points to TiLP itself, but if I'm correct TiLP doesn't
> really do any "low level" stuff. It only passes options and commands on

No, it doesn't.

> to the libs and that all seems to work ok.
> 
> I've also added some debugging info and checked that the cable gets
> inited/opened/closed/exited properly and no problems there either.
> 
> I'm running out of ideas, but I'll keep trying...
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> TiLP-devel mailing list
> TiL...@li...
> https://lists.sourceforge.net/lists/listinfo/tilp-devel
> 

roms.
-- 
Romain Liévin, aka 'roms'  	<ro...@ti...>
Site web 			<http://tilp.info>
Messagerie instantanée (ICQ)    43585029
"Linux, y'a moins bien mais c'est plus cher !"

Re: [TiLP-devel] grey link cable trouble

[Tijl C. <ti...@ul...>]

On Wed, 17 Sep 2003 19:56:28 +0200, Romain Lievin wrote:

> Hi Tijl and mailing list users,
>=20
> Tijl Coosemans a =E9crit :
> > I've ran into a problem with the grey serial cable on FreeBSD.
> > Apparently it got introduced with the switch to gtk2, because if I
> > run the latest versions (cables 3.7.7, files 0.5.7, calcs
> > 4.4.7-4.5.1) there's no problem in gtk12 mode (with tilp 6.09), but
> > there is in the gtk2 version (with tilp 6.52-6.68).
> >=20
> > Because there's no difference between the glib12 and glib2
> > versions of lcalcs, it appears to be with tilp itself. However, I
> > don't know the code that good and a lot has changed between 6.09 and
> > 6.52, so does anybody have an idea what might be the problem?
>=20
> If I remember well, I didn't modified libs when switching to GTK2 but
> I may have done some (or too many ?) clean-up...

I've made diffs from each version to the next and couldn't find
anything. The fact that these libs work with TiLP 6.09 also confirms
this. This all points to TiLP itself, but if I'm correct TiLP doesn't
really do any "low level" stuff. It only passes options and commands on
to the libs and that all seems to work ok.

I've also added some debugging info and checked that the cable gets
inited/opened/closed/exited properly and no problems there either.

I'm running out of ideas, but I'll keep trying...

Re: [TiLP-devel] grey link cable trouble

[Julien B. <jb...@jb...>]

Romain Lievin <rom...@wa...> wrote:

>> btw, who owns the project now roms left?
>
> Nobody, yet ! I'm still searching for the right man who will do the
> good job...

Always the same problem... You'll always find people to complain about
the bugs in TiLP/TiEmu, but you'll only find a few who will send
patches...

So, when it comes to taking over the whole project, you can't imagine
the unbelievable amount of candidates we're rejecting daily... sigh.

JB.

--=20
 N> La radio pourrait etre incluse dans ce forum.
 B> Dans un groupe s'appelant TV ? fr.rec.radio parle de quoi ?
 N> j'ai dis une connerie ?
 -+- in: Guide du Neuneu d'Usenet - C'est juste pour =EAtre sur... -+-

Re: [TiLP-devel] grey link cable trouble

[Tijl C. <ti...@ul...>]

On Tue, 16 Sep 2003 18:13:36 +0200, Tijl Coosemans wrote:

> I've ran into a problem with the grey serial cable on FreeBSD.
> Apparently it got introduced with the switch to gtk2, because if I run
> the latest versions (cables 3.7.7, files 0.5.7, calcs 4.4.7-4.5.1)
> there's no problem in gtk12 mode (with tilp 6.09), but there is in the
> gtk2 version (with tilp 6.52-6.68).
> 
> Because there's no difference between the glib12 and glib2
> versions of lcalcs, it appears to be with tilp itself. However, I
> don't know the code that good and a lot has changed between 6.09 and
> 6.52, so does anybody have an idea what might be the problem?
> 
> A little bit more in detail, most of the time I get a timeout error
> while it's receiving the first byte, so sending seems to work and the
> calc also turns on. Very rarely it all does work properly, but I
> haven't found a way to reproduce that.
> 
> Any clue?
> 
> btw, who owns the project now roms left?

I got it working again, but I don't have a nice solution yet. What I did
is setting VMIN=1 en VTIME=0 in tig_open() in libticables, so it waits
indefinitely for a byte to read. VMIN=0 and VTIME=15 (normal values)
doesn't work and gives a timeout error almost immediately as in, it
doesn't wait 1,5 seconds. The strange thing is that the gtk1version
still works flawlessly without any of these modifications.
What's going on here? Are Linux versions affected too?

Re: [TiLP-devel] grey link cable trouble

[Romain L. <rom...@wa...>]

Hi Tijl and mailing list users,

Tijl Coosemans a écrit :
> I've ran into a problem with the grey serial cable on FreeBSD.
> Apparently it got introduced with the switch to gtk2, because if I run
> the latest versions (cables 3.7.7, files 0.5.7, calcs 4.4.7-4.5.1)
> there's no problem in gtk12 mode (with tilp 6.09), but there is in the
> gtk2 version (with tilp 6.52-6.68).
> 
> Because there's no difference between the glib12 and glib2
> versions of lcalcs, it appears to be with tilp itself. However, I don't
> know the code that good and a lot has changed between 6.09 and 6.52, so
> does anybody have an idea what might be the problem?

If I remember well, I didn't modified libs when switching to GTK2 but I 
may have done some (or too many ?) clean-up...

> 
> A little bit more in detail, most of the time I get a timeout error
> while it's receiving the first byte, so sending seems to work and the
> calc also turns on. Very rarely it all does work properly, but I
> haven't found a way to reproduce that.
> 
> Any clue?

Hmmm, I'm gonna to take a look at my changelog...

> 
> btw, who owns the project now roms left?

Nobody, yet ! I'm still searching for the right man who will do the good 
job...

> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> TiLP-devel mailing list
> TiL...@li...
> https://lists.sourceforge.net/lists/listinfo/tilp-devel
> 

roms.
-- 
Romain Liévin, aka 'roms'  	<ro...@ti...>
Site web 			<http://tilp.info>
Messagerie instantanée (ICQ)    43585029
"Linux, y'a moins bien mais c'est plus cher !"

[TiLP-devel] grey link cable trouble

[Tijl C. <ti...@ul...>]

I've ran into a problem with the grey serial cable on FreeBSD.
Apparently it got introduced with the switch to gtk2, because if I run
the latest versions (cables 3.7.7, files 0.5.7, calcs 4.4.7-4.5.1)
there's no problem in gtk12 mode (with tilp 6.09), but there is in the
gtk2 version (with tilp 6.52-6.68).

Because there's no difference between the glib12 and glib2
versions of lcalcs, it appears to be with tilp itself. However, I don't
know the code that good and a lot has changed between 6.09 and 6.52, so
does anybody have an idea what might be the problem?

A little bit more in detail, most of the time I get a timeout error
while it's receiving the first byte, so sending seems to work and the
calc also turns on. Very rarely it all does work properly, but I
haven't found a way to reproduce that.

Any clue?

btw, who owns the project now roms left?

[TiLP-devel] Great work

[Joe F. <joe...@ya...>]

First, I must say this: Great work on the GTK2
version, it's wonderful. Getting it to compile was a
bit tricky and that's what this email is about. 

I downloaded all of the latest libraries from the
Sourceforge archive (devel), then did a ./configure
make make install. There were a few problems with the
build process though, make kept looking for files that
weren't there. Libticables 3.7.5 kept looking for
porttalk.c and tilp 6.65 was missing several glade
.str files. I simply did a touch for each of the
missing files and it compiled and ran fine. Newest
version seems to connect more reliably too (Black
Link, TI83+). Hope this helps

-Joe Flint

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

Re: [TiLP-devel] cvs nagging

[Romain L. <rom...@wa...>]

Hi,

On Tue, May 06, 2003 at 06:11:53PM +0200, Julien BLACHE wrote:
> Thomas Otto <3.1...@gm...> wrote:
> 
> > Err - do all the CVS commits have to go on the Mailinglist or wouldn't
> > a seperate list be better for this since I am actually only on this
> > list to know when I have to adjust the german translation so all these
> > CVS checking are rather "disturbing" ;-)
> 
> I can remove the diff if the size is the problem, otherwise, given the
> mail includes the modified files, I think it helps you to track the
> changes to the PO files.
> 
> I'll disable the diff for now.
> 
> Btw, svn.technologeek.org could be hard to reach tomorrow morning due
> to a large transfer (~ 5 GB, I expect it to last all the morning at
> least).
> 

That's ok for me. I will be at work ;-)

> JB.
> 
> -- 
> Julien BLACHE                                   <http://www.jblache.org> 
> <jb...@jb...> 
> 
> 

roms.

> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
> 
> _______________________________________________
> TiLP-devel mailing list
> TiL...@li...
> https://lists.sourceforge.net/lists/listinfo/tilp-devel

-- 
Romain Lievin, aka 'roms'  	<ro...@ti...>
The TiLP project is on 		<http://www.ti-lpg.org>
"Linux, y'a moins bien mais c'est plus cher !"

Re: [TiLP-devel] cvs nagging

[Julien B. <jb...@jb...>]

Thomas Otto <3.1...@gm...> wrote:

> Err - do all the CVS commits have to go on the Mailinglist or wouldn't
> a seperate list be better for this since I am actually only on this
> list to know when I have to adjust the german translation so all these
> CVS checking are rather "disturbing" ;-)

I can remove the diff if the size is the problem, otherwise, given the
mail includes the modified files, I think it helps you to track the
changes to the PO files.

I'll disable the diff for now.

Btw, svn.technologeek.org could be hard to reach tomorrow morning due
to a large transfer (~ 5 GB, I expect it to last all the morning at
least).

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb...@jb...> 

[TiLP-devel] cvs nagging

[Thomas O. <3.1...@gm...>]

Err - do all the CVS commits have to go on the Mailinglist or wouldn't a 
seperate list be better for this since I am actually only on this list 
to know when I have to adjust the german translation so all these CVS 
checking are rather "disturbing" ;-)

   -Thomas