Opened 16 months ago

Last modified 15 months ago

#66709 assigned defect

sqlite3-tcl won't build. "error: unsupported option '-static-libgcc'" from clang

Reported by: leeeoooooo Owned by: Schamschula (Marius Schamschula)
Priority: Normal Milestone:
Component: ports Version: 2.8.0
Keywords: i386 Cc:
Port: sqlite3-tcl

Description

sqlite3-tcl won't build on my 32-bit-only CoreDuo MacBook1,1 (Mac OS X 10.6.8)

log shows: "build clang: error: unsupported option '-static-libgcc'" see attached log

Attachments (1)

sqlite3-tcl_main.log (18.1 KB) - added by leeeoooooo 16 months ago.
build log for sqlite3-tcl (i386) under Mac OS X 10.6.8 error: unsupported option '-static-libgcc'

Download all attachments as: .zip

Change History (7)

Changed 16 months ago by leeeoooooo

Attachment: sqlite3-tcl_main.log added

build log for sqlite3-tcl (i386) under Mac OS X 10.6.8 error: unsupported option '-static-libgcc'

comment:1 Changed 16 months ago by jmroot (Joshua Root)

Keywords: sqlite3-tcl removed
Owner: set to Schamschula
Status: newassigned

comment:2 Changed 15 months ago by Schamschula (Marius Schamschula)

I don't have access to a machine running Snow Leopard.

A quick search yields https://stackoverflow.com/questions/19649634/clang-error-unsupported-option-static-libgcc-on-mac-osx-mavericks

comment:3 Changed 15 months ago by Marius Schamschula <mschamschula@…>

In bdca4d29fa69ca6576b37a61bdcb464e924cc1a9/macports-ports (master):

sqlite3-tcl: attempt to fix i386 build

See: #66709

comment:4 Changed 15 months ago by Marius Schamschula <mschamschula@…>

In f5bb575cbf7a6f75e15feacf732756b85267bace/macports-ports (master):

sqlite3-tcl: second attempt to fix i386 build

See: #66709

comment:5 Changed 15 months ago by Marius Schamschula <mschamschula@…>

In d33a5dd484a666e6525259577698f687b58afbe6/macports-ports (master):

sqlite3-tcl: third attempt to fix i386 build

See: #66709

comment:6 Changed 15 months ago by Schamschula (Marius Schamschula)

I give up. I don't know what else to comment out to get rid of this error.

Note: See TracTickets for help on using tickets.