> On Apr 11, 2017, at 17:56, Richard L. Hamilton wrote:
>
> I can do that; but will that need any more info than below? I doubt that I
> kept the log, once I got it built.
That's fine. We have a log here:
https://build.macports.org/builders/ports-10.6_x86_64_legacy-builder/builds/25779
just do
sudo port -v build libgphoto2
and you'll get a new log to submit.
Ken
On 2017-04-11, at 3:56 PM, Richard L. Hamilton wrote:
> I can do that; but will that need any more info than below? I doubt that I
> kept the log, once I got it built.
>
>> On Apr 11, 2017, at 04:03, Ryan Schmid
I can do that; but will that need any more info than below? I doubt that I
kept the log, once I got it built.
> On Apr 11, 2017, at 04:03, Ryan Schmidt wrote:
>
>
>> On Apr 10, 2017, at 14:54, Richard L. Hamilton wrote:
>>
>> ...with the compiler that the port chose given my setup (/usr/bin
> On Apr 10, 2017, at 14:54, Richard L. Hamilton wrote:
>
> ...with the compiler that the port chose given my setup (/usr/bin/gcc-4.2,
> Xcode 3.2.6, although I have others and could switch if needed). It built
> fine using configure.compiler=macports-clang-3.8
Could you file a bug report in
...with the compiler that the port chose given my setup (/usr/bin/gcc-4.2,
Xcode 3.2.6, although I have others and could switch if needed). It built fine
using configure.compiler=macports-clang-3.8
signature.asc
Description: Message signed with OpenPGP
