From: <no...@so...> - 2000-11-27 13:17:12
|
Bug #123553, was updated on 2000-Nov-27 05:17 Here is a current snapshot of the bug. Project: MinGW - Minimalist GNU for Windows Category: gcc Status: Open Resolution: None Bug Group: None Priority: 5 Summary: Problem with common symbols Details: First off, please note that I'm using gcc 2.95.2 out-of-the-box, set up as a cross-compiler for mingw32 on a RedHat linux box, and a mingw32-targeted build of binutils 2.10.1 (also out-of-the-box). As such, this problem may not be present in a 'normal' mingw32 environment. The problem is with common symbols; if they're not explicitly disabled (using -fno-common), these cause serious problems. In particular, take GNU getopt. Its 'optarg' variable isn't initialized, causing it to be compiled as a common symbol. In the resulting executable, the getopt_long function assigns to optarg, but with no result; it stays NULL. As such, many applications are broken (they expect optarg to be non-NULL for an option with a required argument, and using the NULL pointer causes an access violation). Simply using -fno-common (or initialising all variables) solves this problem. So maybe -fno-common should be in the specs file. For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=123553&group_id=2435 |
From: <no...@so...> - 2000-11-27 15:29:13
|
Bug #123553, was updated on 2000-Nov-27 05:17 Here is a current snapshot of the bug. Project: MinGW - Minimalist GNU for Windows Category: gcc Status: Open Resolution: None Bug Group: None Priority: 5 Summary: Problem with common symbols Details: First off, please note that I'm using gcc 2.95.2 out-of-the-box, set up as a cross-compiler for mingw32 on a RedHat linux box, and a mingw32-targeted build of binutils 2.10.1 (also out-of-the-box). As such, this problem may not be present in a 'normal' mingw32 environment. The problem is with common symbols; if they're not explicitly disabled (using -fno-common), these cause serious problems. In particular, take GNU getopt. Its 'optarg' variable isn't initialized, causing it to be compiled as a common symbol. In the resulting executable, the getopt_long function assigns to optarg, but with no result; it stays NULL. As such, many applications are broken (they expect optarg to be non-NULL for an option with a required argument, and using the NULL pointer causes an access violation). Simply using -fno-common (or initialising all variables) solves this problem. So maybe -fno-common should be in the specs file. Follow-Ups: Date: 2000-Nov-27 07:29 By: earnie Comment: This is not our bug, please visit ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/gcc-2.95.2/patches/ for patches to apply. ------------------------------------------------------- For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=123553&group_id=2435 |
From: <no...@so...> - 2000-11-27 15:29:12
|
Bug #123553, was updated on 2000-Nov-27 05:17 Here is a current snapshot of the bug. Project: MinGW - Minimalist GNU for Windows Category: gcc Status: Closed Resolution: Invalid Bug Group: None Priority: 5 Summary: Problem with common symbols Details: First off, please note that I'm using gcc 2.95.2 out-of-the-box, set up as a cross-compiler for mingw32 on a RedHat linux box, and a mingw32-targeted build of binutils 2.10.1 (also out-of-the-box). As such, this problem may not be present in a 'normal' mingw32 environment. The problem is with common symbols; if they're not explicitly disabled (using -fno-common), these cause serious problems. In particular, take GNU getopt. Its 'optarg' variable isn't initialized, causing it to be compiled as a common symbol. In the resulting executable, the getopt_long function assigns to optarg, but with no result; it stays NULL. As such, many applications are broken (they expect optarg to be non-NULL for an option with a required argument, and using the NULL pointer causes an access violation). Simply using -fno-common (or initialising all variables) solves this problem. So maybe -fno-common should be in the specs file. Follow-Ups: Date: 2000-Nov-27 07:29 By: earnie Comment: This is not our bug, please visit ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/gcc-2.95.2/patches/ for patches to apply. ------------------------------------------------------- For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=123553&group_id=2435 |