mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Cc: j-core@lists.j-core.org
Subject: Re: Re: [J-core] [musl] updated cross-compiler build system
Date: Sun, 1 May 2016 23:55:22 +0200	[thread overview]
Message-ID: <20160501215521.GQ22574@port70.net> (raw)
In-Reply-To: <20160501171554.GI21636@brightrain.aerifal.cx>

* Rich Felker <dalias@libc.org> [2016-05-01 13:15:55 -0400]:
> On Sun, May 01, 2016 at 05:38:04PM +0200, Szabolcs Nagy wrote:
> > changed $$(LC_ROOT) to $${LC_ROOT} because it seems to
> > be passed to bash in config.status (as $$(, \$( and  $(
> > and the last one executes LC_ROOT as a command, this
> > might be an autoconf bug: it does not escape the args
> > correctly)
> 
> I noticed that too but didn't get around to looking into the details
> since nothing broke. The whole point though is to _avoid_ it getting
> expanded in places like config.status -- I was trying to keep the
> absolute path to the top-level dir from getting saved anywhere in the
> build tree, so that it can safely be moved. Do you know if your change
> preserves this property?
> 

the only difference i see is the --with-build-sysroot in
gcc -v output has abs path in my version, but otherwise
strings gcc |grep / has the same output.

> > for me make fails in bfd/doc despite MAKINFO=false, but
> > the export AM_MAKEFLAGS=INFO_DEPS= hack fixed it.
> 
> Uhg, yes, I just installed texinfo on my VPS and forgot to check the
> case where it's missing.
> 

this hack is not ok in general as Makefile.am might
have its own AM_MAKEFLAGS.

> > 	$(MAKE) -C ../src_linux headers_install ARCH=$$A \
> > 		CROSS_COMPILE=$(DESTDIR)$(OUTPUT)/$(TARGET)- \
> > 		INSTALL_HDR_PATH=$(DESTDIR)$(OUTPUT)/$(TARGET)
> 
> AFAIK you don't need CROSS_COMPILE= to install headers, and in
> principle it shouldn't be there because the install targets are not
> intended to depend on each other. But you do need to install to a
> staging dir and then copy to the final dest; the broken
> headers_install target in Linux rm's the scsi headers (eew) provided
> by libc and fails to provide replacements.
> 

i see

> > @@ -55,13 +55,13 @@ src_musl: | $(MUSL_SRCDIR)
> >  	ln -sf $(MUSL_SRCDIR) $@
> >  
> >  src_gmp: | $(GMP_SRCDIR)
> > -	ln -sf "$(GMP_SRCDIR)" $@
> > +	ln -sf $(GMP_SRCDIR) $@
> >  
> >  src_mpc: | $(MPC_SRCDIR)
> > -	ln -sf "$(MPC_SRCDIR)" $@
> > +	ln -sf $(MPC_SRCDIR) $@
> >  
> > -src_mpfr: | $(GMP_SRCDIR)
> > -	ln -sf "$(MPFR_SRCDIR)" $@
> > +src_mpfr: | $(MPFR_SRCDIR)
> > +	ln -sf $(MPFR_SRCDIR) $@
> 
> The dep was wrong, but the quoting was intentional, albeit untested.
> The idea was to make broken symlinks that would then ENOENT out if the
> caller does not want to provide these libs (i.e. wants to use the
> system ones). But apparently symlink(2) fails with ENOENT in this
> case, so I need a new solution...

i see


  reply	other threads:[~2016-05-01 21:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-01  5:45 Rich Felker
2016-05-01 15:38 ` Szabolcs Nagy
2016-05-01 17:15   ` [J-core] [musl] " Rich Felker
2016-05-01 21:55     ` Szabolcs Nagy [this message]
     [not found]     ` <5726965F.1060406@landley.net>
2016-05-02  2:58       ` Rich Felker
2016-05-02  4:31         ` Rob Landley
2016-05-02 15:52     ` question: use of musl-libc anonymous

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=20160501215521.GQ22574@port70.net \
    --to=nsz@port70.net \
    --cc=j-core@lists.j-core.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).