From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27877 invoked by alias); 26 May 2003 19:41:55 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 24818 invoked from network); 26 May 2003 19:40:21 -0000 Received: from unknown (HELO localhost.localdomain) (207.236.65.94) by sources.redhat.com with SMTP; 26 May 2003 19:40:21 -0000 Received: from localhost.redhat.com ([10.2.246.247]) by localhost.localdomain (8.11.6/8.11.6) with ESMTP id h4QJeIa08669 for ; Mon, 26 May 2003 15:40:18 -0400 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 393EA2B2F; Mon, 26 May 2003 15:40:06 -0400 (EDT) Message-ID: <3ED26D96.9060306@redhat.com> Date: Mon, 26 May 2003 19:41:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andreas Schwab Cc: gdb-patches@sources.redhat.com Subject: PREPARE_TO_PROCEED; Was: More multi-arch and cleanups for m68k-linux References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg00486.txt.bz2 > The only thing that prevents m68k-linux from advancing to multi-arch > level 2 is the PREPARE_TO_PROCEED definition in config/nm-linux.h. > How can this be multi-arched given that this is a native-only thing? I _think_ the current plan is along the lines of make generic_prepare_proceed(?) the default, and leave HP/UX as the exception. Does the generic version work on GNU/Linux? (Hmm??? nothing appears to currently use it!) Andrew