On Mon, Jun 03, 2019 at 11:03:18AM -0600, Gary Aitken wrote:
> In attempting to build a new port (prusa3d slicer) I need another new
> port (wxWidgets). The original distfile fetch of wxWidgets was a .tar.gz.
> The configure phase had an error; a search for the source of the error
> turned up a
On 6/3/19 3:33 PM, Michael Gmelin wrote:
On Mon, 3 Jun 2019 12:46:32 -0600
Gary Aitken wrote:
On 6/3/19 11:19 AM, Michael Gmelin wrote:
On 3. Jun 2019, at 19:03, Gary Aitken
wrote:
Is it possible to force fetching of .tar.bz2 instead of .tar.gz if
both are available? Or how does one get
On Mon, 3 Jun 2019 12:46:32 -0600
Gary Aitken wrote:
> On 6/3/19 11:19 AM, Michael Gmelin wrote:
> >
> >
> >> On 3. Jun 2019, at 19:03, Gary Aitken
> >> wrote:
> >>
> >> In attempting to build a new port (prusa3d slicer) I need another
> >> new port (wxWidgets). The original distfile
On 6/3/19 11:19 AM, Michael Gmelin wrote:
On 3. Jun 2019, at 19:03, Gary Aitken wrote:
In attempting to build a new port (prusa3d slicer) I need another new
port (wxWidgets). The original distfile fetch of wxWidgets was a .tar.gz.
The configure phase had an error; a search for the source
> On 3. Jun 2019, at 19:03, Gary Aitken wrote:
>
> In attempting to build a new port (prusa3d slicer) I need another new
> port (wxWidgets). The original distfile fetch of wxWidgets was a .tar.gz.
> The configure phase had an error; a search for the source of the error
> turned up a bug
In attempting to build a new port (prusa3d slicer) I need another new
port (wxWidgets). The original distfile fetch of wxWidgets was a .tar.gz.
The configure phase had an error; a search for the source of the error
turned up a bug (old) which claimed the error was solved by fetching the
distfile
