From: Bernhard Walle <bernhard@bwalle.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Using PTXdist on Mac OS
Date: Tue, 17 Apr 2012 13:45:04 +0200 [thread overview]
Message-ID: <20120417114504.GA11343@regiomontanus.bwalle.de> (raw)
In-Reply-To: <20120417112406.GI8237@pengutronix.de>
Hi,
* Michael Olbrich <m.olbrich@pengutronix.de> [2012-04-17 13:24]:
> On Tue, Apr 17, 2012 at 01:08:12PM +0200, Daniel Kriesten wrote:
> [...]
> > So, following your your document I end up with a working tool-chain, a
> > working qemu-arm-softmmu and a working kernel, but no hdd img.
> > I had to fix
> > .../lib/ptxdist-2012.04.0/scripts/genhdimg
> > replacing seq by gseq. But the better approach may be a symlink in
> > .../lib/ptxdist-2012.04.0/bin/
>
> Well, genhdimg is the only user of 'seq', so I'd rather fix that. Would you
> care to send a patch?
But gseq is not available on Linux. So I think adding it to the
configure check is the only reasonable approach?
> [...]
> > An other thing is xargs ... without the gnu version make distclean fails.
> > The solution is to symlink in .../lib/ptxdist-2012.04.0/bin/, too.
>
> It's "make clean" actually and that will remove the relevant symlink.
> Would this work:
That one is already in ptxdist, after 2012.04:
http://git.pengutronix.de/?p=ptxdist.git;a=commit;h=394af1de808e6fc4c3cf921d36e1b1f887133eb7
> ------------------------------------------------------------------
> diff --git a/Makefile.in b/Makefile.in
> index 8382402..32784c8 100644
> --- a/Makefile.in
> +++ b/Makefile.in
> @@ -63,7 +63,7 @@ environment:
>
> clean:
> @rm -f .done
> - @find "$(abs_srcdir)/bin" -type l -print0 | xargs -r -0 rm
> + @cd "$(abs_srcdir)/bin" && find -type l -print | xargs rm -f
> @$(MAKE) -C "$(abs_srcdir)/scripts/kconfig" clean
Maybe just -exec ? Maybe it is a bit slower? But see above.
Regards,
Bernhard
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-04-17 11:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 17:11 Bernhard Walle
2012-04-09 17:48 ` Juergen Beisert
2012-04-10 9:37 ` Bernhard Walle
2012-04-09 18:01 ` Andreas Bießmann
2012-04-09 18:59 ` Bernhard Walle
2012-04-09 19:47 ` Juergen Beisert
2012-04-09 20:04 ` Andreas Bießmann
2012-04-09 20:48 ` Andreas Bießmann
2012-04-10 9:04 ` Bernhard Walle
2012-04-10 18:35 ` Bernhard Walle
2012-04-17 11:08 ` Daniel Kriesten
2012-04-17 11:24 ` Michael Olbrich
2012-04-17 11:45 ` Bernhard Walle [this message]
2012-04-17 11:59 ` Daniel Kriesten
2012-04-17 12:03 ` Bernhard Walle
2012-04-17 12:32 ` Daniel Kriesten
2012-04-18 8:29 ` Michael Olbrich
2012-04-18 11:25 ` Daniel Kriesten
2012-04-18 14:16 ` Michael Olbrich
2012-04-18 14:28 ` Daniel Kriesten
2012-04-19 10:41 ` Daniel Kriesten
2012-04-19 11:29 ` Andreas Bießmann
2012-04-19 12:04 ` Daniel Kriesten
2012-04-19 12:25 ` Andreas Bießmann
2012-04-19 13:12 ` Daniel Kriesten
2012-04-19 13:27 ` Michael Olbrich
2012-04-19 14:03 ` Andreas Bießmann
2012-04-19 20:13 ` Bernhard Walle
2012-12-08 15:31 ` Daniel Kriesten
2012-12-08 15:43 ` [ptxdist] Using PTXdist on Mac OS 10.7 Daniel Kriesten
2012-12-10 8:48 ` Michael Olbrich
2012-12-10 8:46 ` [ptxdist] Using PTXdist on Mac OS Michael Olbrich
2012-12-11 15:00 ` Daniel Kriesten
2012-12-12 11:00 ` Michael Olbrich
2012-04-17 11:48 ` Bernhard Walle
2012-04-17 12:04 ` Daniel Kriesten
2012-04-17 12:18 ` Bernhard Walle
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=20120417114504.GA11343@regiomontanus.bwalle.de \
--to=bernhard@bwalle.de \
--cc=ptxdist@pengutronix.de \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox