On Freitag, Jänner 31, 2003, at 01:01 Uhr, Max Horn wrote:
Hi folks,
Hello Max.
For some time, I hoped we might be able to just reuse the apt engine
(and the hope is still not completely gone), but as far as I can tell
it can't cope with build time only dependencies (but there is the
Failed: Internal error: node for libungif already exists
I am running current fink head. I think we squashed this error before,
so perhaps it has something to do with the recent modifications to the
dep loop.
I'm pretty sure that this part of the dependency code is executed and done
with
At 12:50 Uhr +0100 31.01.2003, David wrote:
On Freitag, J§nner 31, 2003, at 01:01 Uhr, Max Horn wrote:
[...]
I think that it would be an excellent idea to use something like a
Wiki. If you want I can install such a system on one of the boxen I
have authority over.
shrug Never got the hang
On Friday, Jan 31, 2003, at 10:20 US/Eastern, S. Brent Faulkner wrote:
Hi guys... This list may not be the perfect place to ask this question, but I suspect someone may be able to answer it here, so
Visit the macosx-dev list hosted by OmniGroup. It is under developer resources or somesuch.
If I am creating a package and the program adds features if compiled
with library N, should I automatically make it a build dependency? Or
should I leave it for the user to decide how it should be compiled? For
example, if my software can read png, jpeg, and tiff if compiled with
their libs,
On Friday, January 31, 2003, at 04:51 PM, James Gibbs wrote:
If I am creating a package and the program adds features if compiled
with library N, should I automatically make it a build dependency?
It should be a dependency, yes. We try to make packages produce the
same thing on every
In some packages, you can use a flag to the configure step to disable
linking certain libraries. If that is possible, and you want to do it,
then you don't need to make the library a dependency.
However, if the library will be used whenever it is found and there is
no way to disable that, then
snip
Hmm, I might be able to do some of that... I know enough PPC assembler
to do __asm__ statements inside C, but not enough to write whole
functions (don't know how to do stack frames).
I am learning it already. Found some pretty good information on it.
Things like linked lists, btrees and
OK, my promised second mail will have to wait till tomorrow. I just
got home after spending 8 hours in my car, 4 of those standing in one
spot on the highway, at -2 degree celsius with no car heating
(highway was blocked for hours due to a crash). I really don't feel
like anything but sleep
The code freeze for XFree86 4.3.0 will be any day now. I believe the
Mac OS X/Darwin part of the code base is pretty much in final form.
Benjamin put together a package in fink unstable which builds
something very close to the top of the tree. I would encourage as
many people as possible to
Run your in-line fink scripts with -ex:
CompileScript:
#!/bin/sh -ex
export CCACHE_DISABLE=1
rm LIBLINK/*
make all PREFIX=%p LDFLAGS=-L%p/lib MOTIF_LIBPATH=%p/lib/libXm.3.dylib
LIBDIR=%p/lib LIBPATH=-LLIBLINK -L%p/lib
XINCLUDES=-I/usr/X11R6/include -I%p/include/ CFLAGS=-DNDEBUG
It
I know this is a stupid question about your (cool!) hint, please
forgive me...
Should new info files prepend #!/bin/sh at the beginning of scripts
or is it optional? (and only for debugging)
Carsten
On Friday, January 31, 2003, at 07:47 pm, Ben Hines wrote:
Run your in-line fink scripts
If you start a script with #!/bin/sh, then the entire script is executed
as a shell script (and you can even execute it as perl or whatever you
like). Without that beginning, the commands in the script are executed
one line at a time (which originally was the only method available).
-- Dave
please ignore the earlier forwarded message--I selected the wrong list
from my address group.
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
On Friday, January 31, 2003, at 08:28 PM, Benjamin Reed wrote:
As of the last snapshots, things have worked pretty good as far as
backwards-compatibility with software built against xfree86 4.2, but
keep in mind that if you plan on testing this, and you build something
against it, it won't
When I installed lcms 1.09-1, it overwrote my /usr/bin directory with a
file, making my system non-bootable. Note my fink dir is
/usr/local/finksw.
$ dpkg --contents
/usr/local/finksw/fink/dists/unstable/main/binary-darwin-powerpc/graphics
/lcms_1.09-1_darwin-powerpc.deb
...
-rwxr-xr-x
16 matches
Mail list logo
