Opened 9 years ago

Closed 8 years ago

#46195 closed defect (worksforme)

port upgrade outdated not working due sqlite3

Reported by: athenafma@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: sqlite3

Description (last modified by larryv (Lawrence Velázquez))

Dear experts
I have been trying to upgrade my ports but after
attempting to fetch sqlite3-3.8.7.3_0+universal.darwin_14.i386-x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/sqlite3

and Applying patches to sqlite3

--->  Configuring sqlite3

the xcodebuild freezes. Nothing happens. No error msg. It keeps trying to configure the sqlite3 forever. Could you please guide me on how to fix it? Thank you. Kind regards Patricia.

Attachments (2)

main.log (4.0 KB) - added by athenafma@… 9 years ago.
screen.log (11.5 KB) - added by athenafma@… 9 years ago.

Download all attachments as: .zip

Change History (11)

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

Keywords: sqlite3 upgrade outdated removed
Port: sqlite3 added
Type: requestdefect

Since this works for everyone else, we need more information from you. Can you attach the log, please? You can find its location by running the command "port logfile sqlite3".

comment:2 Changed 9 years ago by anton@…

The same thing! And absolutely empty main.log file (zero bytes size).

Last edited 9 years ago by anton@… (previous) (diff)

Changed 9 years ago by athenafma@…

Attachment: main.log added

comment:3 Changed 9 years ago by anton@…

Rebooting of my Mac Mini just fixed problem!

comment:4 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Thanks for attaching the log. Unfortunately it's incomplete: you said the problem occurs during the configure phase, but this log ends partway through the extract phase. Perhaps MacPorts had not yet flushed the rest of the log to disk.

Could you try again with the debug flag? That way, all output will be sent to the terminal as it happens, and we'll hopefully get more info about where exactly it's getting stuck.

sudo port clean sqlite3
sudo port -d upgrade sqlite3

Changed 9 years ago by athenafma@…

Attachment: screen.log added

comment:5 in reply to:  4 ; Changed 9 years ago by athenafma@…

I have attached a new .log after your instructions.

It seems stopping at

checking for gawk... gawk

Replying to ryandesign@…:

Thanks for attaching the log. Unfortunately it's incomplete: you said the problem occurs during the configure phase, but this log ends partway through the extract phase. Perhaps MacPorts had not yet flushed the rest of the log to disk.

Could you try again with the debug flag? That way, all output will be sent to the terminal as it happens, and we'll hopefully get more info about where exactly it's getting stuck.

sudo port clean sqlite3
sudo port -d upgrade sqlite3
Last edited 9 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:6 Changed 9 years ago by larryv (Lawrence Velázquez)

Description: modified (diff)

comment:7 in reply to:  5 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added

Replying to athenafma@…:

It seems stopping at

checking for gawk... gawk

Ok, so it successfully found gawk, and is hanging on the next check, which according to my log should be:

checking whether make sets $(MAKE)... yes

I'm not sure though why that would fail.

sqlite3 has been updated. Could you see if you get the same problem with 3.8.7.4, after running "sudo port selfupdate"?

What version of Xcode and clang do you have?

Have you already tried restarting your computer?

comment:8 Changed 9 years ago by larryv (Lawrence Velázquez)

Is this still an issue with the latest sqlite3 (3.8.10.1 as of r136211)?

comment:9 Changed 8 years ago by raimue (Rainer Müller)

Resolution: worksforme
Status: newclosed

We had multiple reports of this kind. It is usually resolved by rebooting. In all cases, it was xcodebuild or other Command Line Tools hanging.

This is not related to the sqlite3 port. See also similar reports at least in #49647 and #45609.

Note: See TracTickets for help on using tickets.