Re: pkg-config v. -I/opt/local/include

On Jan 12, 2016, at 1:05 PM, Craig Treleaven wrote: > On Jan 12, 2016, at 4:09 AM, Ryan Schmidt wrote: >> On Jan 11, 2016, at 9:03 AM, Craig Treleaven wrote: >>> I’m having buiild failures due to includes pointing to old/other headers >>> installed in /opt/local/include. >>> >>> As I understand

Re: pkg-config v. -I/opt/local/include

On Jan 11, 2016, at 9:03 AM, Craig Treleaven wrote: > I’m having buiild failures due to includes pointing to old/other headers > installed in /opt/local/include. > > As I understand it, 'pig-config —cflags’ returns an empty string when a > header is installed in /usr/include. The port I’m

Re: [144564] trunk/dports

On 1/12/16 1:17 PM, mo...@macports.org wrote: > Revision > 144564 > Author > mo...@macports.org > Date > 2016-01-12 13:17:36 -0800 (Tue, 12 Jan 2016) > > > Log Message > > remove perl5_16..5_20 variants from perl dependents (#50245)

Re: [144564] trunk/dports

On 12 January 2016 at 22:36, David Evans wrote: > On 1/12/16 1:17 PM, mo...@macports.org wrote: >> Revision >> 144564 >> Author >> mo...@macports.org >> Date >> 2016-01-12 13:17:36 -0800 (Tue, 12 Jan 2016) >> >>

Re: [144564] trunk/dports

On 1/12/16 3:07 PM, Mojca Miklavec wrote: > >>> (I'm only slightly inclined to wait a tiny bit until the buildbots >>> have cought up with the history, else other unsuspected committers >>> will be unable to extract whether anything was wrong with their >>> commits.) >> >> Sorry, I don't

Re: [144564] trunk/dports

On 1/12/16 1:59 PM, Mojca Miklavec wrote: > On 12 January 2016 at 22:36, David Evans wrote: >> On 1/12/16 1:17 PM, mo...@macports.org wrote: >>> Revision >>> 144564 >>> Author >>> mo...@macports.org >>> Date >>>

Re: [144564] trunk/dports

On 12 January 2016 at 23:37, David Evans wrote: > > Now that you have removed the subports, you need to commit p5-graveyard > to enable the replaced_by mechanism so that the old ports will update > properly. I know. I only wanted to wait a bit. The old jobs were finished on the buildbots now

Re: [144564] trunk/dports

On 13 January 2016 at 00:20, David Evans wrote: > > Why don't we just kill the p5-graveyard build on the buildbots. It's > irritating and doesn't serve any useful purpose. Do we end up with any spurious files on the buildbot if we do? One more thing: you already committed

Re: pkg-config v. -I/opt/local/include

> On Jan 12, 2016, at 4:09 AM, Ryan Schmidt wrote: > On Jan 11, 2016, at 9:03 AM, Craig Treleaven wrote: >> I’m having buiild failures due to includes pointing to old/other headers >> installed in /opt/local/include. >> >> As I understand it, 'pig-config —cflags’

Re: [144564] trunk/dports

And while off-topic, I just have to say that: I'm completely amazed. We no longer have any single failure of perl modules on the buildbots (other than one single trivial problem that's easy to fix). Thanks for keeping all the modules up to date and working! Mojca

Re: [144564] trunk/dports

On 1/12/16 3:27 PM, Mojca Miklavec wrote: > On 13 January 2016 at 00:20, David Evans wrote: >> >> Why don't we just kill the p5-graveyard build on the buildbots. It's >> irritating and doesn't serve any useful purpose. > > Do we end up with any spurious files on the buildbot if we do? I don't

Re: [144564] trunk/dports

On 13 January 2016 at 00:35, David Evans wrote: > On 1/12/16 3:27 PM, Mojca Miklavec wrote: >> On 13 January 2016 at 00:20, David Evans wrote: >>> >>> Why don't we just kill the p5-graveyard build on the buildbots. It's >>> irritating and doesn't serve any useful purpose. >> >> Do we end up with

Re: [144564] trunk/dports

On 1/12/16 3:40 PM, Mojca Miklavec wrote: > On 13 January 2016 at 00:35, David Evans wrote: >> On 1/12/16 3:27 PM, Mojca Miklavec wrote: >>> On 13 January 2016 at 00:20, David Evans wrote: Why don't we just kill the p5-graveyard build on the buildbots. It's irritating and doesn't