Error Installing TILP2 on OSX 10.14

Question

Error Installing TILP2 on OSX 10.14

acagliano opened this issue 5 years ago · 7 comments

ld: warning: directory not found for option '-L/usr/local/opt/libiconv/lib/'
Undefined symbols for architecture x86_64:
  "_iconv", referenced from:
      _ticonv_iconv in libticonv_la-iconv.o
     (maybe you meant: _ticonv_iconv_close, _ticonv_iconv_open , _ticonv_iconv )
  "_iconv_close", referenced from:
      _ticonv_iconv_close in libticonv_la-iconv.o
     (maybe you meant: _ticonv_iconv_close)
  "_iconv_open", referenced from:
      _ticonv_iconv_open in libticonv_la-iconv.o
     (maybe you meant: _ticonv_iconv_open)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [libticonv.la] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

The build script fails on this line. I also get an error for not finding the package libarchive. I use a Homebrew installation for installing my packages.

As a segway: Considering there is a (albiet outdated) Macports formula for tilp2, I'm surprised you guys haven't created a Homebrew formula or cask to install this thing.

Answer 1 · 2019-08-26T01:08:44.000Z

Looks like you forgot some things (probably either setting the pkg config thing in your bash_profile (or equivalent), or the libiconv for linkage from brew if that's even still possible). Regarding homebrew cask, there is one actually :) Juju made one, its on his github. Might not be published directly though, I'm not sure.

Answer 2 · 2019-08-26T01:31:51.000Z

Edit2: What is the link to the Cask?

Well, now I have an update: I was able to get it fully installed, but now I get this during runtime, with sudo. It does not detect the calculator at all, says "cannot open resource" and says perhaps to check the permissions on the libs.

tilp-INFO: 21:13:17.647: Opening cable null on port #2 to communicate with calculator TI84+CE USB
ticalcs-INFO: 21:13:23.440: Checking hand-held status:
ticalcs-INFO: 21:13:23.440:   PC->TI: Buffer Size Request (1024 bytes)

(tilp:27386): ticalcs-WARNING **: 21:13:23.440: Raw packet is unexpectedly large: 3976101632 bytes

(tilp:27386): ticalcs-CRITICAL **: 21:13:23.440: Raw packet is too large: 3976101632 bytes
ticalcs-INFO: 21:13:23.440: Checking hand-held status:
ticalcs-INFO: 21:13:23.440:   PC->TI: Buffer Size Request (1024 bytes)

(tilp:27386): ticalcs-WARNING **: 21:13:23.440: Raw packet is unexpectedly large: 3976101632 bytes

(tilp:27386): ticalcs-CRITICAL **: 21:13:23.440: Raw packet is too large: 3976101632 bytes
ticalcs-INFO: 21:13:26.475: Checking hand-held status:
ticalcs-INFO: 21:13:26.475:   PC->TI: Buffer Size Request (1024 bytes)

(tilp:27386): ticalcs-WARNING **: 21:13:26.475: Raw packet is unexpectedly large: 3976101632 bytes

(tilp:27386): ticalcs-CRITICAL **: 21:13:26.475: Raw packet is too large: 3976101632 bytes
ticalcs-INFO: 21:13:26.475: Checking hand-held status:
ticalcs-INFO: 21:13:26.475:   PC->TI: Buffer Size Request (1024 bytes)

(tilp:27386): ticalcs-WARNING **: 21:13:26.475: Raw packet is unexpectedly large: 3976101632 bytes

Trying to follow some of the setup for non-root user now.
Edit: Same result

Answer 3 · 2019-08-26T05:43:09.000Z

Is cable null on port #2 to communicate with calculator TI84+CE USB what TILP (libticalcs) detected automatically ? If you're really using a 84+CE, and it's the only TI graphing calculator plugged into your computer, change your settings to the more expected cable DirectLink and port 1, and try again.

Given the above, I'd like you to make explicit your calculator model, cable model and OS version running on the calculator: I know you from other sites, but you made ASM programs for both monochrome TI-Z80 and the TI-eZ80 series :)

3976101632 = 0xECFE7F00, which is a weird value, even in the other endianness, but libticalcs uses the appropriate one, otherwise more people, starting with Adriweb, would certainly have complained.

Answer 4 · 2019-08-26T19:47:03.000Z

When I do this, it says “unable to open device”. I’m convinced that this is some sort of library error or something. Since I did part of the installation with Homebrew, and part of it manually. How would I set up a homebrew tap or cask for this? Or what’s the link to the existing one? I feel doing the whole install in a consistent way would be better.

…

Sent from my iPhone

On Aug 26, 2019, at 1:43 AM, Lionel Debroux ***@***.***> wrote: Is cable null on port #2 to communicate with calculator TI84+CE USB what TILP (libticalcs) detected automatically ? If you're really using a 84+CE, and it's the only TI graphing calculator plugged into your computer, change your settings to the more expected cable DirectLink and port 1, and try again. Given the above, I'd like you to make explicit your calculator model, cable model and OS version running on the calculator: I know you from other sites, but you made ASM programs for both monochrome TI-Z80 and the TI-eZ80 series :) 3976101632 = 0xECFE7F00, which is a weird value, even in the other endianness, but libticalcs uses the appropriate one, otherwise more people, starting with Adriweb, would certainly have complained. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Answer 5 · 2019-08-27T00:26:31.000Z

Well, homebrew should only be used to install the deps, then the install script or the cmake line is used to build libti* and tilp. The install script says which brew command to use and which exports to add regarding pkgconfig so that the deps gets found properly. Anyway, we can probably help you on irc directly

Answer 6 · 2019-08-27T13:58:47.000Z

Turns out I was trying to use a USB power-only cable. Works fine when I use the correct cable.
Genius Level: Expert.
Thanks for the help, anyway.

Answer 7 · 2019-08-27T14:22:43.000Z

Eh, don't worry... mistakes happen :)
Obtaining the USB devices list from MacOS X was probably one of the next debugging steps (and may be what you did yourself); if the calculator had already been undetected at the OS level, you'd have looked at the physical components of the connection to the computer, anyway.