From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8408 invoked by alias); 28 Mar 2009 18:14:07 -0000 Received: (qmail 7394 invoked by uid 48); 28 Mar 2009 18:13:52 -0000 Date: Sat, 28 Mar 2009 18:14:00 -0000 Message-ID: <20090328181352.7393.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/39570] cabs and cabsf are named differently on NetBSD 5 In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "aran at 100acres dot us" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-03/txt/msg01970.txt.bz2 ------- Comment #7 from aran at 100acres dot us 2009-03-28 18:13 ------- (In reply to comment #5) > Another fix is to #undef TARGET_C99_FUNCTIONS as obviously netbsd is another > OS without a clue ... > Please explain how an OS with a clue would handle this problem. Older binaries that use the pre-c99 complex structure links to the existing linker symbols, cabs and cabsf. Changing the meaning of these symbols to the c99 meaning would break these legacy programs. It seems cluefull to decorate these symbols with __c99_ and provide a rename in the header. What would be a better solution? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39570