From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20967 invoked by alias); 20 Mar 2013 18:48:16 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 20913 invoked by uid 89); 20 Mar 2013 18:48:03 -0000 X-Spam-SWARE-Status: No, score=-3.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.1 Received: from oarmail.oarcorp.com (HELO OARmail.OARCORP.com) (67.63.146.244) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Wed, 20 Mar 2013 18:48:00 +0000 Received: from [10.253.80.126] (130.207.218.197) by OARmail.OARCORP.com (192.168.2.2) with Microsoft SMTP Server (TLS) id 8.2.255.0; Wed, 20 Mar 2013 13:47:58 -0500 Message-ID: <514A045A.8070007@oarcorp.com> Date: Wed, 20 Mar 2013 18:48:00 -0000 From: Joel Sherrill User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Mike Frysinger CC: Ralf Corsepius , "gdb@sourceware.org" Subject: Re: [gdb-7.5.91] mips sim fails to build on mingw32 References: <5evvfpyhuvbs9ftm3edxb7na.1363372668425@email.android.com> <201303181405.55098.vapier@gentoo.org> <5149F70C.3040806@oarcorp.com> <201303201433.15976.vapier@gentoo.org> In-Reply-To: <201303201433.15976.vapier@gentoo.org> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2013-03/txt/msg00055.txt.bz2 On 3/20/2013 1:33 PM, Mike Frysinger wrote: > On Wednesday 20 March 2013 13:51:08 Joel Sherrill wrote: >> FYI you have to have bfin as installed to compile the simulator. I >> suppose this >> has never been noticed. > i'm guessing you're referring to the assembly of some fixed code file ? that > happens when timestamps get out of whack. i originally just wanted to add a > .h, but people requested i also add the source .s. > > not sure if there's a way i could put this logic behind "if (file does not > exist) || (file is out of date && maintainer mode)" so it doesn't bite people > randomly ... I think it may have been with the gdb-7.5.91 snapshot. Maybe the timestamp wasn't right. I am in a virtual machine and maybe my time of day was messed up at the time. >> Can I put a generic message for other targets that "dv-sockser hardware >> support is >> unavailable for your target" and let it go at that? Or do I specifically >> need to list the >> devices when dv-sockser.o is hard-coded in the Makefile.in? > since we don't have a large body of people clamoring for sim device support > under Windows, let's start with the simple version and avoid hardcoded lists. OK. Separate message with proposed addition to those configure.ac's. >>> and then add a TODO comment to each of these failing device modules with >>> something like "should change code to respect HAVE_DV_SOCKSER". >> What would such a message look like and where in the file would it go? > i was thinking of a /* TODO: ... */ in each device model file that > unconditionally uses dv-socker. e.g. sim/mips/dv-tx3904sio.c. OK. This is at the bottom of my list. I think I am getting run over by the squeaky wheel that I reported. :) > -mike -- Joel Sherrill, Ph.D. Director of Research & Development joel.sherrill@OARcorp.com On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985