mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alba Pompeo <albapompeo@gmail.com>
To: musl@lists.openwall.com
Subject: Re: musl & proprietary programs
Date: Thu, 24 Dec 2015 19:29:34 -0200	[thread overview]
Message-ID: <CAJDAfTDQm98R-CfKN5aYHYvjB-YUXwTCs0+CFz1LE1xUpSUgyw@mail.gmail.com> (raw)
In-Reply-To: <20151224194944.GA6996@newbook>

Isaac, I just realized nobody on the mailing list received that copy I
sent you. It was delivered to just 1 person by my mistake.
Here's a copy to everyone.

Here's a list of some programs I couldn't get to work - in
alphabetical order and with links to those easily available (no
registration required for free trial).

AIMMS http://download.aimms.com/aimms/download/data/4.13/2.233/Aimms-4.13.2-233.x86_64.rpm
AMPL http://ampl.com/dl/demo/ampl-demo-linux64.tar.gz
MATLAB
Siemens NX
SPSS

It was a colleague that recommended me musl and I immediately loved it
after reading about its goals. But he forgot to tell me about these
shortcomings, which he has too. We both have to dual-boot to use most
proprietary software we need. Maybe we are doing something wrong?

I both thanked my colleague to have introduced me to musl and cursed
him for making my life harder :)
But in general I'm pleased to use musl now. I hope the proprietary
software I need works well.

For now I'd like to focus on AMPL. I got it to run on a chroot as per
my work colleague help, but Rich Felker's suggestions sounds much
better. But I'm out of luck by being a novice user. Does anyone know
of a guide for Void or Alpine (musl distributions) that explain it in
a step-by-step? I couldn't find any.

@Isaac
If it makes things easier, CPLEX can be used instead of MINOS. Does
that helps a bit?

Ciao.

On Thu, Dec 24, 2015 at 5:49 PM, Isaac Dunham <ibid.ag@gmail.com> wrote:
> On Wed, Dec 23, 2015 at 11:00:51PM -0800, Isaac Dunham wrote:
>> On Wed, Dec 23, 2015 at 06:00:12PM -0200, Alba Pompeo wrote:
>> > I also don't want to pollute my system with glibc. That's why I asked
>> > if there was any plan to improve musl support of proprietary programs
>> > like the ones I listed.
>>
>> I looked through the thread and saw no list of proprietary programs.
>> (Is this undelivered mail? is google bouncing random emails?)
>
> (Apparently didn't get successfully delivered from the list to me; thanks
>  for sending a copy.)
>
> Looking at AMPL's linux32 demo, I get this list of missing functions:
>  __divdi3
>  __fpu_control
>  __isinf
>  __isinfl
>  __isnanl
>  __strtod_internal
>  fedisableexcept
>  feenableexcept
>  pthread_rwlockattr_setkind_np
>
> The first indicates that it may be necessary to add libgcc_s.so.1 to
> LD_PRELOAD.
> The rest are missing from musl for ABI compat.
> ampl and minos are "for GNU/Linux 2.2.5", so may use the 32-bit IO abi.
> __is* can be trivially implemented.
> __strtod_internal is a version of strtod with an extra int that's expected
> to be 0 (per LSB); no idea what that's for.
>
> HTH,
> Isaac Dunham


  reply	other threads:[~2015-12-24 21:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 11:23 Alba Pompeo
2015-12-22 11:27 ` Timo Teras
2015-12-22 15:25   ` Рысь
2015-12-22 15:37     ` Alba Pompeo
2015-12-23 14:48       ` Szabolcs Nagy
2015-12-23 16:01         ` u-uy74
2015-12-23 17:22         ` Рысь
2015-12-23 17:43           ` Rich Felker
2015-12-23 18:51             ` Рысь
2015-12-23 20:00               ` Alba Pompeo
2015-12-24  5:04                 ` Рысь
2015-12-24  5:16                   ` Rich Felker
2015-12-24 10:40                     ` Szabolcs Nagy
2015-12-27  3:54                       ` Rich Felker
2015-12-24  7:00                 ` Isaac Dunham
2015-12-24 19:49                   ` Isaac Dunham
2015-12-24 21:29                     ` Alba Pompeo [this message]
2015-12-24  5:12               ` Rich Felker
2015-12-24  7:20                 ` Рысь

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJDAfTDQm98R-CfKN5aYHYvjB-YUXwTCs0+CFz1LE1xUpSUgyw@mail.gmail.com \
    --to=albapompeo@gmail.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).