This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [ITP] mingw-w64 Second try


On 9/1/2010 11:44 AM, JonY wrote:
> On 9/1/2010 23:15, Charles Wilson wrote:
>> On 8/31/2010 11:20 PM, JonY wrote:
>>> On 9/1/2010 10:28, Charles Wilson wrote:
>>>> On 8/31/2010 8:52 PM, JonY wrote:
>>>>> Strange, I'll try a rebuild. The former should be the correct
>>>>> location.
>>>>
>>>> Errr...no. The *latter* is the correct location (at least, that's where
>>>> the sysroot'ed compiler will look for them).
>>>>
>>>> the (buggy) cygport(1) puts them in
>>>> usr/x86_64-w64-mingw32/sys-root/mingw/x86_64-w64-mingw32/include/
>>>> but we really want them to be in
>>>> usr/x86_64-w64-mingw32/sys-root/mingw/include/
>>>> which is what your cygport(5) does -- when you actually use it to
>>>> rebuild.
>>>>
>>>
>>> Right, the latter is correct. I'm misreading it.
>>
>> Given the results of the thread re: Possible cygport bug with cross
>> compiles (e.g. there is no bug), it looks like:
>>
>> 1) rebuild the -header package so that the includes end up in the
>> "correct" location. The current cygport(5) for that package is fine
>> (e.g. (a) the extra rule in src_install is needed, and proper, and (b)
>> it does the right thing)
>>
> 
> I am getting a permission denied error that I wasn't aware of before. I
> have fixed the mv command, and tested with "cygport compile install
> list", cyport list does show the correct locations. Tarball reuploaded.
> 
>> 2) fix the setup.hints
>>
> 
> Does setup.hint itself (for mingw64-x86_64-gcc-core) need an
> external-source link to mingw64-x86_64-gcc?

Well, you'd actually need two setup.hints:

   mingw64-x86_64-gcc/
     mingw64-x86_64-gcc-4.5.1-1-src.tar.bz2
(1)  setup.hint
     mingw64-x86_64-gcc-core/
       mingw64-x86_64-gcc-core-4.5.1-1.tar.bz2
(2)    setup.hint
     mingw64-x86_64-gcc-fortran/
       mingw64-x86_64-gcc-fortran-4.5.1-1.tar.bz2
       setup.hint
     mingw64-x86_64-gcc-g++/
       mingw64-x86_64-gcc-g++-4.5.1-1.tar.bz2
       setup.hint
     mingw64-x86_64-gcc-ada/
       mingw64-x86_64-gcc-ada-4.5.1-1.tar.bz2
       setup.hint

The one marked (1) would not need any requires: or external-source:
marking.  The one marked (2) would only need an external-source:
marking.  The others would all need both an external-source AND a
requires: mingw64-x86_64-gcc-core marking.

I think this also means you need to modify your cygport(5) from

PKG_NAMES="${PN}-core ${PN}-ada ${PN}-g++ ${PN}-fortran ${PN}-objc"
PKG_HINTS="setup ada g++ gfortran objc"

to

PKG_NAMES="${PN} ${PN}-core ${PN}-ada ${PN}-g++ ${PN}-fortran ${PN}-objc"
PKG_HINTS="setup core ada g++ gfortran objc"

where the new core.hint file has the contents of the existing setup.hint
file (as updated above), and the new setup.hint file just says

category: Devel
sdesc: "GCC for MinGW-w64 Win64 toolchain (source)"


I *think* this means that you'll then get an EMPTY
   mingw64-x86_64-gcc-4.5.1-1.tar.bz2
package, but you won't want to include that in the upload set.

--
Chuck


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]