Bug 195492 - net-im/telepathy-glib build goes into endless loop
Summary: net-im/telepathy-glib build goes into endless loop
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: Normal Affects Many People
Assignee: freebsd-gnome (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-29 09:07 UTC by Gerard Seibert
Modified: 2016-01-17 10:55 UTC (History)
2 users (show)

See Also:

Attachments
Build log of the "net-im/telepathy-qt4" port (66.08 KB, text/plain)
2014-12-03 10:17 UTC, Gerard Seibert 		no flags 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 Gerard Seibert 2014-11-29 09:07:41 UTC 
I just updated my ports tree and attempted to update the "net-im/telepathy-glib" port. The build went into an endless loop and the system ran out of swap space. I rebooted, updated the ports tree again and then tried to build the port. The log file of the build was exceeding 3G when I shut the build down. The following is repeated Ad infinitum:

TelepathyGLib-0.12.gir:42725.1-42725.0: warning: expected end element of `type'


TelepathyGLib-0.12.gir:42725.1-42725.0: error: unexpected end of file


TelepathyGLib-0.12.gir:42725.1-42725.0: warning: expected end element of `type'


TelepathyGLib-0.12.gir:42725.1-42725.0: error: unexpected end of file


TelepathyGLib-0.12.gir:42725.1-42725.0: warning: expected end element of `type'


TelepathyGLib-0.12.gir:42725.1-42725.0: error: unexpected end of file


TelepathyGLib-0.12.gir:42725.1-42725.0: warning: expected end element of `type'
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2014-11-29 09:33:33 UTC 
Fix Summary and assign.
Comment 2 Gerard Seibert 2014-12-03 10:17:23 UTC 
Created attachment 150137 [details]
Build log of the "net-im/telepathy-qt4" port
Comment 3 Martin Wilke freebsd_committer freebsd_triage 2016-01-17 10:55:55 UTC 
Hi,

This looks fixed to me, I close it here, if you still face the problem with the current ports tree please let me know and I will reopen.

Thanks.