Opened 2 years ago

Closed 18 months ago

#65727 closed defect (fixed)

scriptix build fails: Undefined symbols: "GC_throw_bad_alloc()"

Reported by: barracuda156 Owned by: barracuda156
Priority: Normal Milestone:
Component: ports Version: 2.7.2
Keywords: Cc:
Port: scriptix

Description

Existing version is broken across the board: https://ports.macports.org/port/scriptix/details/

On 10.6.8 Rosetta the failure is:

/usr/bin/g++-4.2 -pipe -Os -arch ppc -Wl,-headerpad_max_install_names -arch ppc -o .libs/scriptix scriptix.o -Wl,-bind_at_load  -L/opt/local/lib ../lib/.libs/libsxparse-0 ../lib/.libs/libscriptix-0 /opt/local/lib/libgc.dylib -ldl
Undefined symbols:
  "GC_throw_bad_alloc()", referenced from:
      operator new(unsigned long, GCPlacement, void (*)(void*, void*), void*)in scriptix.o
      gc::operator new(unsigned long)in scriptix.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[1]: *** [scriptix] Error 1
make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_scriptix/scriptix/work/scriptix-0.31/bin'
make: *** [all-recursive] Error 1

Change History (3)

comment:1 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)

scriptix is only used by the awemud port.

My understanding is that scriptix 0.31 is the final standalone version of scriptix. After that, scriptix merged with awemud: https://web.archive.org/web/20070505004116/http://awemud.net/index.php?page=news&article=74

The latest version of awemud on SourceForge is 0.25 from 2006: https://sourceforge.net/projects/awemud/files/awemud-ng/

Here is the last version of the awemud homepage from 2007: https://web.archive.org/web/20070602103228/http://awemud.net/

As of January 2009, the awemud homepage redirected to the sourcemud homepage.

Here is the last version of the sourcemud homepage from 2011: https://web.archive.org/web/20110905030825/http://sourcemud.org/

Looks like the last version of sourcemud was 0.0.2 from 2008: https://web.archive.org/web/20090406185256/http://sourcemud.org/files/?mod=files

I found a GitHub project for sourcemud that says it is deprecated and dead: https://github.com/elanthis/sourcemud

So we could either update awemud to the latest version and mark the scriptix port as being replaced by it, or we could mark both as replaced by a new sourcemud port, or just delete both awemud and scriptix.

comment:2 in reply to:  1 Changed 2 years ago by barracuda156

Replying to ryandesign:

scriptix is only used by the awemud port.

My understanding is that scriptix 0.31 is the final standalone version of scriptix. After that, scriptix merged with awemud: https://web.archive.org/web/20070505004116/http://awemud.net/index.php?page=news&article=74

The latest version of awemud on SourceForge is 0.25 from 2006: https://sourceforge.net/projects/awemud/files/awemud-ng/

Here is the last version of the awemud homepage from 2007: https://web.archive.org/web/20070602103228/http://awemud.net/

As of January 2009, the awemud homepage redirected to the sourcemud homepage.

Here is the last version of the sourcemud homepage from 2011: https://web.archive.org/web/20110905030825/http://sourcemud.org/

Looks like the last version of sourcemud was 0.0.2 from 2008: https://web.archive.org/web/20090406185256/http://sourcemud.org/files/?mod=files

I found a GitHub project for sourcemud that says it is deprecated and dead: https://github.com/elanthis/sourcemud

So we could either update awemud to the latest version and mark the scriptix port as being replaced by it, or we could mark both as replaced by a new sourcemud port, or just delete both awemud and scriptix.

Thank you for responding!

I sort of accidentally noticed scriptix as being broken for all systems and its website being dead and initially wanted to open a ticket to remove it. Then I decided to see what is going wrong with it, tried to build, got this error, found solution, it actually fixed the build on 10.6.8. Opened a PR: https://github.com/macports/macports-ports/pull/15921/files – but on new systems it fails to build. I am not specifically interested in this port, so any solution is fine. I can close that PR, if the port will be either removed or replaced.

comment:3 Changed 18 months ago by barracuda156

Owner: set to barracuda156
Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.