On 04/ 5/17 10:01 PM, Sergei Trofimovich wrote:

- pkg_add libiconv

Indeed, I completely overlooked this missing in pkg_add line. Anyway, the configure is the correct one --with-iconv*... Thanks for correction Sergei, Karel

Good Morning All Thanks for the replies @Karel After more testing it looks like i can remove the python business. @Sergei and @Karel libiconv is a prerequisite of ghc and is installed automatically, do you think this should be explicit? @Matthias I will have to have a read about branches and will update the wiki shortly. Cheers Adam On 6 April 2017 at 04:38, Matthias Kilian wrote:

Hi Adam,

On Wed, Apr 05, 2017 at 03:39:18PM +0800, Adam Steen wrote:

...

I have created the Building/Preparation/OpenBSD Wiki Page, i have not yet link it to Building/Preparation https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation page yet, but am looking for a review

Setting Up a OpenBSD System for Building GHC https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/OpenBSD

Nice to see that some people actively work on ghc on OpenBSD (and apologies for me beeing such a slacker keeping the ghc package for OpenBSD up to date).

FWIW, you don't have to pass the very exact package name to pkg_add, like 'autoconf-2.69p2' or ''automake-1.15p0'. There's a relatively new concept in pkg_tools called 'branches' (see pkg_add(1) manpage).

You just have to replace the '-' separating the stem and the version by a '%', e.g.

pkg_add autoconf%2.69 automake%1.15

Then you'll get autoconf-2.69 and aotmake-1.15 regardless of what's the current REVISION (aka package patchleve) ot the package.

Ciao, Kili

On Thu, Apr 6, 2017 at 4:38 AM, Matthias Kilian wrote:

Hi Adam,

On Wed, Apr 05, 2017 at 03:39:18PM +0800, Adam Steen wrote:

...

I have created the Building/Preparation/OpenBSD Wiki Page, i have not yet link it to Building/Preparation https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation page yet, but am looking for a review

Setting Up a OpenBSD System for Building GHC https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/OpenBSD

Nice to see that some people actively work on ghc on OpenBSD (and apologies for me beeing such a slacker keeping the ghc package for OpenBSD up to date).

FWIW, you don't have to pass the very exact package name to pkg_add, like 'autoconf-2.69p2' or ''automake-1.15p0'. There's a relatively new concept in pkg_tools called 'branches' (see pkg_add(1) manpage).

You just have to replace the '-' separating the stem and the version by a '%', e.g.

pkg_add autoconf%2.69 automake%1.15

Then you'll get autoconf-2.69 and aotmake-1.15 regardless of what's the current REVISION (aka package patchleve) ot the package.

Ciao, Kili

Hi Sean The more people using OpenBSD and GHC the better, please add as much information as you think necessary. Cheers Adam On Mon, Apr 10, 2017 at 12:26 PM, Sean Westfall wrote:

Hi Adam Steen, I just chatted with you on https://github.com/commercialhaskell/stack/issues/416, I just added so more info for the wxallowed step to your wiki page -- hope you don't mind. I'm gonna post something to this mailing list in a minute about the trouble I've been having with building GHC on openBSD 6.0.

Thanks, Sean

On Wed, Apr 5, 2017 at 8:04 PM, Adam Steen wrote:

...

Good Morning All

Thanks for the replies

@Karel After more testing it looks like i can remove the python business.

@Sergei and @Karel libiconv is a prerequisite of ghc and is installed automatically, do you think this should be explicit?

@Matthias I will have to have a read about branches and will update the wiki shortly.

Cheers Adam

On 6 April 2017 at 04:38, Matthias Kilian wrote:

...

Hi Adam,

On Wed, Apr 05, 2017 at 03:39:18PM +0800, Adam Steen wrote:

...

I have created the Building/Preparation/OpenBSD Wiki Page, i have not yet link it to Building/Preparation https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation page yet, but am looking for a review

Setting Up a OpenBSD System for Building GHC https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/OpenBSD

Nice to see that some people actively work on ghc on OpenBSD (and apologies for me beeing such a slacker keeping the ghc package for OpenBSD up to date).

FWIW, you don't have to pass the very exact package name to pkg_add, like 'autoconf-2.69p2' or ''automake-1.15p0'. There's a relatively new concept in pkg_tools called 'branches' (see pkg_add(1) manpage).

You just have to replace the '-' separating the stem and the version by a '%', e.g.

pkg_add autoconf%2.69 automake%1.15

Then you'll get autoconf-2.69 and aotmake-1.15 regardless of what's the current REVISION (aka package patchleve) ot the package.

Ciao, Kili

On Thu, Apr 6, 2017 at 4:38 AM, Matthias Kilian wrote:

...

Hi Adam,

On Wed, Apr 05, 2017 at 03:39:18PM +0800, Adam Steen wrote:

...

I have created the Building/Preparation/OpenBSD Wiki Page, i have not yet link it to Building/Preparation https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation page yet, but am looking for a review

Setting Up a OpenBSD System for Building GHC https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/OpenBSD

Nice to see that some people actively work on ghc on OpenBSD (and apologies for me beeing such a slacker keeping the ghc package for OpenBSD up to date).

FWIW, you don't have to pass the very exact package name to pkg_add, like 'autoconf-2.69p2' or ''automake-1.15p0'. There's a relatively new concept in pkg_tools called 'branches' (see pkg_add(1) manpage).

You just have to replace the '-' separating the stem and the version by a '%', e.g.

pkg_add autoconf%2.69 automake%1.15

Then you'll get autoconf-2.69 and aotmake-1.15 regardless of what's the current REVISION (aka package patchleve) ot the package.

Ciao, Kili

---

ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

--

Sean Westfall 2644 E. 4th St. Long Beach, CA 90802 ph: (808) 281-4695 em: sean.westfall@gmail.com