Date: Fri, 26 Mar 2004 09:42:44 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: "Dr. Richard E. Hawkins" <hawk@slytherin.ds.psu.edu> Cc: freebsd-ports@freebsd.org Subject: Re: installing ifc at the moment (version conflict) Message-ID: <20040326094244.584ae10c@Magellan.Leidinger.net> In-Reply-To: <20040325233226.GE24906@slytherin.ds.psu.edu> References: <20040324163317.GA24906@slytherin.ds.psu.edu> <20040324175937.04014407@Magellan.Leidinger.net> <20040325205112.GD24906@slytherin.ds.psu.edu> <20040325224603.7c207108@Magellan.Leidinger.net> <20040325233226.GE24906@slytherin.ds.psu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 25 Mar 2004 18:32:26 -0500
"Dr. Richard E. Hawkins" <hawk@slytherin.ds.psu.edu> wrote:
> > ifc maintainer CCed.
>
> > > #PATCHLEVEL= ${PORTVERSION:C/(.+p)(.+)$/pe\2/}
> > > PATCHLEVEL= pe043
>
> > > This installed the patched version (with the help of NO_CHECKSUM).
>
> > This is not enough. The icc port has the "intel-patch" target in the
> > makefile. This needs to be used for ifc too.
>
> OK, I'll add that. Is what I did the right way to set patch level?
It's a work around. Using something similar like the icc port does,
makes it more easy for the maintainer to update the port. In the icc
port you just have to set the PORTVERSION in a specific way and the
PATCHLEVEL will be set to the right string automatically.
> > > /usr/local/intel_fc_80/lib/libifcore.a(for_diags.o): In function
> > > `redirect_stderr':
>
> etc.
>
> > > and so forth. I'm guessing that this is some kind of library mismatch.
>
> > Remember, this is not a native port. It's a linux port "hacked" to
> > produce FreeBSD binaries. I think you have to add a lseek64 wrapper into
> > lang/ifc/files/linux_file.c.
>
> ? But that's installed by the port. Wouldn't this mean that everyone
> who installs the port has to do this (defeating the purpose?). I
> certainly know my way about Fortran, but I don't know enough C to have
> any idea what the above even means.
The port needs an update to the actual patch level. This includes to
write a "lseek64" function which calls the appropriate native FreeBSD
function. You are trying to update it ATM, but as you said, you are
lacking the appropriate skills to do it.
So if you depend on a bugfix for ifc, you have to find someone with
access to the ifc distfiles, enough knowledge to fix the problem and
enough time to do it.
Bye,
Alexander.
--
I will be available to get hired in April 2004.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040326094244.584ae10c>