On Jul 19, 2008, at 2:56 PM, Daniel Macks wrote:
> On Sat, Jul 19, 2008 at 02:05:27PM -0400, Alexander Hansen wrote:
>> I've found some issues with drawtiming that I'd like to resolve.
>> (drawtiming-nox is missing a freetype219 dependency and didn't build
>> for me on 10.5.4, but that's outside
On Sat, Jul 19, 2008 at 02:05:27PM -0400, Alexander Hansen wrote:
> I've found some issues with drawtiming that I'd like to resolve.
> (drawtiming-nox is missing a freetype219 dependency and didn't build
> for me on 10.5.4, but that's outside the point here)
>
> The relevant line is
>
> ++ -
I've found some issues with drawtiming that I'd like to resolve.
(drawtiming-nox is missing a freetype219 dependency and didn't build
for me on 10.5.4, but that's outside the point here)
The relevant line is
++ -I/sw/include/ImageMagick -g -O2 -Wall -W -D_THREAD_SAFE -
DYYDEBUG=1 -g -O2 -L
On Jun 19, 2004, at 5:33 AM, jfm wrote:
The CompileScript is executed 'line by line'.
Thus either use :
CompileScript: cd src ; make
Or :
CompileScript: <<
#!/bin/sh
cd src
make
<<
Thanks, I found out later that this also works:
SourceDirectory: foo/src
CompileScript: make
- Koen.
-
On Jun 19, 2004, at 1:13 AM, Koen van der Drift wrote:
CompileScript: <<
cd src/
make
<<
This gives the following error:
cd src/
Can't exec "cd": No such file or directory at
/sw/lib/perl5/Fink/Services.pm line 403.
The CompileScript is executed 'line by line'.
Thus either use :
Hi,
The package I am working on has all source code in a separate directory
(/sw/src/foo-1.2.3-1/foo/src). So in my info file I use (there is no
configure-step):
CompileScript: <<
cd src/
make
<<
This gives the following error:
cd src/
Can't exec "cd": No such file or directory
On Tuesday, August 19, 2003, at 05:58 AM, Joe Block wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am creating a package for python23 docs, and have run into the
problem that the tar file is named html-2.3.tar.bz, but expands into a
directory tree named Python-Docs-2.3. It was easy eno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am creating a package for python23 docs, and have run into the
problem that the tar file is named html-2.3.tar.bz, but expands into a
directory tree named Python-Docs-2.3. It was easy enough to rename the
tar file in /sw/src and get fink to create
There are two ways to resolve the versioning issue. One is to rename
the package. The other is to use the relatively new "Epoch" field in
fink. All versions with epoch = 1 are regarded as newer than all
versions with epoch = 0 (the default).
Epochs should only be used in special cases, but this
Greetings All,
I'm the current maintainer of several Fink packages, namely aterm, netcat,
ytalk and ytalk-nox. I've finally had time to read the updated Fink
documentation, and have added Source-MD5 fields to all my packages (and a
License field to ytalk and ytalk-nox). I've submitted the new vers
At 10:56 PM -0700 6/14/03, Ben Hines wrote:
>
>Just list the emboss tarball as a SourceN: line and use it normally.
>There are percent expansions for the build directory like %b you can
>use. Some other packages do it.
>
Thanks, I'll look into that. I also thought about making an emboss-dev
split
On Thursday, June 12, 2003, at 04:26 PM, Koen van der Drift wrote:
If I understand this correctly it wants to be able to access files
from the
tarball of emboss. How do I approach this? I also happen to be the
maintainer of emboss, so maybe I can change that installation so it
will
also instal
Hi,
I am attemping to make a package for bio-emboss (a perl module for emboss).
Now I need to modify the makefile to point to some specific emboss files.
Here's what it says:
#
# --- The following lines need to be adjusted !
#
# --- installation path of EMBOSS (--PREFIX during EMBOSS' config
13 matches
Mail list logo
