Re: Question about bootstrapping MinGW

2016-12-09 Thread Brandon Allbery
On Fri, Dec 9, 2016 at 3:44 PM, Mojca Miklavec wrote: > You mean not adding it as a runtime dependency (even if having also a > runtime dependency on gcc would be technically correct)? > You're only using that package to bootstrap. If you're worried about e.g. a runtime leaking into the final pa

Re: Question about bootstrapping MinGW

2016-12-09 Thread Mojca Miklavec
On 8 December 2016 at 17:16, Brandon Allbery wrote: > On Thu, Dec 8, 2016 at 4:10 PM, Mojca Miklavec wrote: >> >> Also, in an ideal world the package manager would check whether >> "*-all" is already installed or available in a binary form and only if >> it is not, it would start building the "*-gc

Re: Question about bootstrapping MinGW

2016-12-08 Thread Brandon Allbery
On Thu, Dec 8, 2016 at 4:10 PM, Mojca Miklavec wrote: > Also, in an ideal world the package manager would check whether > "*-all" is already installed or available in a binary form and only if > it is not, it would start building the "*-gcc" port. > Specify it as a build dependency? -- brandon

Re: Question about bootstrapping MinGW

2016-12-08 Thread Mojca Miklavec
Hi, Here's the forgotten link: https://github.com/mojca/macports-user-mojca/tree/master/ports/cross On 7 December 2016 at 22:02, Mojca Miklavec wrote: > > I have finally managed to come up with ports for MinGW-w64. It seems > to work as expected except for a tiny problem: gcc has to be compil