On Jan 17, 2012, at 3:46 PM, Ryan Schmidt wrote:
>
> On Jan 17, 2012, at 17:43, Jeremy Huddleston wrote:
>
>> That looks good to me, but I would very much like to know what ports fall
>> into this category, so I can check if this is still the case with
>> top-of-tree clang and file a bug agai
On Tue, Jan 17, 2012 at 05:46:58PM -0600, Ryan Schmidt wrote:
> It's just so tedious. I don't have time to file all these bug reports
> and keep track of what versions of clang work. I'm happy if we can
> commit a fix, any fix, that lets a port compile.
A lot of those problems are only caused by c
On Jan 17, 2012, at 17:43, Jeremy Huddleston wrote:
> That looks good to me, but I would very much like to know what ports fall
> into this category, so I can check if this is still the case with top-of-tree
> clang and file a bug against the compiler if necessary.
>
> I know wine falls into t
There still is a config.log, although you might be having a hard time to
find it.
I agree this message should be adjusted, though, if possible.
--
Clemens
on the road
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforg
That looks good to me, but I would very much like to know what ports fall into
this category, so I can check if this is still the case with top-of-tree clang
and file a bug against the compiler if necessary.
I know wine falls into this category, but most "normal" ports should be fine
with clang
Can you attach the log it's talking about? Probably config.log in
/opt/local/var/macports/
build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_tesseract/tesseract/work/tesseract-3.01
Thanks,
Mark
On Tue, Jan 17, 2012 at 12:16 PM, MacPorts wrote:
> #32907: tesseract
I don't think the log file for selfupdate actually exists... I think
the message saying it does is in error, unfortunately.
Scott
On Tue, Jan 17, 2012 at 12:24 PM, Jeremy Lavergne
wrote:
>> The correct command is "port log". I suggest taking a look at "man 1 port".
>> Several looks.
>
> He's
> The correct command is "port log". I suggest taking a look at "man 1 port".
> Several looks.
He's after the logs for selfupdate itself, not a specific port.
In either case, `port logfile ...` is just as legit as `port log ...`--when
asking about logs for specific ports. logfile shows the fi
On Jan 16, 2012, at 20:24, Joshua Root wrote:
> You still have to ask Bill to create you a buildbot account.
I have a buildbot account, but I'm still not clear how to force a rebuild.
I go to http://build.macports.org/ then click on Buildslaves then on
buildports-snowleopard-x86_64. Then I can
