Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 890421 - sci-geosciences/gmt-6.4.0 fails to compile: Cannot determine GSHHG version:
Summary: sci-geosciences/gmt-6.4.0 fails to compile: Cannot determine GSHHG version:
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Sci-geo Project
URL:
Whiteboard:
Keywords:
: 900673 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-01-11 06:15 UTC by Agostino Sarubbo
Modified: 2024-03-25 03:45 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
build.log (build.log,64.64 KB, text/plain)
2023-01-11 06:15 UTC, Agostino Sarubbo 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2023-01-11 06:15:07 UTC 
https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: sci-geosciences/gmt-5.4.4 fails to compile (DASH-SYSTEM).
Discovered on: amd64 (internal ref: dash_tinderbox)

NOTE:
(DASH-SYSTEM) in the summary means that the bug was found on a machine that runs /bin/sh as dash but this bug MAY or MAY NOT BE related to dash.
Comment 1 Agostino Sarubbo gentoo-dev 2023-01-11 06:15:10 UTC 
Created attachment 848173 [details]
build.log

build log and emerge --info
Comment 2 Agostino Sarubbo gentoo-dev 2023-01-23 12:14:26 UTC 
usr-merge_tinderbox has reproduced this issue with version 6.4.0 - Updating summary.
Comment 3 Eli Schwartz 2024-03-25 03:44:12 UTC 
  Run Build Command(s):/usr/bin/ninja cmTC_74fd0 && [1/2] Building C object
  CMakeFiles/cmTC_74fd0.dir/gshhg_version.c.o

  [2/2] Linking C executable cmTC_74fd0

  

  

  

  		cmTC_74fd0: H5CS.c:224: H5CS_pop: Assertion `fstack->nused > 0' failed.

  Subprocess aborted


Not a dash issue.
Comment 4 Eli Schwartz 2024-03-25 03:45:33 UTC 
*** Bug 900673 has been marked as a duplicate of this bug. ***