Opened 3 years ago

Last modified 3 years ago

#63056 assigned defect

ghc: build stalls

Reported by: dbl001 (dbl) Owned by: essandess (Steve Smith)
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: Cc: chrstphrchvz (Christopher Chavez)
Port: ghc

Description

Catalina, ghc stalls...

So, am I supposed to apply the patch included in #59467?

Attachments (3)

main.log.xz​ (325.6 KB) - added by essandess (Steve Smith) 3 years ago.
port destroot ghc
main.log​ (3.0 MB) - added by dbl001 (dbl) 3 years ago.
config.log.gz​ (982.5 KB) - added by dbl001 (dbl) 3 years ago.

Change History (12)

comment:1 Changed 3 years ago by jmroot (Joshua Root)

Keywords: ghc removed
Owner: set to essandess
Status: new → assigned
Summary: ---> Building ghc → ghc: build stalls

How long did you wait? Can you provide the log?

comment:2 Changed 3 years ago by chrstphrchvz (Christopher Chavez)

An indefinite stall sounds possibly related to #61233. Is the reporter using trace mode?

comment:3 Changed 3 years ago by chrstphrchvz (Christopher Chavez)

Cc: chrstphrchvz added

comment:4 Changed 3 years ago by jmroot (Joshua Root)

But OTOH, ghc's normal build time tends to be over 6 hours.

Changed 3 years ago by essandess (Steve Smith)

Attachment: main.log.xz​ added

port destroot ghc

comment:5 Changed 3 years ago by essandess (Steve Smith)

I ran sudo port destroot ghc last night on a 6-core i7. It took just over 2 hours. Lgfile attached.

comment:6 Changed 3 years ago by dbl001 (dbl) 

$ sudo port destroot ghc
Password:
--->  Computing dependencies for ghc
--->  Fetching distfiles for ghc
--->  Verifying checksums for ghc
--->  Extracting ghc
--->  Configuring ghc
--->  Building ghc

Changed 3 years ago by dbl001 (dbl)

Attachment: main.log​ added

comment:7 Changed 3 years ago by chrstphrchvz (Christopher Chavez)

The reporter appears to be using the default MacPorts prefix (/opt/local) but main.log contains messages involving files in /usr/local. Is this the situation wiki:FAQ#usrlocal advises against?

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

yes indeed.

it looks like whatever is there in /usr/local/include is at least part of the problem, and probably is the whole problem.

comment:9 Changed 3 years ago by dbl001 (dbl)

There are three config.logs: 

13261436236       56 -rw-r--r--    1 macports         wheel               26783 Jun  9 07:14 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_ghc/ghc/work/ghc-8.10.5/config.log
13261455161       48 -rw-r--r--    1 macports         wheel               22342 Jun  9 07:22 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_ghc/ghc/work/src/ghc-8.10.5/libraries/terminfo/dist-boot/build/config.log
13261452146    38920 -rw-r--r--    1 macports         wheel            19425729 Jun  9 07:18 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_ghc/ghc/work/src/ghc-8.10.5/config.log

Should I upload any/all of them?

Changed 3 years ago by dbl001 (dbl)

Attachment: config.log.gz​ added
Note: See TracTickets for help on using tickets.