[pkg-fallout at FreeBSD.org: [REL - head-amd64-default][textproc/multimarkdown] Failed for multimarkdown-4.3.2 in checksum]

Jimmy Kelley ljboiler at gmail.com
Sat Nov 9 15:10:16 UTC 2013


On Fri, Nov 08, 2013 at 09:55:00AM -0500, Adam Weinberger wrote:
> Hi, I'm still having trouble with this. Can anybody offer me some advice
> here? During which build stages may my port dial out? When "make
> checksum" is run independently of "make fetch", it begins by wiping out
> ${WRKDIR}.
> 
> Can I dial out during do-build on the package cluster?
> 
> # Adam
> 
> 
> --
> Adam Weinberger
> adamw at adamw.org
> http://www.adamw.org

> Date: Fri, 8 Nov 2013 05:47:29 GMT
> From: pkg-fallout at FreeBSD.org
> To: adamw at FreeBSD.org
> Cc: pkg-fallout at FreeBSD.org
> Subject: [REL - head-amd64-default][textproc/multimarkdown] Failed for
>  multimarkdown-4.3.2 in checksum
> 
> You are receiving this mail as a port that you maintain
> is failing to build on the FreeBSD package build server.
> Please investigate the failure and submit a PR to fix
> build.
> 
  <snip...>

Hi Adam,

   I've been working on a port for the latest version of Eclipse, which will
have to clone the eclipse git repo along with a bunch of submodules as you are
doing with the multimarkdown port.  I will tell you that what has to be
pulled down is HUGH, and it really was a pain to wait for that fetch to happen
when I wanted to clean and rebuild because of some build error.  What I ended
up doing is have the fetch  phase pull the git repo down into the DISTDIR area
("git clone" if it's not there, "git update" if it is already there" ), and
then have the extract phase copy the stuff in DISTDIR over to WRKSRC where
it can be patched and built; a "clean" copy is always left in DISTDIR, just
like the tarballs of other ports.

This might sound like overkill (it's 2+Gb per copy of the git repo), but
for eclipse it's necessary because the build process needs the repo history
for timestamp info, and it really does speed things up (and will for future
port updates).

Perhaps this might help with the multimarkdown port...

Jimmy


More information about the freebsd-ports mailing list