On Friday, February 7, 2003, at 08:32 PM, [EMAIL PROTECTED] wrote:
How long can I expect the older version to be around?
Forever. Calm down. You can go back to the old one. I'll fix your
package.
However, the old openssl-dev needs to be updated to Conflict/Replace
openssl097-dev, so it
Hi Ben,
On Friday, February 7, 2003, at 11:46 PM, Ben Hines wrote:
On Friday, February 7, 2003, at 11:28 PM, John Davidorff Pell wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was just thinking, is it possible to make /sw/bin/init.csh check
whether /sw/bin and /sw/sbin are
Remi Mommsen [EMAIL PROTECTED] wrote:
[snip]
That's a quick fix for me to do, including the check for the X11
directory as it is mentioned in tracker item 594676. However, I do not
know exactly how to handle the feature tracker. Am I supposed to add
the patch file to the tracker item?
David R. Morrison wrote:
Remi Mommsen [EMAIL PROTECTED] wrote:
[snip]
That's a quick fix for me to do, including the check for the X11
directory as it is mentioned in tracker item 594676. However, I do not
know exactly how to handle the feature tracker. Am I supposed to add
the patch
At 0:02 Uhr -0800 08.02.2003, Ben Hines wrote:
On Friday, February 7, 2003, at 08:32 PM, [EMAIL PROTECTED] wrote:
How long can I expect the older version to be around?
Forever. Calm down. You can go back to the old one. I'll fix your package.
However, the old openssl-dev needs to be
Max et al: I've pulled the xfree86 package (and the xfree86-base,
xfree86-base-threaded upgrades it depends on) from unstable and put them
in expermental/jswhit/x11-system. Probably should have put them there in
the first place - I apologize for that.
Ben H - I would appreciate it if you could
At 6:03 Uhr -0700 08.02.2003, jeff whitaker wrote:
Max et al: I've pulled the xfree86 package (and the xfree86-base,
xfree86-base-threaded upgrades it depends on) from unstable and put them
in expermental/jswhit/x11-system. Probably should have put them there in
the first place - I apologize
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Samstag, Februar 8, 2003, at 02:56 Uhr, Ben Hines wrote:
On Friday, February 7, 2003, at 10:36 AM, David wrote:
Furthermore it is not as simple as simply adding --prebind. Many
pieces of software are not yet fixed to fully support
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Samstag, Februar 8, 2003, at 04:49 Uhr, Max Horn wrote:
snip
1) Always first send a draft of your announce to fink-devel, with the
comment that you plan this announcement. Possibly wait for a go/no-go
by the leads (drm,
There are various people on fink-beginners who already installed this
and ask for help. Maybe we can enhance the news item to describe how
to get out of the situation?
Max
---
This SF.NET email is sponsored by:
SourceForge Enterprise
At 14:50 Uhr +0100 08.02.2003, David wrote:
[...]
Actually, Max, Drm and Benjamin will have to make a decision. I would
much prefer, that people do not post to the fink-devel list, but send
the announcement to me. After I have verified the information in the
Mail and maybe even talked to the
Essentially, this appears to be a quick-fix for the lack of an
auto-update
feature in Virex. The engineers used several existing pieces of
open-source software to make their job easier, but they forgot/didn't
know how/whatever to move the libraries to /Library/Application Support.
There are two
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Samstag, Februar 8, 2003, at 04:18 Uhr, Kyle Moffett wrote:
There are two major problems with this:
1) Licensing violations.
This seems to be a rather iffy case of license violation. I will have
to check back with the lawyers
Maybe you can just open a new patch tracker item and post your code there.
We'll clean up the various tracker items later.
-- Dave
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
At 15:54 Uhr +0100 08.02.2003, David wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Samstag, Februar 8, 2003, at 03:13 Uhr, Max Horn wrote:
snip
Well the drawbacks of this approach (compared to the advantages you list):
Two bottlenecks instead of one (first you, then the
'fink reinstall openssl-shlibs dlcompat-shlibs curl-ssl-shlibs' should
do it, I believe. Although it might break Virex.
On Saturday, February 8, 2003, at 09:06 AM, Max Horn wrote:
There are various people on fink-beginners who already installed this
and ask for help. Maybe we can enhance the
It is true that to build prebound libraries an address must be
specified, but not so for executables.
So on the Mac simply adding -prebind flags to all compiles and links
will not cause any problems for executables or libraries. If the
prebind fails when building an executable (because one or
On Saturday, February 8, 2003, at 11:49 AM, Carsten wrote:
For fink to build prebound libraries, there is a tool someone here
made called gcc-prebind 0.1 (search the mailing list archives around
last November). It might be useful to get started in the process but
ultimately I think each shlib
Pedro Massobrio [EMAIL PROTECTED] wrote:
What can I tell to people who installed Virex-7.2 over a Fink
installation and are asking for a solution?
Thanks, Pedro
Alexander Strange suggested
'fink reinstall openssl-shlibs dlcompat-shlibs curl-ssl-shlibs'
and this sounds good to me. Note
David R. Morrison wrote:
Pedro Massobrio [EMAIL PROTECTED] wrote:
What can I tell to people who installed Virex-7.2 over a Fink
installation and are asking for a solution?
Thanks, Pedro
Alexander Strange suggested
'fink reinstall openssl-shlibs dlcompat-shlibs curl-ssl-shlibs'
and this
First, I apologize for my announcement, which was made in inappropriate
way and surprised you.
On 2003.2.9, at 01:02 AM, Max Horn wrote:
We can still say that you then are the official first reviewer, and
you can integrate any other feedback other people get, and then
forward it to
Thanks Martin,
I passed your info and Dave's to the forums.
Pedro
On Sunday, February 9, 2003, at 01:59 AM, Martin Costabel wrote:
David R. Morrison wrote:
Pedro Massobrio [EMAIL PROTECTED] wrote:
What can I tell to people who installed Virex-7.2 over a Fink
installation and are asking
At 3:01 Uhr +0900 09.02.2003, Masanori Sekino wrote:
First, I apologize for my announcement, which was made in
inappropriate way and surprised you.
Masanori, this was definitly not directed at you in particular, and I
don't believe you have to apologize. In any case I have no ill
bearings
hehe okay I guess I won't :)
[EMAIL PROTECTED] writes:
I prepared two patch files for init.(c)sh, but I cannot attach them to
the tracker item. I suppose because it is a feature request. I have no
permission to change it. Could anyone of the developers change that?
-=[JFH] Justin F. Hallett
I noticed libgnomevfs(-2).la contains '-lssl -lcrypto' in
dependency_libs line. All executables linked using this .la files are
directly linked with libssl and libcrypto. Also, all libtool libraries
which refer this .la files will contain '-lssl -lcrypto' in their .la
files.
To fix this,
1.
On Saturday, Feb 8, 2003, at 10:43 US/Eastern, David wrote:
On Samstag, Februar 8, 2003, at 04:18 Uhr, Kyle Moffett wrote:
There are two major problems with this:
1) Licensing violations.
This seems to be a rather iffy case of license violation. I will have
to check back with the lawyers on
Oops! I spoke too soon. It appears that they do include curl's license,
but not licenses for OpenSSL or Dlcompat. Most likely they obtained
permission for CURL then just included everything that CURL depended
on, rather than checking the licensing issues for each of them as well.
The only
David [EMAIL PROTECTED] wrote:
On Samstag, Februar 8, 2003, at 04:18 Uhr, Kyle Moffett wrote:
There are two major problems with this:
1) Licensing violations.
This seems to be a rather iffy case of license violation. I will have
to check back with the lawyers on Monday. There are
On Saturday, February 8, 2003, at 07:18 AM, Kyle Moffett wrote:
feature in Virex. The engineers used several existing pieces of
open-source software to make their job easier, but they forgot/didn't
know how/whatever to move the libraries to /Library/Application
Support.
Probably not good
I got libintl.1.dylid to compile prebound. I'm working on getting
the rest of the bootstrap working. :) Here's a patch for the patch for
gettext for the bootstrap. I'd appreciate it if one of the
core-developers would look at it. :)
Thanx,
JP
-archive_cmds='$CC $(test .$module =
On Saturday, February 8, 2003, at 10:56 PM, John Davidorff Pell wrote:
-archive_cmds='$CC $(test .$module = .yes echo -bundle || echo
-dynamiclib) $allow_undefined_flag -o $lib $libobjs $deplibs$linkopts
-install_name $rpath/$soname $(test -n $verstring -a x$verstring !=
x0.0 echo
I may be very very wrong, but i think that this simply built the lib
with the address that it defaulted to. It gave no errors about it for
libintl.1.dylid but many other binaries gave errors about conflicting
w/ libintl.1.dylid The later packages also gave me errors about
conflicting w/
uhhh.. So how do I tell it to give libabc the address 0x12345678
while keeping the executables at 0x?
JP
On Saturday, February 8, 2003, at 08:07 PM, Benjamin Reed wrote:
On Saturday, February 8, 2003, at 10:56 PM, John Davidorff Pell wrote:
-archive_cmds='$CC $(test
On Saturday, February 8, 2003, at 11:27 PM, John Davidorff Pell wrote:
uhhh.. So how do I tell it to give libabc the address 0x12345678
while keeping the executables at 0x?
And that is one of the reasons all of fink isn't prebound yet. =)
You will need to hack the Makefile.in
On Saturday, February 8, 2003, at 08:41 PM, [EMAIL PROTECTED]
wrote:
Hi:
I'm trying to compile a python C++ module called Vpython to help
someone out and I'm in way over my head. I am getting errors of the
form
CXX/Include/CXX_Objects.h:967: no class template named
35 matches
Mail list logo
