On Thu, Apr 19, 2012 at 6:40 PM, Frank Warmerdam <span dir="ltr"><<a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Charlie,<br>
<br>
The typical reason would be that adding opendap adds stuff into the<br>
libraries list that results in other "test links" failing. It would<br>
be helpful if you could file a bug and attach the config.log.<br>
<br>
Best regards,<br>
Frank</blockquote><div><br></div><div>I looked through the config.log a little closer, and in all four cases the following argument was added to the compiler flags:</div><div><br></div><div> -arch x86_64 i386 ppc</div>
<div><br></div><div>This is bad for two reasons:</div><div><br></div><div> - I'm not trying to build a universal binary and all of my components are x86_64 only.</div><div><br></div><div> - `-arch x86_64 i386 ppc` isn't even a valid compiler flag. The proper thing to pass would be `-arch x86_64 -arch i386 -arch ppc`, so the compiler would error out even if I had the universal binaries to support a 3-way build.</div>
<div><br></div><div>I've traced the offending flags to `dap-config` so it looks like this is an OpenDAP bug now, not a GDAL bug.</div><div><br></div><div>Apologies for the noise.</div><div><br></div><div><br></div><div>
-Charlie </div></div>