On 2018/12/04 16:57, Charles A Daniels wrote:
> > COMPILER and COMPILER_LANGS go right above BUILD_DEPENDS here, but
> > that
> > can be moved on import.
>
> How is the preferred order determined, so I can make sure things are
> ordered correctly in the future?
There's not a hard definition but
On 12/4/18 4:57 PM, Charles A Daniels wrote:
COMPILER and COMPILER_LANGS go right above BUILD_DEPENDS here, but
that
can be moved on import.
How is the preferred order determined, so I can make sure things are
ordered correctly in the future?
> COMPILER and COMPILER_LANGS go right above BUILD_DEPENDS here, but
> that
> can be moved on import.
How is the preferred order determined, so I can make sure things are
ordered correctly in the future?
> I think I prefer Stuart's DESCR. Makes more sense to my ears, flows
> a
> little better
On 12/4/18 4:47 PM, Charles A Daniels wrote:
pcalc.012 passes on i386 (i.e. little-endian 32-bit) with clang
(default
compiler) or ports-gcc, but fails with base-gcc.
Based on this I would set
COMPILER = base-clang ports-gcc
COMPILER_LANGS =c
Please add CC="${CC}" to
> pcalc.012 passes on i386 (i.e. little-endian 32-bit) with clang
> (default
> compiler) or ports-gcc, but fails with base-gcc.
>
> Based on this I would set
>
> COMPILER =base-clang ports-gcc
> COMPILER_LANGS = c
>
> Please add CC="${CC}" to MAKE_FLAGS while there (the wrapper
Updated version integrating Brian and Stuart's changes / suggestions.
> Agreed, nearly there. DESCR could do with a little polish though,
Thoughts on this one?
---
pcal is a programmer's calculator. It simplifies some operations
(especially
working with multiple bases) that are difficult with
On 2018/12/04 16:23, Brian Callahan wrote:
>
>
> On 12/4/18 4:11 PM, Charles A Daniels wrote:
> > > This version is much nicer.
> > I agree your version is more pleasing. I approve of using this.
> >
> > I'm still new around here and learning the conventions, so having this
> > to diff is very
On 12/4/18 4:29 PM, Stuart Henderson wrote:
On 2018/12/04 15:36, Brian Callahan wrote:
On 12/2/18 2:34 PM, Charles A Daniels wrote:
Thanks to the help of Klemens, Brian, and Stuart, I have ported pcalc
(originally written by Peter Glen, now maintained by Mike Frysinger).
Brief description:
On 2018/12/04 15:36, Brian Callahan wrote:
>
>
> On 12/2/18 2:34 PM, Charles A Daniels wrote:
> > Thanks to the help of Klemens, Brian, and Stuart, I have ported pcalc
> > (originally written by Peter Glen, now maintained by Mike Frysinger).
> >
> > Brief description:
> >
> > Programmer's
On 12/4/18 4:11 PM, Charles A Daniels wrote:
This version is much nicer.
I agree your version is more pleasing. I approve of using this.
I'm still new around here and learning the conventions, so having this
to diff is very helpful for me.
My interpretation of Mike's (the upstream)
> This version is much nicer.
I agree your version is more pleasing. I approve of using this.
I'm still new around here and learning the conventions, so having this
to diff is very helpful for me.
My interpretation of Mike's (the upstream) response was that pcalc-4
isn't known to work reliably
On 12/2/18 2:34 PM, Charles A Daniels wrote:
Thanks to the help of Klemens, Brian, and Stuart, I have ported pcalc
(originally written by Peter Glen, now maintained by Mike Frysinger).
Brief description:
Programmer's calculator, command line utility.
There was always a loophole
Thanks to the help of Klemens, Brian, and Stuart, I have ported pcalc
(originally written by Peter Glen, now maintained by Mike Frysinger).
Brief description:
Programmer's calculator, command line utility.
There was always a loophole when it came to a need to covert
13 matches
Mail list logo
