Re: Relocation patch for cygwin

2011-10-12 Thread Charles Wilson
On 10/5/2011 8:10 AM, Bruno Haible wrote: > Charles Wilson wrote: >> The problem is, it can really cause issues for "the rest of cygwin" if >> an app uses the Win32 API "behind cygwin's back". > > I understand all that. I'm only saying that > - My need was to have the file name behind one partic

Re: Relocation patch for cygwin

2011-10-05 Thread Bruno Haible
Charles Wilson wrote: > > Only it's a pity that you gave me the advice to use Cygwin's > > /proc/self/maps, > > which I did [2], and now we discover that it is much slower than the Win32 > > API calls that I had originally. > ... > The problem is, it can really cause issues for "the rest of cygwin

Re: Relocation patch for cygwin

2011-10-04 Thread Charles Wilson
On 10/3/2011 7:26 AM, Bruno Haible wrote: > I'm applying this change to gnulib, from where it will propagate to libiconv > and libintl. I really don't think this is the right approach. See below. > Only it's a pity that you gave me the advice to use Cygwin's /proc/self/maps, > which I did [2], an

Re: Relocation patch for cygwin

2011-10-03 Thread Bruno Haible
Charles Wilson wrote: > On 9/26/2011 6:00 PM, Bruno Haible wrote: > > It is normal that --enable-relocatable has a runtime cost. Certainly when > > you apply --enable-relocatable to small, fast programs like 'id' or 'pwd' > > the runtime cost will be more perceivable than with programs which run >

Re: Relocation patch for cygwin

2011-09-29 Thread Charles Wilson
On 9/26/2011 6:00 PM, Bruno Haible wrote: > It is normal that --enable-relocatable has a runtime cost. Certainly when > you apply --enable-relocatable to small, fast programs like 'id' or 'pwd' > the runtime cost will be more perceivable than with programs which run > for longer than 1 second on av

Re: Relocation patch for cygwin

2011-09-26 Thread Bruno Haible
[Dropping cygwin list from CC.] Charles Wilson wrote: > > in cygwin libintl is expected to place in /bin so there's no use > > of relocatable. > > Right, and it is intended that, in the cygwin official packages, both > libiconv and libintl are built without relocation support. If that > isn't tr

Re: Relocation patch for cygwin

2011-09-25 Thread Charles Wilson
On 9/23/2011 4:10 PM, jojelino wrote: > It fixed the relocation problem. but led performance issue :( > > $ time id > /dev/null > > real0m0.141s > user0m0.000s > sys 0m0.000s Well, the libiconv distributed as an official cygwin package *SHOULD* not have been built with --enable-reloc

Re: Relocation patch for cygwin

2011-02-28 Thread Charles Wilson
On 2/28/2011 5:23 PM, Bruno Haible wrote: > Thanks for the reminder. Three weeks ago, I concentrated on discussing the > support of UCS-4 characters (still working on that). I've added minor tweaks > (especially so as to avoid mixing the Win32 and the Cygwin approach), and > committed this: Thanks

Re: Relocation patch for cygwin

2011-02-28 Thread Bruno Haible
Hi Chuck, > Ping? Thanks for the reminder. Three weeks ago, I concentrated on discussing the support of UCS-4 characters (still working on that). I've added minor tweaks (especially so as to avoid mixing the Win32 and the Cygwin approach), and committed this: 2011-02-28 Corinna Vinschen(ti

Re: Relocation patch for cygwin

2011-02-27 Thread Charles Wilson
On 1/28/2011 1:04 PM, Charles Wilson wrote: > 2011-01-27 Corinna Vinschen <...> > Charles Wilson <...> > > On Cygwin, use unix mechanisms instead of win32 > * progreloc.c: Prefer linux code throughout, rather than > win32 implementations. > (find_executable):

Relocation patch for cygwin

2011-01-28 Thread Charles Wilson
On the cygwin list, Corinna Vinschen, one of the main cygwin developers and project lead, noticed a problem with libiconv's behavior on cygwin 1.7.x (which I'll follow up on the appropriate list, in a few days). However, while she was investigating it, she ran across some very obsolete code in the