Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 4 Sep 2018 16:27:14 +0300
From: John Found <>
Subject: Re: How to use MUSL without installing it?

On Tue, 4 Sep 2018 13:58:28 +0200
Szabolcs Nagy <> wrote:

> * John Found <> [2018-09-04 14:34:39 +0300]:
> > On Tue, 4 Sep 2018 11:40:20 +0200
> > Szabolcs Nagy <> wrote:
> > > i think you can pass 'CROSS_COMPILE=' to configure
> > > and then you don't need such symlinks.
> > > 
> > What value should I set CROSS_COMPILE to? i386?
> > 
> leave it empty (by default it is '386-')
> ./configure --host=i386 CROSS_COMPILE=

Unfortunately, it is not working this way.
I was able to make it compile without the symlinks only by
passing CROSS_COMPILE="/bin/"

The empty value falls back to the
default "i386" and is searching for "i386-ar" and so on.

> > Well, I will keep it the right way then. BTW, "make install"
> > tries to create symlink for in /usr/lib/ directory
> > How to prevent this attempt?
> if you don't use dynamic linking then --disable-shared
> if you want to build dynamic linked executables that work
> locally with your musl install, but not portable to other
> musl systems then --syslibdir='$(prefix)/lib'
> (then the binaries will use that path for the dynamic linker)
> if you want to build dynamic linked executables that are
> portable, but don't run locally, then ignore that failure
> (it is not fatal, binaries will have standard dynamic linker
> path, but your system will not have it set up)
> if you want to build dynamic linked executables that are
> portable and work locally, then you must have the dynamic
> linker in /lib so you have to put the symlink there.

John Found <>

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.