From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id DBC7421F14D for ; Fri, 21 Sep 2012 15:16:04 -0700 (PDT) Received: by wibhm2 with SMTP id hm2so1989476wib.10 for ; Fri, 21 Sep 2012 15:16:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=IIMfhcSnOBGTtVjN7tdvMGqoe0SERNQFBEharaZLCcw=; b=mdsS3MBgxwQ3jQju28tZ4viQOa4DeQ8tsEEPb76TsPDTDG5KJxasFHjooc8BzfaYxE w0jzDpBbIpOTkw6Fq3QoxpdhEhfcDmRjn5zPT0H9D0JpucZKx8GlbEWmSNwFwcwzAqbM nImI731ZtJjMPsa+4XWZ9+irX3xVbvqPm8B3JXZHdnaeAqd5KJOd8dXqu4N6532ZOWEk pj2vrhsGSeoi3kXWCmFXB1bLccxf5ZaVh1SvlVLm/I/5VCfQfuUUMUPG/bXoKPlTYvAX OCNXGCBJWJpjPTpB7RQwt+2V+LMMiTkPgixsYzhS6fYsb50Gm9wG6k+gty4V3om89qRl E0gg== MIME-Version: 1.0 Received: by 10.216.197.104 with SMTP id s82mr3418828wen.62.1348265763035; Fri, 21 Sep 2012 15:16:03 -0700 (PDT) Received: by 10.223.89.136 with HTTP; Fri, 21 Sep 2012 15:16:02 -0700 (PDT) In-Reply-To: <505AC149.2000905@googlemail.com> References: <505AC149.2000905@googlemail.com> Date: Fri, 21 Sep 2012 15:16:02 -0700 Message-ID: From: Dave Taht To: Oliver Niesner Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: cerowrt-devel@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] understanding_cerowrt_buildsystem X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Sep 2012 22:16:05 -0000 On Thu, Sep 20, 2012 at 12:10 AM, Oliver Niesner wrote: > Hi! > > After a zillion tries i managed to build a cerowrt image for myself. > It's not really clear what happened when it fails, but sometimes building= a > package again does the trick. When doing parallel builds, things can fail in random places as not all the dependencies are captured in openwrt. Also I've seen an issue when sometimes a file doesn't get built right and fails a dependency later. make package/{clean,compile,install}/the_package/name is usually of help in both cases. Sometimes merely doing a sequential build after a parallel build fails is the only answer, too make V=3Ds > Here is another question to understand better: > > When building a package (eg. selecting a new one in menuconfig) does the > buildsystem take care of > dependencies in other "parts" of the system? Let's say i do a package whi= ch > requires something new > must be build in the linux kernel, but in the build before the kernel is > already succesfully compiled. Will the > buildsystem automatically detect that it is neccessary to build the kerne= l > again, or do i have to do it > manually, eg. do a "make clean"? My guess is that i have to do it manuall= y. Often it will "just work". But not often enough. > Thanks, for clearing things up > > Oliver > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel --=20 Dave T=E4ht http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out with fq_codel!"