| 1 |
Perl 5.8 compiles fine on Leopard as long as you don't specify |
| 2 |
-Duseshrplib (for a dynamic libperl), but unfortunately that is |
| 3 |
necessary to install Postgres with Pl/Perl support. |
| 4 |
|
| 5 |
I've tried hand-compiling Perl from raw source (and Gentoo's build and |
| 6 |
macport's build) to no avail; it clearly is a problem in the official |
| 7 |
release. |
| 8 |
|
| 9 |
5.10 does properly build shared libraries using both the official |
| 10 |
release and the macports build. |
| 11 |
|
| 12 |
Logan Bowers |
| 13 |
|
| 14 |
In article <20080208091057.GF1750@g.o>, |
| 15 |
Fabian Groffen <grobian@g.o> wrote: |
| 16 |
|
| 17 |
> On 07-02-2008 20:12:48 -0800, Logan Bowers wrote: |
| 18 |
> > Hello all, |
| 19 |
> > |
| 20 |
> > It appears that Perl 5.8 does not compile as a shared library on Leopard |
| 21 |
> > (due |
| 22 |
> > to upstream breakage). As such, I'd like to get 5.10 into the portage tree |
| 23 |
> > asap so I can link it against Postgres. :) |
| 24 |
> |
| 25 |
> Is there a bug on this issue? I don't recall having problems with Perl |
| 26 |
> 5.8 on Leopard. |
| 27 |
> |
| 28 |
> > Per bug http://bugs.gentoo.org/show_bug.cgi?id=206455, Perl 5.10 is not yet |
| 29 |
> > in |
| 30 |
> > mainline although I've made several changes (attached) to the ebuild in |
| 31 |
> > the |
| 32 |
> > bug and *almost* have libperl building properly. It compiles fine (sans |
| 33 |
> > the |
| 34 |
> > soname patch), but I get the following error: |
| 35 |
> |
| 36 |
> That bug looks like it may going to take a while before 5.10 is in |
| 37 |
> portage, hence my preference to "fix" 5.8 if feasible. |
| 38 |
> |
| 39 |
> > >>> Source compiled. |
| 40 |
> > >>> Test phase [not enabled]: sys-devel/libperl-5.10.0 |
| 41 |
> > |
| 42 |
> > >>> Install libperl-5.10.0 into |
| 43 |
> > /Volumes/Gentoo/var/tmp/portage/sys-devel/libperl-5.10.0/image/Volumes/Gento |
| 44 |
> > o/ |
| 45 |
> > category sys-devel |
| 46 |
> > >>> Completed installing libperl-5.10.0 into |
| 47 |
> > /Volumes/Gentoo/var/tmp/portage/sys-devel/libperl-5.10.0/image/Volumes/Gento |
| 48 |
> > o/ |
| 49 |
> > |
| 50 |
> > * QA Notice: invalid reference to |
| 51 |
> > /Volumes/Gentoo/usr/lib/perl5/5.10.0/darwin-2level/CORE/libperl.1.5.10.dylib |
| 52 |
> > |
| 53 |
> > in |
| 54 |
> > /Volumes/Gentoo/var/tmp/portage/sys-devel/libperl-5.10.0/image/Volumes/Gento |
| 55 |
> > o/u |
| 56 |
> > sr/lib/libperl.1.5.10.dylib |
| 57 |
> > * ERROR: sys-devel/libperl-5.10.0 failed: |
| 58 |
> > * invalid install_name found, your application will crash at runtime |
| 59 |
> |
| 60 |
> Something is broken. There may be a darwin patch for this in 5.8. In |
| 61 |
> any case, building is broken for Darwin as the build dir library |
| 62 |
> references are stored in the dylibs, instead of the locations that the |
| 63 |
> libs would get installed in. This usually is a missing -install_name |
| 64 |
> directive (similar to -soname). |
| 65 |
> |
| 66 |
> > 1) I'm assuming the conf isn't quite right for the prefixed environment but |
| 67 |
> > I'm not sure how. Any thoughts? |
| 68 |
> |
| 69 |
> See above. |
| 70 |
> |
| 71 |
> > 2) How do you guys handle packages not in mainline? Assuming we iron out |
| 72 |
> > these build issues, what the preferred delivery mechanism/format/process |
| 73 |
> > for |
| 74 |
> > the ebuilds into the prefix tree? |
| 75 |
> |
| 76 |
> I'm very much not in favour of adding newer versions of packages not in |
| 77 |
> gentoo-x86, simply because that results in conflicts nevertheless. If |
| 78 |
> we do it, it should be a really last resort, but first I'd try and see |
| 79 |
> what the main tree devs think about it, and maybe adding it there, so we |
| 80 |
> can use its mirror in prefix. |
| 81 |
> |
| 82 |
> -- |
| 83 |
> Fabian Groffen |
| 84 |
> Gentoo on a different level |
| 85 |
|
| 86 |
-- |
| 87 |
gentoo-alt@l.g.o mailing list |
Archives