public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Sascha Kilian <sascha@sakisoft.de>
To: development@lists.ipfire.org
Subject: Re: Toolchain Build Failure
Date: Wed, 26 Feb 2014 12:33:27 +0100	[thread overview]
Message-ID: <1393414407.2393.9.camel@localhost> (raw)
In-Reply-To: <1393414023.21180.62.camel@rice-oxley.tremer.info>

[-- Attachment #1: Type: text/plain, Size: 3010 bytes --]

The toolchain compiled successful on the old stand of repository,
on the new stand i try with bash instead of dash.

Since i updated to "next", it crashes on ncurses. 


Am Mittwoch, den 26.02.2014, 12:27 +0100 schrieb Michael Tremer:
> On Wed, 2014-02-26 at 12:20 +0100, Sascha Kilian wrote:
> > okay, 
> > 
> > i have checked my /bin/sh, it pointed to dash, now its bash :)
> > i have downloaded the toolchain and it compiles. the Time is not really
> > interessed for me, its i7 with no workload and i can use it to compile
> > some things like ipfire :)
> 
> It still takes some time and is energy consuming.
> 
> > The System is a Debian 7 x64
> > 
> > is the toolchain now buildable with /bin/bash ?
> 
> Yes. I think so.
> 
> dash is some sort of lightweight shell and not 100% compatible with the
> build systems of the packages we build there.
> 
> -Michael
> 
> > Am Mittwoch, den 26.02.2014, 11:24 +0100 schrieb Michael Tremer:
> > > Hello Sascha,
> > > 
> > > I think that your shell does not provide those kinds of substitution we
> > > are using there.
> > > 
> > > If your /bin/sh is pointing to dash or something else, you should change
> > > that to /bin/bash.
> > > 
> > > Honestly, I would recommend to download the toolchain unless you are
> > > building for a new architecture. This will save you some time and of
> > > course the trouble of compiling it.
> > > 
> > > -Michael
> > > 
> > > On Wed, 2014-02-26 at 10:35 +0100, Sascha Kilian wrote:
> > > > Good Morning,
> > > > 
> > > > i tried to make a clean build to verify the Fireinfo and have the newest
> > > > version.
> > > > 
> > > > i can reproduce this by run the following commands:
> > > > 
> > > > on ipfire-2.x folder
> > > > 
> > > > "git checkout next" (told me i am already on this)
> > > > "git pull" (told me some updates or up-to-date)
> > > > "./make.sh clean"
> > > > "./make.sh build"
> > > > 
> > > > on Building the Toolchain::ncurses i got following Compile error
> > > > 
> > > > make[2]: Leaving directory
> > > > `/opt/ipfire/ipfire-2.x/build/usr/src/ncurses-5.9/widec/c++'
> > > > make[1]: Leaving directory
> > > > `/opt/ipfire/ipfire-2.x/build/usr/src/ncurses-5.9/widec'
> > > > # Install everything.
> > > > cd /opt/ipfire/ipfire-2.x/build/usr/src/ncurses-5.9 && make -C narrowc
> > > > install.{libs,progs,data}
> > > > make[1]: Entering directory
> > > > `/opt/ipfire/ipfire-2.x/build/usr/src/ncurses-5.9/narrowc'
> > > > make[1]: *** No rule to make target `install.{libs,progs,data}'.  Stop.
> > > > make[1]: Leaving directory
> > > > `/opt/ipfire/ipfire-2.x/build/usr/src/ncurses-5.9/narrowc'
> > > > make: *** [/opt/ipfire/ipfire-2.x/log/ncurses-5.9-tools] Error 2
> > > > 
> > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Development mailing list
> > > > Development(a)lists.ipfire.org
> > > > http://lists.ipfire.org/mailman/listinfo/development
> > > 
> > 
> > 
> 



      reply	other threads:[~2014-02-26 11:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26  9:35 Sascha Kilian
2014-02-26 10:24 ` Michael Tremer
2014-02-26 11:20   ` Sascha Kilian
2014-02-26 11:27     ` Michael Tremer
2014-02-26 11:33       ` Sascha Kilian [this message]

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=1393414407.2393.9.camel@localhost \
    --to=sascha@sakisoft.de \
    --cc=development@lists.ipfire.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