Opened 4 years ago

Closed 4 years ago

#61760 closed defect (fixed)

Octave assumes gcc variant and port names are always the same

Reported by: Isaacych Owned by: Chris Jones <jonesc@…>
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: cjones051073 (Chris Jones)
Port: octave

Description

After

sudo port install octave

Then I received the output

---> Computing dependencies for octave Error: Dependency 'gccdevel' not found.

I checked the port related to gccdevel. I found ports called libgcc-devel and gcc-devel. Could it possibly just a typo for the octave installation procedure? Is there any way to refer gccdevel to gcc-devel during installation?

The version I am trying to install is:

sudo port list octave

octave @5.2.0 math/octave

Thanks!

Change History (7)

comment:2 Changed 4 years ago by kencu (Ken)

Cc: cjones051073 added

Young Christopher, your public beckons...

comment:3 Changed 4 years ago by kencu (Ken)

Keywords: Octave removed
Port: gcc-devel added; Octave removed
Summary: Octave dependency problem for Big Sur with apple silicon → compilers PG refers to nonexistent gccdevel

comment:4 Changed 4 years ago by kencu (Ken)

well something is funny -- Chris had it one way, now changed it to this way, that seems broken <​https://github.com/macports/macports-ports/commit/d9b5e26e2007f4e964983069da4a076e8e1196f9#diff-18ddf39afeaaff209d51f90863e28c1242959b72fdd895504f6485a300d18163>

We'll have to let him straighten it out, after a flurry of commits.

comment:5 Changed 4 years ago by cjones051073 (Chris Jones)

No, that change I made above is correct.

The line 

 set compilers.gcc_default gccdevel

sets the default 'variant' name, *not* the port name that that variant uses. The variant name is 'gccdevel' and the compiler port associated to that is 'gcc-devel'

The issue is previously the port name and variant name was always the same, and some ports had made the assumption this would always be the case. Octave is doing the same here and needs to be fixed to not do this.

See

​https://github.com/macports/macports-ports/commit/770ac7b5057936a6631dcf952e8602fd7eb713d0#diff-18ddf39afeaaff209d51f90863e28c1242959b72fdd895504f6485a300d18163

where I added a method to the PG to access the correct port depends for a given fortran variant, and

​https://github.com/macports/macports-ports/commit/a77555c71b83992dd197b205544651b3c0a808a1#diff-86f513d8f85457e8d4e3747d69c34953ddce490ea3287c5e95085e12f17a0087

which uses it.

Octave needs to do the same.

comment:6 Changed 4 years ago by cjones051073 (Chris Jones)

Port: octave added; gcc-devel removed
Summary: compilers PG refers to nonexistent gccdevel → Octave assumes gcc variant and port names are always the same

comment:7 Changed 4 years ago by Chris Jones <jonesc@…>

Owner: set to Chris Jones <jonesc@…>
Resolution: → fixed
Status: new → closed

In 1444149f3489dcac7659bcaca661d5a159c68157/macports-ports (master):

octave: Fix gcc-devel conflict, don't assume gcc port and variant names are always the same
Closes: #61760

Note: See TracTickets for help on using tickets.