mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: ./configure errors witn musl-gcc (zlib library conflict when building openssh)
Date: Fri, 5 Aug 2016 19:30:46 -0400	[thread overview]
Message-ID: <20160805233046.GR15995@brightrain.aerifal.cx> (raw)
In-Reply-To: <20160805232605.GB9968@haswell>

On Fri, Aug 05, 2016 at 04:26:05PM -0700, Khem Raj wrote:
> On 16-08-05 18:32:14, Assaf Gordon wrote:
> > Hello,
> > 
> > I'm trying to build openssh on Ubuntu with musl-gcc, and encountered a problem during "./configure" due to required library (zlib) which causes conflicts between the system's glibc and musl-libc.
> > 
> > There is probably a simple solution, but I couldn't find one.
> > 
> > The system is Ubuntu 14.04 LTS, gcc 4.8.4.
> > musl is 1.1.15 built from source, installed to /usr/local/musl .
> > 
> > First, I build zlib using musl-gcc:
> > 
> >      wget http://zlib.net/zlib-1.2.8.tar.gz
> >      tar -xf zlib-1.2.8.tar.gz
> >      cd zlib-1.2.8
> >      CC=musl-gcc ./configure
> >      make
> > 
> > This works well (note I did not install it with 'sudo make install').
> > 
> > Second, I try to build openssh:
> > 
> >     git clone https://github.com/openssh/openssh-portable
> >     cd openssh-portable
> >     autoreconf -if
> >     CC=musl-gcc ./configure --without-stackprotect --with-zlib=/home/ubuntu/sources/zlib-1.2.8
> 
> I think you need to point it to a staged install of zlib, so may be run make DESTDIR="some/location" install
> when building zlib

That may also be true, but if so, the result of failure to do so
should be failure to find the library at all, not using a
glibc-ecosystem copy of library.

Rich


  reply	other threads:[~2016-08-05 23:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05 22:32 Assaf Gordon
2016-08-05 23:08 ` Rich Felker
2016-08-05 23:26 ` Khem Raj
2016-08-05 23:30   ` Rich Felker [this message]
2016-08-05 23:33 ` Rich Felker
2016-08-13  3:57   ` Assaf Gordon

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=20160805233046.GR15995@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).