public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Harley Laue <losinggeneration@gmail.com>
To: linux-8086@vger.kernel.org
Subject: Re: MAKE errors when trying to compile in Ubuntu 9.10
Date: Tue, 2 Mar 2010 13:24:21 -0600	[thread overview]
Message-ID: <ef8d4e9b1003021124y1442020asa3c40b345b114a9d@mail.gmail.com> (raw)
In-Reply-To: <20100301093133.GA19186@gevaerts.be>

Frank Gevaerts wrote:
> On Tue, Mar 02, 2010 at 01:25:28AM -0500, Dieter R Kedrowitsch wrote:
> > Greetings!  I am trying to compile ELKS from the archive
> > elks-0.1.3.tar.gz and I am experiencing an error during make that I have
> > never seen before.  I am using bin86 0.16.17 on a pretty much stock
> > installation of Ubuntu 9.10.
> >
> > This is just a small snippet of an error that is repeated many times
> > when I run make to 'make dep'.
> >
> > printf: 1: $[0x000103-1]: expected numeric value
> > printf: 1: $[0x000103-1]: expected numeric value
> > printf: 1: $[0x000103-1]: expected numeric value
>
> This looks like your shell doesn't like some particular printf syntax.
> Doesn't Ubuntu use dash as /bin/sh? Try setting it to bash

 I can confirm this on Debian with dash. The problem goes away as soon as
/bin/sh is switched from dash to bash.

  reply	other threads:[~2010-03-02 19:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <S1750932Ab0CAFCB/20100301050201Z+473@vger.kernel.org>
2010-03-01  6:24 ` MAKE errors when trying to compile in Ubuntu 9.10 Dieter R Kedrowitsch
2010-03-01  9:31   ` Frank Gevaerts
2010-03-02 19:24     ` Harley Laue [this message]
2010-03-02 19:52   ` Dieter R Kedrowitsch
2010-03-02 20:24     ` Harley Laue
2010-03-02 20:37       ` MAKE errors when trying to compile in Ubuntu 9.10 (nospam: message 9 of 20) Dieter R Kedrowitsch

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=ef8d4e9b1003021124y1442020asa3c40b345b114a9d@mail.gmail.com \
    --to=losinggeneration@gmail.com \
    --cc=linux-8086@vger.kernel.org \
    /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