public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: m.postman@lefog.net
To: development@lists.ipfire.org
Subject: Re: Building IPFire Howto - Wannabe Error
Date: Thu, 03 Oct 2013 21:56:14 +0200	[thread overview]
Message-ID: <524DCBDE.4070602@lefog.net> (raw)
In-Reply-To: <524DCB23.1080109@lefog.net>

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

BTW: I successfully used OpenSUSE 12.3 if you want to update this into 
the wiki :)

Am 03.10.2013 21:53, schrieb m.postman(a)lefog.net:
> Hey,
> i spend a week to find the reason for the follwing error when running
> # linux32 ./make.sh build'' to build ipfire-2.x.
>
> hplip                                      [     3.12.6 ]            [
>   2 ] [ DONE ]
> transmission                                      [       2.81
> ]            [  1 ] [ DONE ]
> mtr                                      [       0.82 ]            [  0
> ] [ DONE ]
> tor                                      [   0.2.3.25 ]            [  3
> ] [ DONE ]
> mysql                                      [    5.0.24a ]            [
>   8 ] [ DONE ]
> mpfire                                      [     ipfire ]            [
>   0 ] [ DONE ]
> icegenerator                                      [ 0.5.5-pre2
> ]            [  1 ] [ DONE ]
> ls: cannot access *.bz2: No such file or directory
> ls: cannot access *.img.gz: No such file or directory
> Generating files list from logs
>       [ DONE ]
> *** Checking Logfiles for new Files (Last stage took 588 secs)
>                                             version   options    time
> (sec)   status
> ***Build is finished now and took 3 hour(s) 54 minute(s) 35 second(s)!
>
> These two lines indicated an incomplete build in my eyes.
> ls: cannot access *.bz2: No such file or directory
> ls: cannot access *.img.gz: No such file or directory
>
> Finally I found out that the message is caused by
> https://github.com/ipfire/ipfire-2.x/blob/master/make.sh#L876
> and doesn't mean anything bad :D
>
> I just wanted to let you (and hopefully any googlers with the same
> problem) know ;)
> Maybe (if you have too much free time ;P) you can fix this message, but
> I don't think that's urgent ;)
>
> Thank you for your great work!
> Marc
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
>


  reply	other threads:[~2013-10-03 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 19:53 m.postman
2013-10-03 19:56 ` m.postman [this message]
2013-10-04 14:22   ` Michael Tremer

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=524DCBDE.4070602@lefog.net \
    --to=m.postman@lefog.net \
    --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