On Sep 17, 2012, at 00:34, Frank J. R. Hanstick wrote:
When upgrading outdated, I ran into this error:\
I don't see an actual error message in the output you posted. Perhaps the real
error is earlier.
What do you need gcc42 for? It's very old; we're planning to delete it soon:
Is this another manifestation of the current problem with ld64?
Greg Shenaut
On Sep 17, 2012, at 6:06 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Sep 17, 2012, at 00:34, Frank J. R. Hanstick wrote:
When upgrading outdated, I ran into this error:\
I don't see an actual error
On Sep 17, 2012, at 08:21, Gregory Shenaut wrote:
On Sep 17, 2012, at 6:06 AM, Ryan Schmidt wrote:
I don't see an actual error message in the output you posted. Perhaps the
real error is earlier.
What do you need gcc42 for? It's very old; we're planning to delete it soon:
On Sep 16, 2012, at 4:31 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Sep 16, 2012, at 10:01, Murray Eisenberg wrote:
I posted a ticket that libstdcxx would not build. The ticket was closed with
duplicate status and pointer to #36026.
But #36026 refers to gcc46 problem after ld64
On Sep 17, 2012, at 9:52 AM, Murray Eisenberg murrayeisenb...@gmail.com wrote:
On Sep 16, 2012, at 4:31 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Sep 16, 2012, at 10:01, Murray Eisenberg wrote:
I posted a ticket that libstdcxx would not build. The ticket was closed
with
On Sep 17, 2012, at 10:38:35 -0600, Frank Schima macsforever2...@macports.org
wrote:
On Sep 17, 2012, at 9:52 AM, Murray Eisenberg murrayeisenb...@gmail.com
wrote:
On Sep 16, 2012, at 4:31 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Sep 16, 2012, at 10:01, Murray Eisenberg
Hello,
I am not sure what it is needed for these days, It was originally
installed to build ports requiring a more upgraded version of gcc 4.2
than that supported by Apple (that was a long time ago) and it has
been maintained since? If only the development gcc 4.2.1 is used by
MacPorts,
Hi all,
I have installed the py27-django port and I'm running through the django
tutorial at projectdjango [1]. I modified the project settings.py file to use
sqlite3 as follows:
'ENGINE': 'django.db.backends.sqlite3', # Add
'postgresql_psycopg2', 'mysql', 'sqlite3'
Hello,
Sorry for the slightly late response, but I noticed something which bugs me:
My ports kmymoney4(-devel) and skrooge ALREADY MAKE USE of this
post-activate {
# Calling kbuildsycoca4 in case KDE hasn't called it yet to make sure that
plugins are loaded.
system
