Re: How reconcile openmodelica-dvel & octave dependencies on sundials vs. sundials2

[Ken Cunningham]

Adam, Murray -- This small patch will patch the octave Portfile to make 
sundials2 support a variant.
If you want to install octave without sundials2 support (so you can use 
openmodelica which needs sundials) this should allow you to do that.

The command is:

sudo port -v install octave -sundials2

I built octave locally without sundials2 support and it seems to build cleanly.

I don't know how many people might want to install both octave and openmodelica.
If there are enough people, perhaps Marcus /Marius might add something like 
this into the octave Portfile.

Best,

Ken

--- patch below ---

--- Portfile2018-06-02 16:18:27.0 -0700
+++ Portfile2018-06-05 22:14:12.0 -0700
@@ -295,6 +295,11 @@
 --without-magick\
 --disable-docs
 
+#default to no sundials support - see variant below
+configure.args-append   \
+--without-sundials_nvecserial \
+--without-sundials_ida
+
 # in configure.ac, listed as one of "[p]rograms used when running Octave"
 depends_lib-append port:python27
 configure.python ${prefix}/bin/python2.7
@@ -365,10 +370,6 @@
 configure.args-append --without-openssl
 #depends_lib-append path:lib/libssl.dylib:openssl
 
-#--without-sundials_nvecserial
-#--without-sundials_ida
-depends_lib-append  port:sundials2
-
 # see etc/README.MacOS
 depends_run-append   \
 port:epstool \
@@ -399,6 +400,13 @@
 #https://trac.macports.org/ticket/51480
 #default_variants-append +java
 
+variant sundials2 description {build with sundials2 support - not compatible 
with sundials} {
+depends_lib-append  port:sundials2
+configure.args-delete --without-sundials_nvecserial
+configure.args-delete --without-sundials_ida
+}
+default_variants-append +sundials2
+
 variant qt4 conflicts qt5 description {build the GUI using Qt4} {
 PortGroup qt4 1.0
 depends_lib-append port:qscintilla-qt4

Re: gcc49 fails to build

[Joshua Root]

Dave Horsfall wrote:
> On Tue, 5 Jun 2018, Ken Cunningham wrote:
> 
>> You will still need to fix this 
>> 
>>  
>> , and who knows what else
>>
>> The real question is why? What do you need gcc49 for that gcc5 doesn't do?
> 
> Because I use whatever MacPorts comes with...  I don't touch *anything* in 
> that area except upon advice from this list (I don't futz around with 
> symlinks, for example, although I can under FreeBSD).
> 
> If it wants to build with gcc49, then, well, it wants to build with gcc49; 
> I certainly didn't tell it to...

I'm sure you didn't, but after a default variant is chosen the first
time you install, it sticks across upgrades. This proposal would fix
your problem: 

In the meantime, whichever port it is that is using gcc49 should be
changed to not do so on platforms or with Xcode versions where it won't
work. These commands might help find out which one(s): 'port dependents
gcc49', 'port dependents libgcc', 'port installed variant:gcc49'.

>> If there is any good reason that would certainly make the exercise 
>> somewhat more palatable
> 
> Or are you saying that I need the latest Xcode, which needs High Sierra, 
> which seems to refuse to install on this box?  13", late 2009, firmware 
> "6,1" (note the comma).

The opposite. Newer Xcode versions fail to build gcc49 and older.

- Josh

Re: gcc49 fails to build

[Christopher Jones]

> On 5 Jun 2018, at 5:42 pm, Dave Horsfall  wrote:
> 
> On Mon, 4 Jun 2018, Ryan Schmidt wrote:
> 
>> Here is the bug report corresponding to that problem:
>> https://trac.macports.org/ticket/56511
> 
> Ooh - a utility called "sw_vers"!  I wonder what other hidden gems are 
> lurking, essentially undocumented, on one of Apple's finest products?
> 
> After over 40 years of Unix programming, this Mac never ceases to astonish 
> me...  No, I'm not being sarcastic (for once).
> 
> Anyway...
> 
>> gcc4x is not compatible with Xcode 9.2. It may not be compatible with any 
>> Xcode 9.x. Use gcc5 or later if possible. We don't plan to backport the 
>> fixes to make gcc4x compatible with newer Xcode.
> 
> And, err, how do I achieve that?  I have this odd expectation that MacPorts 
> "just works" i.e. the dependencies have been taken care of for me.

What port are you installing/updating that requires gcc49 ? I.e. in your first 
message what was printed prior to

--->  Building gcc49
Error: Failed to build gcc49: command execution failed

??

Its possible you have a port installed using a gcc49 variant, and when you 
update this choice is maintained, even if the default has switched to a newer 
gcc. In these cases you need to manually remove the port and reinstall it with 
the newer defaults. What does

 > port installed | grep gcc

give you ?

Chris

> 
> Speaking of Xcode, I keep being offered to upgrade it, but it will only run 
> on High Sierra.  The first time I tried that, I got a message about something 
> being incompatible with this box which I couldn't write down fast enough 
> before it reverted to Sierra.  The next time I tried (paying more attention 
> this time), it bombed out because a critical file was missing...  I suppose 
> I'd better start putting money aside from my old age pension (yes, I'm a 
> pensioner) to buy an Air or something.
> 
> -- Dave, the iconoclast



smime.p7s
Description: S/MIME cryptographic signature

Re: gcc49 fails to build

[Dave Horsfall]

On Tue, 5 Jun 2018, Ken Cunningham wrote:

You will still need to fix this 
 
, and who knows what else


The real question is why? What do you need gcc49 for that gcc5 doesn't do?


Because I use whatever MacPorts comes with...  I don't touch *anything* in 
that area except upon advice from this list (I don't futz around with 
symlinks, for example, although I can under FreeBSD).


If it wants to build with gcc49, then, well, it wants to build with gcc49; 
I certainly didn't tell it to...


If there is any good reason that would certainly make the exercise 
somewhat more palatable


Or are you saying that I need the latest Xcode, which needs High Sierra, 
which seems to refuse to install on this box?  13", late 2009, firmware 
"6,1" (note the comma).


There aren't any firmware upgrades for the thing; I can cheat and reflash 
it to look like a "Pro" instead, but I ain't about to go down that route 
any time soon...


-- Dave, with a seamless upgrade on his iPhone 5s from iOS 10 to 11.4

Re: gcc49 fails to build

[Ken Cunningham]

On 2018-06-05, at 9:53 AM, Ken Cunningham wrote:

> build on 10.16 and 10.17 

before I get shot, read this as "darwin 16 and darwin 17" please...

Re: gcc49 fails to build

[Ken Cunningham]

On 2018-06-05, at 9:42 AM, Dave Horsfall wrote:

> On Mon, 4 Jun 2018, Ryan Schmidt wrote:
> 
>> Here is the bug report corresponding to that problem:
>> https://trac.macports.org/ticket/56511
> 
> Ooh - a utility called "sw_vers"!  I wonder what other hidden gems are 
> lurking, essentially undocumented, on one of Apple's finest products?
> 
> After over 40 years of Unix programming, this Mac never ceases to astonish 
> me...  No, I'm not being sarcastic (for once).
> 
> Anyway...
> 
>> gcc4x is not compatible with Xcode 9.2. It may not be compatible with any 
>> Xcode 9.x. Use gcc5 or later if possible. We don't plan to backport the 
>> fixes to make gcc4x compatible with newer Xcode.
> 
> And, err, how do I achieve that?  I have this odd expectation that MacPorts 
> "just works" i.e. the dependencies have been taken care of for me.
> 
> Speaking of Xcode, I keep being offered to upgrade it, but it will only run 
> on High Sierra.  The first time I tried that, I got a message about something 
> being incompatible with this box which I couldn't write down fast enough 
> before it reverted to Sierra.  The next time I tried (paying more attention 
> this time), it bombed out because a critical file was missing...  I suppose 
> I'd better start putting money aside from my old age pension (yes, I'm a 
> pensioner) to buy an Air or something.
> 
> -- Dave, the iconoclast


gcc49 will probably build on 10.16 and 10.17 without too much trouble -- just 
not with the Xcode clang and headers that comes with those systems.

you might get further building it with gcc7.

You will still need to fix this 

 , and who knows what else

The real question is why? What do you need gcc49 for that gcc5 doesn't do?

If there is any good reason that would certainly make the exercise somewhat 
more palatable

Ken

Re: gcc49 fails to build

[Dave Horsfall]

On Mon, 4 Jun 2018, Ryan Schmidt wrote:


Here is the bug report corresponding to that problem:
https://trac.macports.org/ticket/56511


Ooh - a utility called "sw_vers"!  I wonder what other hidden gems are 
lurking, essentially undocumented, on one of Apple's finest products?


After over 40 years of Unix programming, this Mac never ceases to astonish 
me...  No, I'm not being sarcastic (for once).


Anyway...

gcc4x is not compatible with Xcode 9.2. It may not be compatible with 
any Xcode 9.x. Use gcc5 or later if possible. We don't plan to backport 
the fixes to make gcc4x compatible with newer Xcode.


And, err, how do I achieve that?  I have this odd expectation that 
MacPorts "just works" i.e. the dependencies have been taken care of for 
me.


Speaking of Xcode, I keep being offered to upgrade it, but it will only 
run on High Sierra.  The first time I tried that, I got a message about 
something being incompatible with this box which I couldn't write down 
fast enough before it reverted to Sierra.  The next time I tried (paying 
more attention this time), it bombed out because a critical file was 
missing...  I suppose I'd better start putting money aside from my old age 
pension (yes, I'm a pensioner) to buy an Air or something.


-- Dave, the iconoclast

Re: issue building libgcc 7.3 on Snow Leopard

[Riccardo Mottola via macports-users]

Hi Ken,

Ken Cunningham wrote:

o

sudo port -v install libmacho

you should be good to go.

If it works for you as well as it has for me, I'll add it as a build dep for 
10.6. Please report back.


yes, it works for me! I was able to rebuild libgcc and all installed gccs.

I still wonder why it doesn't work, --disable-libsanitizer is still 
supproted. I thought at first it was a removed option in 7.3, but it is not.


Riccardo