|
From: Paul G. <pga...@te...> - 2000-12-14 01:01:45
|
Hi folks, Looks like we need to clarify what exactly constitutes a "bug", technically speaking. It is clear that anyone who is subscribed to this list already knows what a "bug report" is and what such things should look like. ------- Forwarded message follows ------- To: fu...@is..., Pau...@te..., min...@so... From: no...@so... Date sent: Wed, 13 Dec 2000 14:58:32 -0800 Subject: [Mingw-notify] [Bug #124561] search-path for include files Send reply to: no...@so... This list is used to send updates of submitted patches, bug reports and file releases. You are discouraged from posting to this list. If you wish to unsubscribe you can do so at http://lists.sourceforge.net/mailman/listinfo/mingw-notify.Bug #124561, was updated on 2000-Dec-05 08:08 Here is a current snapshot of the bug. Project: MinGW - Minimalist GNU for Windows Category: gcc Status: Open Resolution: Invalid Bug Group: None Priority: 5 Submitted by: fusz Assigned to : pfalcon Summary: search-path for include files Details: <main>/mingw32/include is not in the search-path for < ..>include files. But the path <main>/i386-mingw32msvc/include, which is not in alpha-release in the search-path. [this looks like a configuration problem on the end-users side.] [to continue] ------------------------------------------------------- Date: 2000-Dec-06 05:31 By: fusz Comment: If I start gcc like this: gcc -v -c hello.c I get a output with the following lines: ............ #include <...> search starts here: E:/Creat/MinGw/Bin/../lib/gcc- lib/mingw32/2.95.2/../../../../inc lude E:/Creat/MinGw/Bin/../lib/gcc- lib/mingw32/2.95.2/../../../../i38 6-mingw32msvc/include E:/Creat/MinGw/Bin/../lib/gcc-lib/mingw32/2.95.2/include End of search list. The following default directories have been omitted from the search path: /gcc-2.95.2/lib/gcc-lib/i386- mingw32msvc/2.95.2/../../../../incl ude/g++-3 /usr/local/i386-mingw32/include End of omitted list. [This seems to confirm my theory, the person sumitting this is unsure about what constitutes a "bug". I am thinking that if this is Georg Fusz, that he may misunderstand the mailing list policies, or it could be that the patch submittal process is not fulfilling its function properly. This report, as any bug report, should've gone to mingw-patches AND mingw-notify, not just to mingw-notify.] ............... ------------------------------------------------------- Date: 2000-Dec-05 13:56 By: pfalcon Comment: Not in search path for what? How do you know that in the first place? Don't conceal this information, I really like to know! [You're not the only one who is confused here, Paul S., it is confusing to me, too.] Peace, Paul G. Nothing real can be threatened. Nothing unreal exists. |