From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1Rvt9F-0002bG-1Q for mharc-grub-devel@gnu.org; Fri, 10 Feb 2012 11:16:33 -0500 Received: from eggs.gnu.org ([140.186.70.92]:33679) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rvt97-0002XR-N4 for grub-devel@gnu.org; Fri, 10 Feb 2012 11:16:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rvt93-0001zq-H7 for grub-devel@gnu.org; Fri, 10 Feb 2012 11:16:25 -0500 Received: from mail-wi0-f169.google.com ([209.85.212.169]:37810) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rvt93-0001zm-BP for grub-devel@gnu.org; Fri, 10 Feb 2012 11:16:21 -0500 Received: by wibhj13 with SMTP id hj13so2707559wib.0 for ; Fri, 10 Feb 2012 08:16:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=iyfIJ2GbCRVybFglKowGFdzKvsckE4JOiRxoTOk8IuQ=; b=iw7TETGTkDPJUnifNCxXuCFXWojmnBaN/+v4aYyCor9aWwZcuSsudhQzSrIHFWepuq I2vUTvfp50eUBpJWSc4ESQ/lyiqn+7TuXom5aqmDb4kR3j2Ig3caad2+brqYyXvhXrvD Gh5VkgZgM7TyM5rEFvHL5hjttf2BLQJvBFU1Q= Received: by 10.180.100.33 with SMTP id ev1mr12848743wib.3.1328890580671; Fri, 10 Feb 2012 08:16:20 -0800 (PST) Received: from debian.x201.phnet (93-93.203-62.cust.bluewin.ch. [62.203.93.93]) by mx.google.com with ESMTPS id cs4sm19260562wib.8.2012.02.10.08.16.18 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 10 Feb 2012 08:16:19 -0800 (PST) Message-ID: <4F3542D2.7000304@gmail.com> Date: Fri, 10 Feb 2012 17:16:18 +0100 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120104 Icedove/8.0 MIME-Version: 1.0 To: grub-devel@gnu.org Subject: Re: Various build failures in current bzr tree References: <20120209190204.GW27742@caffeine.csclub.uwaterloo.ca> <20120209193301.GX27742@caffeine.csclub.uwaterloo.ca> <20120209205045.GY27742@caffeine.csclub.uwaterloo.ca> In-Reply-To: <20120209205045.GY27742@caffeine.csclub.uwaterloo.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.212.169 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2012 16:16:31 -0000 On 09.02.2012 21:50, Lennart Sorensen wrote: > On Thu, Feb 09, 2012 at 02:33:01PM -0500, Lennart Sorensen wrote: >> On Thu, Feb 09, 2012 at 02:02:04PM -0500, Lennart Sorensen wrote: >>> I am trying to build a powerpc build using the current bzr tree, and >>> have hit a few problems so far. >>> >>> I am trying to use gcc-4.4, which seems to cause issues with -Werror. >>> I think that is gcc's fault, and --disable-werror gets around that, >>> so not a big deal. >>> >>> I am hitting bug #35452 of course caused by commit r3826, but even after >>> fixing that, commit r38xx does the same thing to another set of files. >>> >>> I also hit that grub_arch_dl_get_tramp_got_size isn't defined. It appears >>> it was cleaned up for powerpc as being unused recently, but dl.c still >>> says that powerpc has it (along with ia64). Removing powerpc from: >>> >>> #if defined (__ia64__) || defined (__powerpc__) >>> grub_arch_dl_get_tramp_got_size (e,&tramp,&got); >>> >>> seems to fix that. >>> >>> Should I file bug reports, or will someone just fix these? >> grub-probe prints 'raid' rather than 'diskfilter' for the modulename to >> use when raid is in use. > grub-install also still (as reported about 2 years ago) tries to use > $grub_device rather than $install_device when getting the partition > table type. This is not an error. (see other mail) install_device is only read from by firmware to locate the core. GRUB uses it only to infer root if $grub_device and $install_device refer to the same disk but $install_device isn't used otherwise by GRUB runtime. Please detail symptoms if any. If none, this is a non-issue. > > However, I did now manage to boot after fixing that. > > So there is a chance I can make a patch to fix grub-install soon so it > actually works on IBM power systems. Given I have a production machine > and a new machine around for a few days I can experiment until it > is right. > -- Regards Vladimir 'φ-coder/phcoder' Serbinenko