Re: Issues with compiler flags in gfortran

On 2019-1-23 02:44 , Ken Cunningham wrote: > Patching or configuring gcc to call a specific clang directly as an assembler > seems to me to be quite complicated, but may appear simpler to some others. I > looked at this before and balked. Doesn't look too hard, just changing '--with-as=${prefix

Re: Issues with compiler flags in gfortran

On 2019-1-23 03:16 , Ken Cunningham wrote: > > On 2019-01-22, at 2:37 AM, Joshua Root wrote: > > >> >> I think this issue overall is covered by >> , and I agree with jeremyhu's >> assessment there. >> >> - Josh > > Yes, we discussed it there similarly to

Re: Issues with compiler flags in gfortran

Hi, > On Jan 23, 2019, at 17:06, Joshua Root wrote: > > Doesn't look too hard, just changing '--with-as=${prefix}/bin/as' in the > portfile to '--with-as=${prefix}/bin/llvm-as-mp-7.0' for example. But > we're already telling the gcc ports --with-as=${prefix}/bin/as > specifically, which makes t

Re: Issues with compiler flags in gfortran

On 2019-1-23 21:01 , Nicolas Pavillon wrote: > Hi, > >> On Jan 23, 2019, at 17:06, Joshua Root wrote: >> >> Doesn't look too hard, just changing '--with-as=${prefix}/bin/as' in the >> portfile to '--with-as=${prefix}/bin/llvm-as-mp-7.0' for example. But >> we're already telling the gcc ports --w

Re: Issues with compiler flags in gfortran

On 23/01/2019 11:00 am, Joshua Root wrote: On 2019-1-23 21:01 , Nicolas Pavillon wrote: Hi, On Jan 23, 2019, at 17:06, Joshua Root wrote: Doesn't look too hard, just changing '--with-as=${prefix}/bin/as' in the portfile to '--with-as=${prefix}/bin/llvm-as-mp-7.0' for example. But we're al

Re: Issues with compiler flags in gfortran

On 2019-1-23 22:10 , Chris Jones wrote: > > Which ports exactly are you thinking of adding clang dependencies to ? > Will need to be careful of not creating circular deps, as for instance > the clang ports themselves depend on cctools. When building with macports-clang or older Xcode versions, ye

Re: Issues with compiler flags in gfortran

> On Jan 23, 2019, at 00:06, Joshua Root wrote: > > '--with-as=${prefix}/bin/llvm-as-mp-7.0' 1. have to be sure we're not talking about the assembler for llvm IR here, which is a totally different thing...I think we call clang. 2. bootstrapping. the stock toolchain on many systems can't bui

Re: Issues with compiler flags in gfortran

On 23/01/2019 1:47 pm, Ken Cunningham wrote: On Jan 23, 2019, at 00:06, Joshua Root wrote: '--with-as=${prefix}/bin/llvm-as-mp-7.0' 1. have to be sure we're not talking about the assembler for llvm IR here, which is a totally different thing...I think we call clang. 2. bootstrapping.

Re: Issues with compiler flags in gfortran

On 2019-1-24 00:51 , Chris Jones wrote: > > To my eye, the better way out here would seem to be leave gcc as is, > configure to use ${prefix}/bin/as, but then enhance the cctools port (in > some way to be discussed) to allow it to behaviour more along the lines > of how the system /usr/bin/as does

function wrapping mechanism

Hi all, I’m about to commit a new type of system to macports-legacy-support, to “wrap” current library functions to enable updating them to current functionality. The general method is to: #define function function_original #include_next #undef function #define function macports_wrapped_f