From: Paarvai N. <ope...@gm...> - 2010-06-30 21:00:37
|
Hi, I want to gain an understanding for the reasoning behind the "libtool_patch" function used in the "Custom toolchain builds" distributed by Ozkan Sezer. I don't see this mentioned in the standard cross-compiler instructions found on the mingw-w64 project page: http://sourceforge.net/apps/trac/mingw-w64/wiki/Cross%20Win32%20and%20Win64%20compiler But this libtool patch is used consistently for a number of the upstream sources. Can someone explain the rationale behind this? Thanks in advance! Paarvai |
From: Ozkan S. <se...@gm...> - 2010-06-30 21:07:47
|
On Thu, Jul 1, 2010 at 12:00 AM, Paarvai Naai <ope...@gm...> wrote: > Hi, > > I want to gain an understanding for the reasoning behind the > "libtool_patch" function used in the "Custom toolchain builds" > distributed by Ozkan Sezer. > > I don't see this mentioned in the standard cross-compiler instructions > found on the mingw-w64 project page: > http://sourceforge.net/apps/trac/mingw-w64/wiki/Cross%20Win32%20and%20Win64%20compiler > > But this libtool patch is used consistently for a number of the > upstream sources. Can someone explain the rationale behind this? It fixes libtool for proper win64 support. Upgrading to new libtool may not be trivial, but the fix itself is. Not every source need that fix, but applying it doesn't hurt either. Some libraries may not even compile without it (libxml2 comes to mind, can't remember else at the moment.) > > Thanks in advance! > Paarvai -- Ozkan |
From: Paarvai N. <ope...@gm...> - 2010-06-30 23:00:23
|
Hi Ozkan, Sorry to bug you, but can you give a little more explanation on how libtool is used by the configure script for -w64- support and why not having this fix will break things? I think it might be a good general education not only for me but for others on the group. Thanks again, Paarvai On Wed, Jun 30, 2010 at 2:07 PM, Ozkan Sezer <se...@gm...> wrote: > On Thu, Jul 1, 2010 at 12:00 AM, Paarvai Naai <ope...@gm...> wrote: >> Hi, >> >> I want to gain an understanding for the reasoning behind the >> "libtool_patch" function used in the "Custom toolchain builds" >> distributed by Ozkan Sezer. >> >> I don't see this mentioned in the standard cross-compiler instructions >> found on the mingw-w64 project page: >> http://sourceforge.net/apps/trac/mingw-w64/wiki/Cross%20Win32%20and%20Win64%20compiler >> >> But this libtool patch is used consistently for a number of the >> upstream sources. Can someone explain the rationale behind this? > > It fixes libtool for proper win64 support. Upgrading to new libtool > may not be trivial, but the fix itself is. Not every source need that > fix, but applying it doesn't hurt either. Some libraries may not even > compile without it (libxml2 comes to mind, can't remember else at > the moment.) > >> >> Thanks in advance! >> Paarvai > > -- > Ozkan > |
From: Ozkan S. <se...@gm...> - 2010-07-01 05:42:10
|
On Thu, Jul 1, 2010 at 2:00 AM, Paarvai Naai <ope...@gm...> wrote: > Hi Ozkan, > > Sorry to bug you, but can you give a little more explanation on how > libtool is used by the configure script for -w64- support and why not > having this fix will break things? > Libtool < 2.2.6/2.2.7 may not detect w64 libraries properly so the linkage would fail. Please look at what the patch does: it just updates the pe-x86_64 magic that is already in libtool 2.2.7. > I think it might be a good general education not only for me but for > others on the group. > > Thanks again, > Paarvai > -- Ozkan > > On Wed, Jun 30, 2010 at 2:07 PM, Ozkan Sezer <se...@gm...> wrote: >> On Thu, Jul 1, 2010 at 12:00 AM, Paarvai Naai <ope...@gm...> wrote: >>> Hi, >>> >>> I want to gain an understanding for the reasoning behind the >>> "libtool_patch" function used in the "Custom toolchain builds" >>> distributed by Ozkan Sezer. >>> >>> I don't see this mentioned in the standard cross-compiler instructions >>> found on the mingw-w64 project page: >>> http://sourceforge.net/apps/trac/mingw-w64/wiki/Cross%20Win32%20and%20Win64%20compiler >>> >>> But this libtool patch is used consistently for a number of the >>> upstream sources. Can someone explain the rationale behind this? >> >> It fixes libtool for proper win64 support. Upgrading to new libtool >> may not be trivial, but the fix itself is. Not every source need that >> fix, but applying it doesn't hurt either. Some libraries may not even >> compile without it (libxml2 comes to mind, can't remember else at >> the moment.) >> >>> >>> Thanks in advance! >>> Paarvai >> >> -- >> Ozkan >> > |
From: Paarvai N. <ope...@gm...> - 2010-07-01 17:28:52
|
Hi Ozkan, > Libtool < 2.2.6/2.2.7 may not detect w64 libraries properly so the > linkage would fail. Please look at what the patch does: it just updates > the pe-x86_64 magic that is already in libtool 2.2.7. While I have been developing code and compiling open source projects for a long time, I am not so familiar with exact flow for libtool (and automake and friends). This might be for the better. :) Consequently, the patch was not (and still is not) so obvious to me. My understanding is that the patch is required for building target code that links to pe-x86_64 libraries when the build process is tied to libtool. At the end of the day, once I build binutils, gcc, and mingw-w64-crt, I use my -w64- cross-compiler with a build system that is not dependent on libtool. Therefore, my guess is that the patch is not necessary, but applying it would not cause any harm either (of course). Is this correct? Thanks, Paarvai |
From: Ozkan S. <se...@gm...> - 2010-07-01 17:46:20
|
On Thu, Jul 1, 2010 at 8:28 PM, Paarvai Naai <ope...@gm...> wrote: > Hi Ozkan, > >> Libtool < 2.2.6/2.2.7 may not detect w64 libraries properly so the >> linkage would fail. Please look at what the patch does: it just updates >> the pe-x86_64 magic that is already in libtool 2.2.7. > > While I have been developing code and compiling open source projects > for a long time, I am not so familiar with exact flow for libtool (and I don't say that I'm much familiar with it either ;) > automake and friends). This might be for the better. :) > Consequently, the patch was not (and still is not) so obvious to me. > > My understanding is that the patch is required for building target > code that links to pe-x86_64 libraries when the build process is tied > to libtool. At the end of the day, once I build binutils, gcc, and > mingw-w64-crt, I use my -w64- cross-compiler with a build system that For them, it is not necessary, they have a properly updated libtool (and mingw-w64-crt doesn't even use libtool) > is not dependent on libtool. Therefore, my guess is that the patch is > not necessary, but applying it would not cause any harm either (of > course). Is this correct? > Yes > Thanks, > Paarvai > -- Ozkan |