All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: 2Marco Gerards (important info)
Date: Fri, 23 Sep 2005 15:46:25 +0200	[thread overview]
Message-ID: <87k6h7dhhq.fsf@student.han.nl> (raw)
In-Reply-To: <20050922224335.39699.qmail@web35308.mail.mud.yahoo.com> (Ruslan Nikolaev's message of "Thu, 22 Sep 2005 15:43:35 -0700 (PDT)")

Ruslan Nikolaev <nruslan_devel@yahoo.com> writes:

> Just want to inform you about other problems.
>  
> Please note that all other testings (expect for OBJCOPY) during
> configure _MUST_ BE DONE in 64-bit mode compiling. Otherwise I had
> problems with Linux w/o 32-bit support (there are problems with
> building because I haven't 32-bit libraries and so on).
>  
> OBJCOPY test can be done in 32-bit mode compiling. Otherwise i386 test
> will fail. There is no problems. It compiles properly in 32-bit mode
> even if you haven't 32-bit libraries.
>  
> FOR MORE INFO SEE MY PATCH. IT OVERRIDES CC and keep original value in
> CC_ARCH (for building utilities as 64-bit files) !!!!!!! AFTER ALL
> TESTINGS EXPECT "OBJCOPY test".

Most tests just test if it compiles.  AFAIK only the REGPARAM_BUG test
checks if it runs.  We can test for that.  But this is a bug not just
related to the AMD64, it is also the case when cross-compiling, I
think?  So this bug already exists, this is just one scenario that
triggers this bug, right?

> !!!!! It's really too hard to make patch without saving and restoring
> CC and LD because you also need to make configure tests for x86_64
> separately and more routine works.  That is why my patch just
> overrides settings and then restores settings for building utilities.

I am not sure about that yet.

I will check in my patch later this evening.  After that I will have a
look at the REGPARAM issue.  I will try to test if it will build on a
system without 32 bits libraries installed.

--
Marco




  reply	other threads:[~2005-09-23 13:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-20 23:10 [PATCH] new patch for amd64 Ruslan Nikolaev
2005-09-21 11:38 ` Yoshinori K. Okuji
2005-09-21 23:03   ` 2Yoshinori K. Okuji Ruslan Nikolaev
2005-09-21 13:07 ` [PATCH] new patch for amd64 Marco Gerards
2005-09-21 22:47   ` 2Marco Gerards Ruslan Nikolaev
2005-09-21 23:10     ` 2Marco Gerards (new) Ruslan Nikolaev
2005-09-22 18:16       ` Marco Gerards
2005-09-22 22:43         ` 2Marco Gerards (important info) Ruslan Nikolaev
2005-09-23 13:46           ` Marco Gerards [this message]
2005-09-24 22:17             ` 2Marco Gerards (answer) Ruslan Nikolaev

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=87k6h7dhhq.fsf@student.han.nl \
    --to=metgerards@student.han.nl \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.