From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3002 invoked by alias); 16 Apr 2004 16:39:47 -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 2967 invoked from network); 16 Apr 2004 16:39:45 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sources.redhat.com with SMTP; 16 Apr 2004 16:39:45 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 09DFB47D63; Fri, 16 Apr 2004 09:39:45 -0700 (PDT) Date: Fri, 16 Apr 2004 16:39:00 -0000 From: Joel Brobecker To: gdb-patches@sources.redhat.com Subject: build failure due to observer.sh Message-ID: <20040416163944.GS1131@gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-SW-Source: 2004-04/txt/msg00357.txt.bz2 Hello, The build failed on most of our machines, due to a problem happening during the sed command in observer.sh. Here is the output we got: Creating observer.h-tmp sed: # Save original line for later processing into the actual parameter is not a recognized function. As a consequence, all observers are missing, and we fail during the link. I tried on AiX to remove the comments, to see if it works any better, and managed to get past this error. Are comments a GNU sed extension? In my opinion, I would handle observer.sh the same as gdbarch.sh: The contributors run it manually when needed. And we keep and up-to-date version of observer.[hc] checked in the repository. That way, we avoid requiring a certain implementation of sed when just building GDB. I can regenerate observer.[hc] and check them in, if you agree. -- Joel