Re: [Mingw-w64-public] import library overlap

2010-08-31 Thread Kai Tietz
2010/8/30 Chris Sutcliffe : > On 30 August 2010 11:23, Kai Tietz wrote: >> Well, this is a bit too much. Just make sure you specify on command >> line (at end, or before -lkernel32 - if you specify it - the option >> -ladvapi32. You can file a bug report for gcc, so I don't miss to >> modify it for

Re: [Mingw-w64-public] import library overlap

2010-08-30 Thread Chris Sutcliffe
On 30 August 2010 11:23, Kai Tietz wrote: > Well, this is a bit too much. Just make sure you specify on command > line (at end, or before -lkernel32 - if you specify it - the option > -ladvapi32. You can file a bug report for gcc, so I don't miss to > modify it for 4.6. Done: http://gcc.gnu.org/bu

Re: [Mingw-w64-public] import library overlap

2010-08-30 Thread Kai Tietz
2010/8/30 Chris Sutcliffe : > On 30 August 2010 10:42, Kai Tietz wrote: >> 2010/8/30 Chris Sutcliffe : >>> Is it possible to override / change the default link order (i.e. is it >>> in a config file somewhere), or is it hard coded at compile time? >> >> Well, this is a suggested default by gcc (IMH

Re: [Mingw-w64-public] import library overlap

2010-08-30 Thread Chris Sutcliffe
On 30 August 2010 10:42, Kai Tietz wrote: > 2010/8/30 Chris Sutcliffe : >> Is it possible to override / change the default link order (i.e. is it >> in a config file somewhere), or is it hard coded at compile time? > > Well, this is a suggested default by gcc (IMHO we should change here > order, or

Re: [Mingw-w64-public] import library overlap

2010-08-30 Thread Kai Tietz
2010/8/30 Chris Sutcliffe : > On 30 August 2010 10:21, Kai Tietz wrote: >> The issue you see here is related to the default import library order >> given by gcc. It uses "-luser32 -lkernel32 -ladvapi32 -lshell32" which >> leads here to the issue. IMHO kernel32 should come last here. >> Something li

Re: [Mingw-w64-public] import library overlap

2010-08-30 Thread Chris Sutcliffe
On 30 August 2010 10:21, Kai Tietz wrote: > The issue you see here is related to the default import library order > given by gcc. It uses "-luser32 -lkernel32 -ladvapi32 -lshell32" which > leads here to the issue. IMHO kernel32 should come last here. > Something like this is more correct "-lshell32

Re: [Mingw-w64-public] import library overlap

2010-08-30 Thread Kai Tietz
2010/8/30 Chris Sutcliffe : > On 30 August 2010 09:27, JonY wrote: >> On 8/30/2010 21:00, Chris Sutcliffe wrote: >>> The OpenProcessToken in particular has come to bite me in a bad way >>> with Emerge Desktop.  I ran in to this issue when using gendef to >>> update the def files for w32api, in that

Re: [Mingw-w64-public] import library overlap

2010-08-30 Thread Chris Sutcliffe
On 30 August 2010 09:27, JonY wrote: > On 8/30/2010 21:00, Chris Sutcliffe wrote: >> The OpenProcessToken in particular has come to bite me in a bad way >> with Emerge Desktop.  I ran in to this issue when using gendef to >> update the def files for w32api, in that I had to check for multiple >> ex

Re: [Mingw-w64-public] import library overlap

2010-08-30 Thread Kai Tietz
2010/8/30 JonY : > On 8/30/2010 21:00, Chris Sutcliffe wrote: >> The latest crt (at least the one in the Cygwin 'dist' release) has >> conflicting exports: >> >> csutc...@eush65 /usr/x86_64-w64-mingw32/sys-root/mingw/lib >> $ x86_64-w64-mingw32-nm.exe libadvapi32.a | grep -i OpenProc >> 000

Re: [Mingw-w64-public] import library overlap

2010-08-30 Thread JonY
On 8/30/2010 21:00, Chris Sutcliffe wrote: > The latest crt (at least the one in the Cygwin 'dist' release) has > conflicting exports: > > csutc...@eush65 /usr/x86_64-w64-mingw32/sys-root/mingw/lib > $ x86_64-w64-mingw32-nm.exe libadvapi32.a | grep -i OpenProc > T OpenProcessTo

[Mingw-w64-public] import library overlap

2010-08-30 Thread Chris Sutcliffe
The latest crt (at least the one in the Cygwin 'dist' release) has conflicting exports: csutc...@eush65 /usr/x86_64-w64-mingw32/sys-root/mingw/lib $ x86_64-w64-mingw32-nm.exe libadvapi32.a | grep -i OpenProc T OpenProcessToken I __imp_OpenProcessToken csutc..