Re: [oi-dev] oi-build feature #1252 - GCC 4.6.2
Big problems - they are GCC_LIBS. We can't use different GCC version from /usr/gcc/version with GCC_LIBS from one place - because we have for example: libgcc_s.so.1 and others with the same names for different GCC versions and we have to use libgcc_s.so for -lgcc_s flags for linker. We don't have problems with tools if we are using static libs, but we have a big problems with dynamic libs - have to identify where primary libs is locate. We can put libs to different places, but it is next problem - we have to use RPATH for identification where libs locate - it is not good solution. Next problem - not critical, but present - we have package with GCC_LIBS and we have dependencies to this package in tools after builds. We have to re-build all tools after changing package name. Will be better to have ONE GCC version on the system and use it. This is example for GCC4.4 and GCC4.6 - not for GCC3 from /usr/sfw. -Igor On 11/13/11 2:06 AM, Richard Lowe richl...@richlowe.net wrote: On Sat, Nov 12, 2011 at 12:11, Igor Kozhukhov ikozhuk...@gmail.com wrote: I think that link to /usr/bin/gcc - it as mistake, because you will broke illumos-gate build. The illumos build uses /usr/sfw/bin/gcc, If the build finds or tries to use /usr/bin/gcc, something is wrong with illumos. We have to save illumos-gate build based on current userland. That's why /usr/sfw/bin/gcc must be left alone /usr/bin/gcc should be fine. Of course, it's probably a good idea for someone to test that. The patched GCC4 is not important until the changes to illumos integrate. The intent behind the way we were structuring the GCC paths going forward was that the need for a special GCC for illumos does not impact any other use of GCC in the system. That is, /usr/gcc/X.Y.Z was to be used by people who _specifically_ required a version of GCC, such as illumos, whereas /usr/bin/gcc could be a convenient, user-appropriate, version. -- Rich ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] oi-build feature #1252 - GCC 4.6.2
# ls -lh /usr/lib/gcc/x86_64-linux-gnu/4.5/libgcc_s.so lrwxrwxrwx 1 root root 35 Сен 17 08:41 /usr/lib/gcc/x86_64-linux-gnu/4.5/libgcc_s.so - /lib/x86_64-linux-gnu/libgcc_s.so.1 # ls -lh /usr/lib/gcc/x86_64-linux-gnu/4.6/libgcc_s.so lrwxrwxrwx 1 root root 35 Окт 10 22:41 /usr/lib/gcc/x86_64-linux-gnu/4.6/libgcc_s.so - /lib/x86_64-linux-gnu/libgcc_s.so.1 14.11.2011 13:43, Igor Kozhukhov пишет: Big problems - they are GCC_LIBS. We can't use different GCC version from /usr/gcc/version with GCC_LIBS from one place - because we have for example: libgcc_s.so.1 and others with the same names for different GCC versions and we have to use libgcc_s.so for -lgcc_s flags for linker. We don't have problems with tools if we are using static libs, but we have a big problems with dynamic libs - have to identify where primary libs is locate. We can put libs to different places, but it is next problem - we have to use RPATH for identification where libs locate - it is not good solution. Next problem - not critical, but present - we have package with GCC_LIBS and we have dependencies to this package in tools after builds. We have to re-build all tools after changing package name. Will be better to have ONE GCC version on the system and use it. This is example for GCC4.4 and GCC4.6 - not for GCC3 from /usr/sfw. -Igor On 11/13/11 2:06 AM, Richard Lowerichl...@richlowe.net wrote: On Sat, Nov 12, 2011 at 12:11, Igor Kozhukhovikozhuk...@gmail.com wrote: I think that link to /usr/bin/gcc - it as mistake, because you will broke illumos-gate build. The illumos build uses /usr/sfw/bin/gcc, If the build finds or tries to use /usr/bin/gcc, something is wrong with illumos. We have to save illumos-gate build based on current userland. That's why /usr/sfw/bin/gcc must be left alone /usr/bin/gcc should be fine. Of course, it's probably a good idea for someone to test that. The patched GCC4 is not important until the changes to illumos integrate. The intent behind the way we were structuring the GCC paths going forward was that the need for a special GCC for illumos does not impact any other use of GCC in the system. That is, /usr/gcc/X.Y.Z was to be used by people who _specifically_ required a version of GCC, such as illumos, whereas /usr/bin/gcc could be a convenient, user-appropriate, version. -- Rich ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] oi-build feature #1252 - GCC 4.6.2
# dpkg -S libgcc_s lib32gcc1: /usr/lib32/libgcc_s.so.1 gcc-4.5: /usr/lib/gcc/x86_64-linux-gnu/4.5/libgcc_s.so libgcc1: /lib/x86_64-linux-gnu/libgcc_s.so.1 gcc-4.6: /usr/lib/gcc/x86_64-linux-gnu/4.6/libgcc_s.so 14.11.2011 14:16, Igor Kozhukhov пишет: They are libs for builds. What libs are using tools ? Ldd ? /usr/lib/libgcc_s.so.1 - ??? I know about using libs by GCC, but how to fix dependencies ? And how to fix tool for using another GCC libs ? I have problem what I said about GCC4. Changing location for libs - it is big problems for tools with RPATH. ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] 1660 first release of The dcmtk package, Ask for review
Thank you I fixed the configuration file and the source issue. I think it is ready Paolo Marcheschi On 11/ 3/11 04:21 PM, Guido Berhoerster wrote: Hello, * Paolo Marcheschipaolo.marches...@ftgm.it [2011-10-31 19:49]: This another contribution, I'm asking for a review, dcmtk: DCMTK is a collection of libraries and applications implementing large parts the DICOM standard. It includes software for examining, constructing and converting DICOM image files, handling offline media, sending and receiving images over a network connection, as well as demonstrative image storage and worklist servers. DCMTK is is written in a mixture of ANSI C and C++. It comes in complete source code and is made available as open source software. http://dicom.offis.de/dcmtk https://bitbucket.org/paolo_marcheschi/oi-build The oi-build tools fail to download the package from ftp, I added the file. the configuration files are installed in the wrong place (/usr/etc/dcmtk/), that should be /etc/dcmtk. For autoconf/autotools projects you can usually pass --sysconfdir=/etc to configure to specify that location, I'm not sure whether userland has any predefined macros to take care of that. Please don't inline source files, if it cannot be downloaded from the upstream servers I'm sure we can arrange to mirror it from dlc.openindiana.org. ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] oi-build feature #1252 - GCC 4.6.2
I can see one real file: libgcc1: /lib/x86_64-linux-gnu/libgcc_s.so.1 And 2 different symlinks to this file: gcc-4.5: /usr/lib/gcc/x86_64-linux-gnu/4.5/libgcc_s.so gcc-4.6: /usr/lib/gcc/x86_64-linux-gnu/4.6/libgcc_s.so It is not correct if wee have different libs. And you didn't provide LDD output for some tools. -Igor On 11/14/11 3:01 PM, Igor Pashev pashev.i...@gmail.com wrote: # dpkg -S libgcc_s lib32gcc1: /usr/lib32/libgcc_s.so.1 gcc-4.5: /usr/lib/gcc/x86_64-linux-gnu/4.5/libgcc_s.so libgcc1: /lib/x86_64-linux-gnu/libgcc_s.so.1 gcc-4.6: /usr/lib/gcc/x86_64-linux-gnu/4.6/libgcc_s.so 14.11.2011 14:16, Igor Kozhukhov пишет: They are libs for builds. What libs are using tools ? Ldd ? /usr/lib/libgcc_s.so.1 - ??? I know about using libs by GCC, but how to fix dependencies ? And how to fix tool for using another GCC libs ? I have problem what I said about GCC4. Changing location for libs - it is big problems for tools with RPATH. ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] oi-build feature #1252 - GCC 4.6.2
14.11.2011 15:12, Igor Kozhukhov пишет: I can see one real file: libgcc1: /lib/x86_64-linux-gnu/libgcc_s.so.1 Try to guess what ldd will show ;-) ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] oi-build feature #1252 - GCC 4.6.2
On Mon, Nov 14, 2011 at 04:43, Igor Kozhukhov ikozhuk...@gmail.com wrote: Big problems - they are GCC_LIBS. We can't use different GCC version from /usr/gcc/version with GCC_LIBS from one place - because we have for example: libgcc_s.so.1 and others with the same names for different GCC versions and we have to use libgcc_s.so for -lgcc_s flags for linker. GCC attempt to maintain backward compatibility in their runtime libraries. This should not be a problem, and we're in the process of actually testing whether this _is_ a problem, sort of, via OI-SFE. -- Rich ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] 1660 first release of The dcmtk package, Ask for review
Hi I removed the lines and add the configure options. But it seems to put the binaries in /usr/local/bin btw I commited in this way. Paolo On 11/14/11 12:53 PM, Guido Berhoerster wrote: Hello, * Paolo Marcheschipaolo.marches...@ftgm.it [2011-11-14 12:01]: Thank you I fixed the configuration file and the source issue. yes, that's better. Please remove CONFIGURE_OPTIONS += --bindir=/usr/bin CONFIGURE_OPTIONS += --mandir=/usr/man these are set by userland automatically and /usr/man is not correct anyway (it's only a compatibility symlink to /usr/share/man). I would also suggest changing CONFIGURE_OPTIONS += --docdir=/usr/share/dcmtk/doc to CONFIGURE_OPTIONS += --docdir=$(CONFIGURE_PREFIX)/share/doc/dcmtk ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] 1660 first release of The dcmtk package, Ask for review
* Paolo Marcheschi paolo.marches...@ftgm.it [2011-11-14 15:29]: Hi I removed the lines and add the configure options. But it seems to put the binaries in /usr/local/bin Change the CONFIGURE_OPTIONS = --sysconfdir=/etc to CONFIGURE_OPTIONS += --sysconfdir=/etc The CONFIGURE_OPTIONS macro is already defined with default values for mandir/bindir/libdir etc. in configure.mk so you should not override it but only add to it. -- Guido Berhoerster ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] 1660 first release of The dcmtk package, Ask for review
Hi Thank you Very Much. I did it. Paolo On 11/14/11 04:04 PM, Guido Berhoerster wrote: * Paolo Marcheschipaolo.marches...@ftgm.it [2011-11-14 15:29]: Hi I removed the lines and add the configure options. But it seems to put the binaries in /usr/local/bin Change the CONFIGURE_OPTIONS = --sysconfdir=/etc to CONFIGURE_OPTIONS += --sysconfdir=/etc The CONFIGURE_OPTIONS macro is already defined with default values for mandir/bindir/libdir etc. in configure.mk so you should not override it but only add to it. ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] 1660 first release of The dcmtk package, Ask for review
* Paolo Marcheschi paolo.marches...@ftgm.it [2011-11-14 16:33]: Hi Thank you Very Much. I did it. Looks good now, have you tested the resulting package? -- Guido Berhoerster ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] 1660 first release of The dcmtk package, Ask for review
Yes it installs and works fine, I tried a few command with man pages and it works. Paolo On 11/14/11 05:02 PM, Guido Berhoerster wrote: * Paolo Marcheschipaolo.marches...@ftgm.it [2011-11-14 16:33]: Hi Thank you Very Much. I did it. Looks good now, have you tested the resulting package? ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] Python DTrace probes... HELP!.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am a Python core developer, and I pretend to adopt Solaris/Illumos/OpenIndiana DTrace Probes in Python, natively. There is a previous effort in http://bugs.python.org/issue4111 . I am trying to start over again in http://bugs.python.org/issue13405 . I do see dtrace probes in OI 151 python 2.6. I can see the (OLD!) patches in OpenSolaris: http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/Python-07-dtrace.diff http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/Python25-07-dtrace.diff Could you tell me where Python2.6 patches are in OpenIndiana Sourcecode URL?. Would you like to join the effort?. I am unexperienced with DTrace providers, help would be very welcomed!. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTsFz5Zlgi5GaxT1NAQKmVAP/aIPDFJTdbhCnd678qAKoH+7D0+XpxtQf FLeZFafBqPilc4UbEGmXGSP9VMUxJUPLdiWZvdlUHcsu7Ri9RWOcxvG8+KSdzb4y VVzKzTj/OXWMPISRWBfx055UUAtbD8056ce5Qkdz1CPPkfUjPKBAYR4La15Y0ISi yPb3aFm0p+I= =j8UG -END PGP SIGNATURE- ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Python DTrace probes... HELP!.
Python-2.6.4 is available on oi-build and have dtrace patch. -Igor On 11/15/11 12:02 AM, Jesus Cea j...@jcea.es wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am a Python core developer, and I pretend to adopt Solaris/Illumos/OpenIndiana DTrace Probes in Python, natively. There is a previous effort in http://bugs.python.org/issue4111 . I am trying to start over again in http://bugs.python.org/issue13405 . I do see dtrace probes in OI 151 python 2.6. I can see the (OLD!) patches in OpenSolaris: http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/Pytho n-07-dtrace.diff http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/Pytho n25-07-dtrace.diff Could you tell me where Python2.6 patches are in OpenIndiana Sourcecode URL?. Would you like to join the effort?. I am unexperienced with DTrace providers, help would be very welcomed!. - -- Jesus Cea Avion _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ jabber / xmpp:j...@jabber.org _/_/_/_/ _/_/_/_/_/ . _/_/ _/_/_/_/ _/_/ _/_/ Things are not so easy _/_/ _/_/_/_/ _/_/_/_/ _/_/ My name is Dump, Core Dump _/_/_/_/_/_/ _/_/ _/_/ El amor es poner tu felicidad en la felicidad de otro - Leibniz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBTsFz5Zlgi5GaxT1NAQKmVAP/aIPDFJTdbhCnd678qAKoH+7D0+XpxtQf FLeZFafBqPilc4UbEGmXGSP9VMUxJUPLdiWZvdlUHcsu7Ri9RWOcxvG8+KSdzb4y VVzKzTj/OXWMPISRWBfx055UUAtbD8056ce5Qkdz1CPPkfUjPKBAYR4La15Y0ISi yPb3aFm0p+I= =j8UG -END PGP SIGNATURE- ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Feature 1768 - add dovecot to oi-build
On Sat, Nov 12, 2011 at 11:17:10PM +, Colin Ellis wrote: bitbucket here: https://bitbucket.org/cellis_oidev/oi-build/changeset/d7c2addf18b7 Awesome, this one was on my todo list. Less work for me :) 1) no need to set --prefix --sbindir yourself 2) $(ETCDIR) instead of /etc 3) did the `gmake publish` not complain about the missing info.classification? 4) Do we really need to ship all those .a and .la files? Solaris likes shared libs a lot - and handles them pretty well too. 5) Do the files in usr/share/doc have the doc facet? (They should; you can check the published manifest.) 6) Is there an SMF manifest? Thanks! Jeff. -- All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can’t get them together again, there must be a reason. By all means, do not use a hammer. — IBM Manual, 1925 ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] 1660 first release of The dcmtk package, Ask for review
On Mon, Nov 14, 2011 at 06:55:39PM +0100, Paolo Marcheschi wrote: Yes it installs and works fine, I tried a few command with man pages and it works. Cool. Looks good to me. Jeff. Paolo On 11/14/11 05:02 PM, Guido Berhoerster wrote: * Paolo Marcheschipaolo.marches...@ftgm.it [2011-11-14 16:33]: Hi Thank you Very Much. I did it. Looks good now, have you tested the resulting package? ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev -- NT is to UNIX what a doughnut is to a particle accelerator. ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] oi-build feature #1252 - GCC 4.6.2
On Mon, 2011-11-14 at 20:04 -0500, Josef 'Jeff' Sipek wrote: Keep in mind that we have mediated links - something that debian doesn't have. Is Debian exceptional as a Linux distribution in this respect? ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] oi-build feature #1252 - GCC 4.6.2
15.11.2011 05:04, Josef 'Jeff' Sipek пишет: On Mon, Nov 14, 2011 at 03:19:44PM +0400, Igor Pashev wrote: 14.11.2011 15:12, Igor Kozhukhov пишет: I can see one real file: libgcc1: /lib/x86_64-linux-gnu/libgcc_s.so.1 Try to guess what ldd will show ;-) Keep in mind that we have mediated links - something that debian doesn't have. It is not true, Debian has update-alternatives. ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
