From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1WP9oZ-0008Ul-8w for mharc-grub-devel@gnu.org; Sun, 16 Mar 2014 08:05:15 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48567) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WP9oT-0008NR-9s for grub-devel@gnu.org; Sun, 16 Mar 2014 08:05:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WP9oO-00026l-AI for grub-devel@gnu.org; Sun, 16 Mar 2014 08:05:09 -0400 Received: from mail-wg0-x22d.google.com ([2a00:1450:400c:c00::22d]:52992) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WP9oO-00022U-00 for grub-devel@gnu.org; Sun, 16 Mar 2014 08:05:04 -0400 Received: by mail-wg0-f45.google.com with SMTP id l18so3729877wgh.16 for ; Sun, 16 Mar 2014 05:05:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Jyn8hO3Qduo4zcNGbLUNy21ayxZ3EuUdadv8KN1xPSY=; b=FKWHUxId1Ka+zcRaMCy4kG8slcGp8aXtLdOEJf0RF7R3VwGzZfbs3U5XAfCkpBYeHH eDXU9wgGSz7bKeivdbjzhFmRaa3QHI12BGXl++erl+lHIyHsXheO8fT9HWYZ2FRhxC82 /H/O2Q2cYGdOXtxx6rUaVBGr/yv6D4a46xUavYPu38B4O4JpQpMFzbO1I7FvG5uOePsc Pc9WFwtftxHSZ+6k6ldv+ibiu+m72r+8gevH/jbUdKLSnXRdsKB/y2eN6XcEspSEmeKM Hc8Tx+HXKKodvQkmL79U68bPB8tKbysx9pSwWZt7BE1jTT6OGPi7D+1gIkqiFWix2Eh5 /2CA== X-Received: by 10.180.105.65 with SMTP id gk1mr5691633wib.12.1394971503017; Sun, 16 Mar 2014 05:05:03 -0700 (PDT) Received: from [192.168.10.45] (136.Red-88-21-16.staticIP.rima-tde.net. [88.21.16.136]) by mx.google.com with ESMTPSA id h9sm29090219wjz.16.2014.03.16.05.05.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 16 Mar 2014 05:05:02 -0700 (PDT) Message-ID: <5325936C.1020501@gmail.com> Date: Sun, 16 Mar 2014 13:05:00 +0100 From: adrian15 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.3.0 MIME-Version: 1.0 To: Andrey Borzenkov Subject: Re: Trying to build Rescue image for three different target and platform References: <531C934C.5070501@gmail.com> <20140313095128.74e85778@opensuse.site> <53253D1E.5030107@gmail.com> <20140316110428.5714ce94@opensuse.site> In-Reply-To: <20140316110428.5714ce94@opensuse.site> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::22d Cc: The development of GNU GRUB 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: Sun, 16 Mar 2014 12:05:14 -0000 El 16/03/14 08:04, Andrey Borzenkov escribió: > В Sun, 16 Mar 2014 06:56:46 +0100 > adrian15 пишет: > >>> >>> To be honest, I do not understand what you are trying to do here. >> >> The same thing as in: >> >> https://forja.cenatic.es/plugins/scmgit/cgi-bin/gitweb.cgi?p=supergrub2/supergrub2.git;a=blob_plain;f=supergrub-meta-mkrescue;hb=22683e2b5fa0d65141c1be1a7487914b1d43f4dd >> >> (which uses Debian packages) but using source code. >> > > Why would you want to build separate ISO for every platform? The whole > point of using grub-mkrescue is to create single ISO image that > supports and can be booted on all platforms. Because I want to support all the GRUB2 platforms but not having a single 60 MB (random size guess) download for that. The other reason is because a: i386-efi + x86_64_efi + x86_pc hybrid did not boot in a x86_64_efi only system. Right now I'm not sure if I built it from source or if I made the iso with Debian binaries but, what it's sure is that it did not boot at all. It just hung. So I want a separate ISO for every platform. > >> >>>> 8) What's the best way to build and install an hybrid system that >>>> includes both: x86_64_efi and i386 - pc stuff? >>>> >>> >>> Just built and install grub for each platform you want to use; >>> grub-mkrescue will automatically include every platform it finds. >> >> Any advice for the special where I want to build x86_64_efi + x86_pc >> hybrid disk? >> > > Not really. Just build and install both platforms using the same prefix > and run grub-mkrescue that is build to use the same prefix. Ok. > > As mentioned, when building you should distinguish between host (grub > utils) and target (boot time). It is perfectly valid to build utils for > x86 and target for ARM as long as you have suitable cross tools. In > your case all builds should use the same host (which defaults to target > which may be wrong even for x86 case - consider 32 vs. 64 bit). > > See INSTALL how to set various options for each environment. Ok,I'll check that. > >>> >>> I prefer to build every platform in separate directory, there were >>> issues with incomplete cleanup. If you hit one, please report. >> >> Well, as I don't want to have a separate directory for each build my >> question would be: >> >> What is it the official commands for doing a safe cleanup? >> > > I always used "make distclean". But IIRC there are some files that are > not removed. Not sure to which extent they affect subsequent builds. I > had problems when re-building on Windows but they should be fixed now. > > From my point of view, "make distclean" is official and if it does not > work it is a bug that has to be fixed. make distclean . Written down. > >> >>> >>>> 9) A) What's the best way to remove grub configuration files installed >>>> on the system so that I can start from scratch so that already built >>>> target+platform grub binaries or configurations are ignored? >>>> >>> >>> There are no configuration files after "make install" (if we do not >>> count /etc/grub.d as configuration). >> >> I meant the ones that someone makes grub-mkrescue to look for the >> /usr/local/lib/grub/i386-pc/boot_hybrid.img files which I suppose are >> not found in source code but in the system (Gnu/Linux filesystem I mean). >> > > There are no special configuration files. If grub-mkrescue is called > without --directory option, it will enumerate all platforms found > under /usr/local/lib/grub (in your example). Just place additional > platform directory there and grub-mkrescue will pick it up. So I just need to purge the /usr/local/lib/grub contents so that I can start again without the fear of grub-mkrescue picking up an earlier built platform (That's what I tried to achieve before with make uninstall by the way). That's exactly what I wanted to know. Thank you very much! I do not know when I will be able to try all of this but now it's much more clear everything and I'll be able to report GRUB build errors (or runtime) more easily for my special use case. adrian15 -- Support free software. Donate to Super Grub Disk. Apoya el software libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/