RE: FW: MAX_PATH problems with mingw gcc

2013-10-27 Thread Vladimir Simonov
> -Original Message- > From: Joey Ye [mailto:joey.ye...@gmail.com] > Sent: Monday, October 21, 2013 6:31 AM > To: Vladimir Simonov; Ian Lance Taylor; d...@redhat.com > Vladimir, > > I found no more issue on patch itself. But ChangeLogs are missing. > Please refer to format in /include/Cha

Re: FW: MAX_PATH problems with mingw gcc

2013-10-20 Thread Joey Ye
Vladimir, I found no more issue on patch itself. But ChangeLogs are missing. Please refer to format in /include/ChangeLog, and generate yours in your next email for /include /libcpp /libiberty Maintainers of libiberty are in TO list. - Joey

RE: FW: MAX_PATH problems with mingw gcc

2013-10-19 Thread Vladimir Simonov
> -Original Message- > From: Joey Ye [mailto:joey.ye...@gmail.com] > Sent: Friday, October 18, 2013 6:37 AM > > I do encourage you to upstream this patch, though I'm not the maintainer of > libiberty to approve it. OK. Thank you. Here it is. Could you push it to appropriate people? Atta

Re: FW: MAX_PATH problems with mingw gcc

2013-10-17 Thread Joey Ye
On Thu, Oct 17, 2013 at 4:18 PM, Vladimir Simonov wrote: > > Thank you for pointing this problem. > > So, on file systems with symlinks support "playing" with filenames as strings > is impossible. > This means that filename_normalize name is too pretentious - it will do > nothing for most of gcc

RE: FW: MAX_PATH problems with mingw gcc

2013-10-17 Thread Vladimir Simonov
Thank you for review. Please see inline > From: Joey Ye [mailto:joey.ye...@gmail.com] > Sent: Thursday, October 17, 2013 7:36 AM > > The macro FILENAME_NORMALIZE doesn't look necessary. I would prefer use > filename_normalize directly, just as filename_cmp is used in GCC rather than > FILENAME

RE: FW: MAX_PATH problems with mingw gcc

2013-10-17 Thread Vladimir Simonov
> -Original Message- > From: Joey Ye [mailto:joey.ye...@gmail.com] > > There is an issue on file system with symbolic link, like Linux ext2/3. It > could vitally change behavior of GCC. The issue is described as following. > > Such a logic cannot be deduced simple from the name string,

Re: FW: MAX_PATH problems with mingw gcc

2013-10-16 Thread Joey Ye
On Wed, Oct 16, 2013 at 6:45 PM, Vladimir Simonov wrote: > There are many pro and contras, i.e. it adds additional, probably unnecessary > work on Linux > time but makes filenames shorter, it affects libiberty which is shared > between gcc/binutils/gdb, > but it may be useful in other packages,

Re: FW: MAX_PATH problems with mingw gcc

2013-10-16 Thread Joey Ye
Thanks for contribution. See review comments at following. On Wed, Oct 16, 2013 at 6:45 PM, Vladimir Simonov wrote: > Hi, > > Resending filename-normalize patch to correct list gcc-patches@gcc.gnu.org. > All context, please, see below. > > +extern void filename_normalize (char *f); > +#define FI

FW: MAX_PATH problems with mingw gcc

2013-10-16 Thread Vladimir Simonov
Hi, Resending filename-normalize patch to correct list gcc-patches@gcc.gnu.org. All context, please, see below. Regards Vladimir Simonov -Original Message- From: Vladimir Simonov Sent: Wednesday, October 16, 2013 12:52 PM To: 'Jiri Dobry'; 'gcc-h...@gcc.gnu.org' Subject: RE: MAX_PATH pr