Context Navigation

Changes between Initial Version and Version 1 of Ticket #43362, comment 4

initial	v1
1		Okay, I think I understand what's going on here. First (as described above), unless a version of Berkeley DB is ```port select```ed, configuration fails. Second, even if one is ```port select```ed, the configuration fails for prefix builds, because it can't find Boost. That second issue is remedied by adding ```--with-boost=[[PREFIX]]``` to ```./configure```.
	1	Okay, I think I understand. First (as described above), unless a version of Berkeley DB is ```port select```ed, configuration fails. Second, even if one is ```port select```ed, configuration fails for prefix builds, because it can't find Boost. That second issue is remedied by adding ```--with-boost=[[PREFIX]]``` to ```./configure``` (which should be harmless for default installations).
2	2
3	3	I'm attaching a ```Portfile``` patch that addresses only the second issue. The first remains (I do not know the preferred way to properly address that).

initial	v1
1		Okay, I think I understand what's going on here. First (as described above), unless a version of Berkeley DB is ```port select```ed, configuration fails. Second, even if one is ```port select```ed, the configuration fails for prefix builds, because it can't find Boost. That second issue is remedied by adding ```--with-boost=[[PREFIX]]``` to ```./configure```.
	1	Okay, I think I understand. First (as described above), unless a version of Berkeley DB is ```port select```ed, configuration fails. Second, even if one is ```port select```ed, configuration fails for prefix builds, because it can't find Boost. That second issue is remedied by adding ```--with-boost=[[PREFIX]]``` to ```./configure``` (which should be harmless for default installations).
2	2
3	3	I'm attaching a ```Portfile``` patch that addresses only the second issue. The first remains (I do not know the preferred way to properly address that).