Fink gnomemeeting is MIA.
The current release of gnomemeeting is 1.2.1.
Fink has 0.98.0-11, which doesn't compile (and hasn't been compiling
for what seems like 2^25 seconds now, error message below).
I'm just raising this again to see whether there are any gnome people
out there.
I know we are
On Sep 20 2004, at 08:45 Uhr, Stefano Franchi wrote:
I am try to execute a 'fink update-all' command that ends up in
wanting to install/update 411 packages. After a few hours spent
downloading all of them and then compiling about 1/3 of them, the
command fails and exits when the compilation of
Hi,
i tar 1.14-1 GNU tar - tape archiver
sagwa:~ cabo$ fink --version
Package manager version: 0.20.3
Distribution version: 0.7.0.cvs
My problem:
sagwa:~ cabo$ /sw/bin/gtar
Segmentation fault
sagwa:~ cabo$
This crash happens before the command line options are even evaluated.
On Jun 14 2004, at 00:05 Uhr, David R. Morrison wrote:
Try updating your prebinding, as decribed here:
http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#seg-fault
Thanks, that was it.
Also fixed some other weird problems I was having.
Is there any documentation on what causes this to
I just sent this to the maintainer -- unfortunately, the mail address
evokes an error message from cdc.noaa.gov.
Gruesse, Carsten
Begin forwarded message:
From: [EMAIL PROTECTED] (Dr. Carsten Bormann)
Date: January 22 2004 22:01:52 Uhr CET
To: [EMAIL PROTECTED]
Subject: Fink: ispell compile
Alexander K. Hansen wrote:
It seemed to build fine on my machine. This is 3.2.0.6-3?
3.2.06-3, to be precise.
On Jan 22 2004, at 23:07 Uhr, Martin Costabel wrote:
+ yacc parse.y
parse.y:676.17: syntax error, unexpected |
This could be a bug (feature?) of fink's yacc. Try
fink
From: Carsten Bormann [EMAIL PROTECTED]
Date: Mon Oct 13, 2003 00:23:16 Europe/Berlin
To: [EMAIL PROTECTED]
Subject: Re: Fink C-Kermit checksum mismatch
I should add:
Even if you accept the mismatch, it does not compile.
See below.
Gruesse, Carsten
cc -DMACOSX10 -DCK_NCURSES -DTCPSOCKET -O
Actually, it looks like groff-1.19 works without doing any patching: I
built it on my machine with no problems (using the environment settings from
http://fink.sourceforge.net/faq/usage-general.php#compile-myself ,
and it seems to run OK.
I'll put a formal request in on your behalf.
I would be very grateful for any help or suggestions --
Sure. Tell us the error message and/or symptoms.
Oh, and what does copy mean here? scp?
http://www.tuxedo.org/~esr/faqs/smart-questions.html#beprecise
(I'm not trying to insult you -- rereading this document every once in
a while is good
Can you send us a specific example?
I think he is referring to console crash log windows that tend to lie
around after configure tests that crash, if you have enabled crash
reporting in the console preferences.
The answer is close the window -- this is a feature, not a bug.
The configure
We all knew this was going to happen:
http://www.cert.org/advisories/CA-2002-28.html
Given the variety of sources we use for obtaining source files, this is
just an accident waiting to happen over and over again in fink.
Running the compiles as root seriously exacerbates the problem. Can
First of all, it's great to hear that Fink people have thought about
the issue.
I'm just not quite sure the level of protection that affords is already
sufficient to make compilation as root a complete non-issue.
Yep. If a fink package tells you its MD5 is bad, please notify the
maintainer
Vincent BOUDON wrote:
Thus far my problem seems to be solved, apt-get install patch fixed it.
Great ! It works also for me ! Thanks a lot !
Just one point: apt-get install patch places a new patch in /sw/bin.
Think to remove the one in /usr/bin.
Apparently /usr/bin/patch is one of the
This crash is from november, i don't think it is relevant. :) Looks like
it is from the aqua version of emacs.
I can do it with 10.1.5 (and the November devtools, if that matters).
See below. It looks like the dumped version of emacs doesn't work right.
(Of course, 21.2-6 runs fine here.)
It's possible that you are using the ssh client that comes with Mac OS X,
which does not have X11 forwarding built into is
I'm not entirely sure what that is supposed to mean, but /usr/bin/ssh definitely
can forward X11 (OS X 10.1.5, I'm pretty sure at least since 10.1.3).
(You may have to use
It happily builds away, until it hits an @ sign when compiling .libs/etherealS.c
Line 1972 of this file reads like this:
{@PROGRAM@, (lt_ptr) 0},
Not very good for a C program :-)
Actually, the first line of ethereal.nm looks like this:
: @PROGRAM@
which may be the origin of this. I
When I try to execute ispell in emacs, it will invariably hang with the
minibuffer message continuing spelling check using default dictionary
I have no idea whether this is related, but there is something fishy
going on with subprocesses in emacs.
1) Using emacs commands such as man, only
There have been a series of related posts on the mac-emacs mailing
lists. Apparently, emacs and Mac OS' ptys don't play well together.
There's some compromise or other that makes ange-ftp happy but makes
something else break; I don't remember the exact details right now.
I'll look it up. A
18 matches
Mail list logo
