[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: RE: Managing IUP on Linux
- From: "Antonio Scuri" <scuri@...>
- Date: Tue, 10 Jun 2014 10:27:20 -0300
Very interesting tools. I use Virtual Machines to build our binaries.
I think that the LSB tools will be very helpful.
The problem in choosing an old Ubuntu version is the GTK version that affects several IUP features. Some of these features are at the GTK API level forcing us to do some ifdefs using GTK_CHECK_VERSION along the IUP code. So the system must be updated with a newer GTK (at least GTK 2.12). I don't know if this is an issue in Ubuntu 8.04.
But you pointed me a very interesting direction. This could simplify a lot the IUP distribution.
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:email@example.com] On
> Behalf Of Stefano
> Sent: terça-feira, 10 de junho de 2014 06:02
> To: Lua mailing list
> Subject: Re: Managing IUP on Linux
> On 10 June 2014 08:45, Antonio Scuri <firstname.lastname@example.org> wrote:
> > As I told you before, the target system for our pre-compiled
> > binaries is Ubuntu. Not the regular debian Debian. That's why you need
> > to do all these hacks. Probably it is also the same cause of the
> > segmentation fault. Because there is also GTK involved.
> > In my opinion, "naive users" as you mention on your initial e-mail
> > will choose to install an easy system. And Ubuntu seems to be the
> > common choice.
> > Anyway, I never generated binaries for a specific version of libc before.
> > Best,
> > Scuri
> Well, what I'm doing for my Linux LuaJIT binaries is to build them using an
> *ancient* version of Ubuntu (I use Ubuntu 8.04 LTS) via chroot, see for
> The distro compatibility of the resulting binary can be checked using this tool:
> Even if not LSB-compliant you'll observe a very large degree of compatibility
> among distributions if you build your binary using an old version of libc as
> described above...