Emmanuele Salvati wrote:
[]
hank:~$ sudo apt-get install xemacs-sumo-pkg
Reading Package Lists... Done
Building Dependency Tree... Done
The following NEW packages will be installed:
xemacs-sumo-pkg
0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 0B/28.3MB
Koen van der Drift wrote:
Hi,
A new upstream version of a package I maintain, gives a lot of warnings,
such as:
evaluate.c:2129: warning: incompatible implicit declaration of built-in
function 'strlen'
Does the warning disappear if you add #include string.h to evaluate.c?
--
Martin
On Apr 16, 2006, at 6:45 AM, Martin Costabel wrote:
Does the warning disappear if you add #include string.h to
evaluate.c?
Yes, that worked. Thanks.
The package instructions say to run ./install to build and install
the package, it looks like this:
more license.txt
echo Type YES if you
Koen van der Drift wrote:
[]
cd t_coffee_source
make clean
make -i CC=gcc USER_BIN=../bin/ all
[]
The line make -i CC=gcc USER_BIN=../bin/ all works when I issue it
outside of fink, however when using fink, I get the following error:
make -i CC=gcc
On Apr 16, 2006, at 10:08 AM, Martin Costabel wrote:
Stupid question:
Are you sure you are in the right directory when make is called?
Is the compile script executed line-per-line, or is it a shell script?
It's a plain text file, but I extracted the relevant lines into my
info file, for
Koen van der Drift wrote:
[]
CompileScript:
cd t_coffee_source
make -i CC=gcc USER_BIN=%i/bin all
Yes, that's what I supected. The 'cd' has no effect in this case.
Either combine both lines into one or make it a shell script by putting
'#!/bin/sh' (or more correctly '#!/bin/sh -ev') as a
On Apr 16, 2006, at 10:25 AM, Martin Costabel wrote:
CompileScript:
cd t_coffee_source
make -i CC=gcc USER_BIN=%i/bin all
Yes, that's what I supected. The 'cd' has no effect in this case.
Either combine both lines into one or make it a shell script by
putting '#!/bin/sh' (or more
Koen van der Drift wrote:
[]
What about the lines that install stuff in the $HOME directory, can I
leave those in the info file? The program won't execute when these files
are missing, but since they are installed outside /sw, I am not sure
what to do here.
mkdir $HOME/.t_coffee
mkdir
On Apr 16, 2006, at 2:14 PM, Martin Costabel wrote:
Koen van der Drift wrote:
[]
What about the lines that install stuff in the $HOME directory,
can I leave those in the info file? The program won't execute when
these files are missing, but since they are installed outside /sw,
I am not
Koen van der Drift wrote:
Since part of the installation process is a test for the package, these
folders need to be created before the InstallScript is executed, so I
thought about putting them in PreInstScript. However, you are correct
about the ownership, it is root, not the username, and
On Apr 16, 2006, at 5:48 PM, Benjamin Reed wrote:
Considering that multiple users can use a given mac, I don't see
how you
can assume the only person who will need those files in their home
directory is the person installing the package.
Good point, I didn't think of that. I will put a
Dear Fink developers,
I hope this is right mailinglist. I encounter a problem while compiling a
program that uses gls. I run FINK on an Intel architecture. The error
message is the following:
In file included from /sw/include/gsl/gsl_sf.h:20,
from specialfunctionsmodule.cc:26:
The packages listed below were brought forward from the 10.4-
transitional tree, but do not compile in the 10.4 tree. (They may or
may not compile in the 10.4-transitional tree.) They are being
removed from the 10.4 tree, and listed in the wiki. Of course, they
may be repaired and
13 matches
Mail list logo
