<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to tilp-devel</title><link href="https://sourceforge.net/p/tilp/discussion/131473/" rel="alternate"/><link href="https://sourceforge.net/p/tilp/discussion/131473/feed.atom" rel="self"/><id>https://sourceforge.net/p/tilp/discussion/131473/</id><updated>2019-11-28T10:45:37.694000Z</updated><subtitle>Recent posts to tilp-devel</subtitle><entry><title>Installing with install_tilp.sh to alternative PREFIX</title><link href="https://sourceforge.net/p/tilp/discussion/131473/thread/948784ce22/?limit=25#0df4" rel="alternate"/><published>2019-11-28T10:45:37.694000Z</published><updated>2019-11-28T10:45:37.694000Z</updated><author><name>Lionel Debroux</name><uri>https://sourceforge.net/u/debrouxl/</uri></author><id>https://sourceforge.net3e2d56dc2a641eca8226ccaf914706fa17900885</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Well, I'm not sure what happens in the case you describe: it's been years since I started always recommending users to uninstall the distro packages before attempting to build libti*/gfm/tilp, TIEmu (if that's still possible on modern distros...) or TilEm, in order to avoid potential interference between the distro packages and the headers + binaries being built and installed :)&lt;/p&gt;
&lt;p&gt;Which calculator and cable are you using ?&lt;/p&gt;
&lt;p&gt;FWIW, starting from the next release - when I produce it - packages for future releases of Debian and derivative distros will contain the TI-Z80 and TI-68k ROM/Flash dumpers out of the box, because I rewrote / converted them in such a way that they can be built from source using programs packaged by Debian and derivatives. Only the TI-eZ80 ROM dumper will remain disabled by Debian, because there's no eZ80 assembler in the Debian archives, AFAICT.&lt;/p&gt;
&lt;p&gt;Bye,&lt;br/&gt;
Lionel.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>compiling on Slackware64 up-to-date stable 14.2</title><link href="https://sourceforge.net/p/tilp/discussion/131473/thread/1f2791cc/?limit=25#522c" rel="alternate"/><published>2017-10-11T17:52:33.319000Z</published><updated>2017-10-11T17:52:33.319000Z</updated><author><name>Lionel Debroux</name><uri>https://sourceforge.net/u/debrouxl/</uri></author><id>https://sourceforge.net83c9f67d175ba39c5aa3281029b780fd284f2c16</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;In a Docker container run thusly:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;docker run -it --rm vbatts/slackware:14.2&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;after running&lt;/p&gt;
&lt;p&gt;&lt;code&gt;slackpkg install git gcc binutils make pkgconfig autoconf automake libtool glib2 zlib libusb gtk+2 libglade gettext bison flex groff texinfo xdg-utils libarchive intltool xz ca-certificates libmpc glibc cyrus-sasl curl perl m4 less kernel-headers pkg-config guile gc libffi libcroco libxml2 lzo nettle acl eudev pango cairo pixman fontconfig freetype libpng harfbuzz expat mesa libdrm libX11 xproto kbproto libxcb libpthread-stubs libXau libXdmcp libXext xextproto libXdamage damageproto libXfixes fixesproto libXxf86vm xf86vidmodeproto libXrender renderproto gdk-pixbuf2 atk libxshmfence libXinerama libXi libXrandr libXcursor libXcomposite&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;the build using the standard script from the Github debrouxl/tilp_and_gfm repo, for which an official shortlink is &lt;a href="https://ti-pla.net/tilpinst" rel="nofollow"&gt;https://ti-pla.net/tilpinst&lt;/a&gt; , works for me.&lt;/p&gt;
&lt;p&gt;As I wrote on IRC, where I saw your lines after being notified about this topic, performing manual dependency resolution, a.k.a playing whack-a-mole on missing dependencies, wasn't much fun - but at least it's done, and it shall end up in the next update of install_tilp.sh in the Git repo.&lt;/p&gt;
&lt;p&gt;Does the above install solve whatever the issue on your computer, shown by that unusual error message, was - or do you still get the same errors as dTal ?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>compiling on Slackware64 up-to-date stable 14.2</title><link href="https://sourceforge.net/p/tilp/discussion/131473/thread/1f2791cc/?limit=25#e4cf" rel="alternate"/><published>2017-10-11T02:00:14.102000Z</published><updated>2017-10-11T02:00:14.102000Z</updated><author><name>David Melik</name><uri>https://sourceforge.net/u/dchmelik/</uri></author><id>https://sourceforge.net5d1e437358551d5a9ba4031590e8014f480c70e5</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;d@cosmos:~/tilp2-1.18$ ./configure
configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.."
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;If you can fix that or explain what to do to get it to work, I'd be able to tell other Slackware users how to compile it, or I could submit Tilp2 to SlackBuilds.org so anyone can automatically build &amp;amp; install the package with a quasi-official package manager.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>