Re: [Fink-devel] Getting patches back "upstream"

[Karin Kosina]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

### Sylvain Cuaz [Thu, May 02, 2002 at 11:38:45AM +0200]
>   No, there at least 3 problems, see (as Dave already told you ;-)  
> http://fink.sourceforge.net/doc/porting/libtool.php

Oh, I'm sorry. I thought the website only talked about the 1.3.x issue,
and didn't scroll down. D'oh. :) -- Thank you for not getting mad at me.
:)

- -- 
Karin Kosina (vka kyrah)
http://kyrah.net

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (Darwin)
Comment: For info see http://www.gnupg.org

iD8DBQE80Qqv7vvdOh/igesRApLOAJ0VO3sCbLsJRBKMAK2GnoJa/qAhNQCgn+jX
zGdxlizq8WZdIt3Zt07oNiM=
=Pv5+
-END PGP SIGNATURE-

___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] Getting patches back "upstream"

[Sylvain Cuaz]

Le jeudi 2 mai 2002, à 10:21 AM, Karin Kosina a écrit :

> Thanks for pointing that out. I know, but most software still uses
> libtool 1.3.x -- which brings me to the question, does any of you know
> if libtool 1.4 is Mac OS X friendly? :)

No, there at least 3 problems, see (as Dave already told you ;-)  
http://fink.sourceforge.net/doc/porting/libtool.php


--
Zauc


___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] Getting patches back "upstream"

[Karin Kosina]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

### Max Horn [Wed, May 01, 2002 at 10:57:58PM +0200]
> >The first thing I have noticed is that Fink uses its own ltconfig and
> >ltmain.sh.
> 
> Note that these are for libtool 1.3.5, which is not anymore being 
> developed.

Thanks for pointing that out. I know, but most software still uses
libtool 1.3.x -- which brings me to the question, does any of you know
if libtool 1.4 is Mac OS X friendly? :)

- -- 
Karin Kosina (vka kyrah)
http://kyrah.net

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (Darwin)
Comment: For info see http://www.gnupg.org

iD8DBQE80Pbu7vvdOh/igesRAgP2AJ9afSgvtrtD/VsaPwmA9lkcI1NxGQCdFu2P
XjZtmQQmiMoEsOSu6T4Dbn0=
=2ILu
-END PGP SIGNATURE-

___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] Getting patches back "upstream"

[Max Horn]

[...]

>The first thing I have noticed is that Fink uses its own ltconfig and
>ltmain.sh.

Note that these are for libtool 1.3.5, which is not anymore being 
developed. Others have replied to your request already, but nobody 
mentioned this detail :-)


Max
-- 
---
Max Horn
Software Developer

email: 
phone: (+49) 6151-494890

___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] Getting patches back "upstream" + libtool convenience libs

[Dave Vasilevsky]

On Fink's website, there's a page devoted to our libtool fixes at 
. These include 
patches to fix the flat_namespace bug and the convenience library bug.

By the way, I fixed up the libtool convenience library patch so the 
folks over at libtool like it more. The new patch is appended to this 
email. No word yet from the libtool upstream maintainers on whether 
they'll actually incorporate this patch.

Dave Vasilevsky


--- ltmain.sh.old   2002-04-27 00:01:23.0 -0400
+++ ltmain.sh   2002-04-27 00:01:45.0 -0400
@@ -2894,7 +2894,18 @@
if test -n "$export_symbols" && test -n "$archive_expsym_cmds"; then
  eval cmds=\"$archive_expsym_cmds\"
else
+ save_deplibs="$deplibs"
+ for conv in $convenience; do
+   tmp_deplibs=
+   for test_deplib in $deplibs; do
+ if test "$test_deplib" != "$conv"; then
+   tmp_deplibs="$tmp_deplibs $test_deplib"
+ fi
+   done
+   deplibs="$tmp_deplibs"
+ done
  eval cmds=\"$archive_cmds\"
+ deplibs="$save_deplibs"
fi
save_ifs="$IFS"; IFS='~'
for cmd in $cmds; do


___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: 
[EMAIL PROTECTED]
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] Getting patches back "upstream"

[Karin Kosina]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

### David R. Morrison [Tue, Apr 30, 2002 at 06:23:10PM -0400]
> I don't think a permanent fix has been found for the "convenience bug",
> though.  There was a fink guy who had a fix, I'm not sure of the status.

Would it be much trouble for you to find out who this was, so I can
contact this person? The problem caused me a sleepless night half a year
back, and my "solution" is still a dirty hack, so I'd be glad to hear a
second opinion.

> What you are talking about, really, is getting patches "way upstream."
> That's been done, but we have to wait for the stream to flow a bit,
> as it were.

I know that things take time, and I'm not expecting changes over night.
I just mentioned the libtool issue since it is one of the most frequent
problems that you encounter when trying to get packages to build on OS
X.

Anyways, thanks a lot for your answers,
#!/kyrah

- -- 
Karin Kosina (vka kyrah)
http://kyrah.net

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (Darwin)
Comment: For info see http://www.gnupg.org

iD8DBQE8zxxw7vvdOh/igesRAnEdAJ4xxVV+fLPp9awifIqqKfL6FvU/cwCfdw4H
AW/a2PwFhfvaY9fNiz5LHRY=
=qze/
-END PGP SIGNATURE-

___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: 
[EMAIL PROTECTED]
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] Getting patches back "upstream"

[David R. Morrison]

All of the libtool stuff has been sent back upstream to the libtool project
a long time ago, and we see the results of this sometimes, when other
upstream authors update the libtool that they are using.  This includes
the 10.1 fix that you mention (-flat_namespace -undefined_suppress).

I don't think a permanent fix has been found for the "convenience bug",
though.  There was a fink guy who had a fix, I'm not sure of the status.

Another common issue is getting the order correct for flags given to the
linker.  GNU ld is more tolerant than Apple's ld, so sometimes packages
need modification to run on OS X.

What you are talking about, really, is getting patches "way upstream."
That's been done, but we have to wait for the stream to flow a bit,
as it were.

  -- Dave

___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: 
[EMAIL PROTECTED]
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] Getting patches back "upstream"

[Karin Kosina]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

### David R. Morrison [Tue, Apr 30, 2002 at 05:57:40PM -0400]
> Speaking only for myself, of course: I think it's great whenever patches
> go back upstream, no matter how they get there. 

Good, I would have been quite astonished to hear a diametrically opposed
opinion here.

The first thing I have noticed is that Fink uses its own ltconfig and
ltmain.sh. Probably for good reasons (I remember having quite a few
problems with libtool myself) -- what is the status of getting these
things supported? At least in my experience, two of the most common
things that do not work when trying to build packages "out of the box"
on Mac OS X are:

o not having "-flat_namespace" but having "-undefined (suppress|warning)" 
  instead of "-undefined error" or having undefined symbols (I think
  this is a libtool thing, since it by default sets "-undefined warning"
  but does not specify the namespace thing, therefore the default,
  -twolevel_namespace, is assumed)
o A strange bug in libtool 1.4.x that results in having duplicate 
  convenience libraries on the linker commandline (and therefore having
  multiply defined symbol errors when linking) -- I guess you've seen
  this before.

Having this fixed (and getting CPPFLAGS += "-no-cpp-precomp" on Darwin
into the default autoconf checks) would probably already improve things
greatly, don't you think?

Cheers,
#!/kyrah

- -- 
Karin Kosina (vka kyrah)
http://kyrah.net

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (Darwin)
Comment: For info see http://www.gnupg.org

iD8DBQE8zxfY7vvdOh/igesRAsCeAJ9JzZ75/L5D6BplUN1Vy4ozxF+xTwCfUUWi
Gn+yXjd7JuG/ZlkfIyaXNFc=
=JgU1
-END PGP SIGNATURE-

___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: 
[EMAIL PROTECTED]
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] Getting patches back "upstream"

[David R. Morrison]

Speaking only for myself, of course: I think it's great whenever patches
go back upstream, no matter how they get there.  Ideally, a packaging
system like fink should only need to adjust things like installation
directories, with the software itself "just working" due to good
configure scripts and appropriate patches.

  -- Dave

___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: 
[EMAIL PROTECTED]
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

[Fink-devel] Getting patches back "upstream"

[Karin Kosina]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi everybody,

  I have a question concering your policy on the patches you create.
While Fink is a great distribution, there are obviously people out there
who will just go to their favourite GNU (or whatever) mirror and
download the source code of the package they are looking for from there.
It would be great if the patches you make are integrated into the
individual software source trees (where possible) so that the greatest
number of users can enjoy the fruits of your work. I have just read the
FAQ entry on that (q2.1), and among the other (very valid) reasons you
state that sometimes you (the Fink people) are just too busy to take the
considerable hassle of making clean patches, explaining things, etc. 

Now my question is: Do you mind if somebody else does this? When I need
a specific package, try to compile it, see that it doesn't work per se,
but Fink has it in the distribution -- would you mind if I reported this
back to the maintainer (making patches and explaining the Mac
specifics, of course giving full credit to you)?

Regards,
#!/kyrah






- -- 
Karin Kosina (vka kyrah)
http://kyrah.net

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (Darwin)
Comment: For info see http://www.gnupg.org

iD8DBQE8zxJ47vvdOh/igesRAkqFAJ0YmnCsHTcTTdrmBTqkcSZ8maZpWgCgmN1p
zWRKeZQ7U93Y9cFQONEmBUk=
=yE3m
-END PGP SIGNATURE-

___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: 
[EMAIL PROTECTED]
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel