From lrhazi at gmail.com Thu Apr 7 02:15:06 2011 From: lrhazi at gmail.com (Mohamed Lrhazi) Date: Wed, 6 Apr 2011 20:15:06 -0400 Subject: [csw-users] Error buiding ruby gem sys-proctable (missing procfs.h) Message-ID: What do I need to install to get this to work: [root at albany opt]$ gem install --no-rdoc --no-ri sys-proctable Building native extensions. This could take a while... sh: make: not found ERROR: Error installing sys-proctable: ERROR: Failed to build gem native extension. /opt/csw/bin/ruby extconf.rb checking for rb_pid_t in ruby.h... yes checking for procfs.h... no creating Makefile make Thanks a lot, Mohamed. From bwalton at opencsw.org Thu Apr 7 02:59:36 2011 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 06 Apr 2011 20:59:36 -0400 Subject: [csw-users] Error buiding ruby gem sys-proctable (missing procfs.h) In-Reply-To: References: Message-ID: <1302137837-sup-5252@pinkfloyd.chass.utoronto.ca> Excerpts from Mohamed Lrhazi's message of Wed Apr 06 20:15:06 -0400 2011: Hi Mohamed, > What do I need to install to get this to work: Are you running the current ruby version? Can you provide the output of the following please: pkgparam CSWruby18 VERSION which make alternatives --display rbconfig18 Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From lrhazi at gmail.com Thu Apr 7 03:09:44 2011 From: lrhazi at gmail.com (Mohamed Lrhazi) Date: Wed, 6 Apr 2011 21:09:44 -0400 Subject: [csw-users] Error buiding ruby gem sys-proctable (missing procfs.h) In-Reply-To: <1302137837-sup-5252@pinkfloyd.chass.utoronto.ca> References: <1302137837-sup-5252@pinkfloyd.chass.utoronto.ca> Message-ID: Here is the info: [root at albany csw]$ pkgparam CSWruby18 VERSION pkgparam: ERROR: unable to locate parameter information for "CSWruby18" [root at albany csw]$ pkg-get -l|grep ruby libruby1 ruby rubydev rubygems [root at albany csw]$ pkginfo CSWruby application CSWruby ruby - An object-oriented language for quick and easy programming. [root at albany csw]$ pkginfo -l CSWruby PKGINST: CSWruby NAME: ruby - An object-oriented language for quick and easy programming. CATEGORY: application ARCH: sparc VERSION: 1.8.7p302,REV=2010.12.04 BASEDIR: / VENDOR: ftp://ftp.ruby-lang.org/pub/ruby/ packaged for CSW by Ben Walton PSTAMP: bwalton at current9s-20101204182920 INSTDATE: Mar 28 2011 16:23 HOTLINE: http://www.opencsw.org/bugtrack/ EMAIL: bwalton at opencsw.org STATUS: completely installed FILES: 674 installed pathnames 8 shared pathnames 87 directories 35 executables 9835 blocks used (approx) I had no 'make" in my path, so I set it: [root at albany csw]$ which make no make in /opt/csw/bin /opt/csw/sbin /opt/openssh/bin /usr/bin /bin /usr/sbin /sbin /usr/ucb /usr/local/bin /usr/bin/X11 /etc /opt/EMCpower/bin/64 /etc/emc/bin [root at albany csw]$ /opt/csw/gnu/make [root at albany csw]$ export PATH=/opt/csw/gnu:$PATH/sbin:$PATH [root at albany csw]$ which make /opt/csw/gnu/make [root at albany csw]$ ch)`gem ': gem install --no-rdoc --no-ri sys-proctable Building native extensions. This could take a while... ERROR: Error installing sys-proctable: ERROR: Failed to build gem native extension. /opt/csw/bin/ruby extconf.rb checking for rb_pid_t in ruby.h... yes checking for procfs.h... no creating Makefile make /opt/csw/gcc4/bin/gcc -I. -I/opt/csw/lib/ruby/1.8/sparc-solaris2.9 -I/opt/csw/lib/ruby/1.8/sparc-solaris2.9 -I. -DHAVE_TYPE_RB_PID_T -I/opt/csw/include -D_FILE_OFFSET_BITS=64 -fPIC -O2 -pipe -mcpu=v8 -fPIC -c proctable.c proctable.c: In function 'proctable_ps': proctable.c:224: error: 'as_file' undeclared (first use in this function) proctable.c:224: error: (Each undeclared identifier is reported only once proctable.c:224: error: for each function it appears in.) make: *** [proctable.o] Error 1 Last command you asked for: [root at albany csw]$ alternatives --display rbconfig18 Installed alternatives for rbconfig18 are: Thanks a lot. On Wed, Apr 6, 2011 at 8:59 PM, Ben Walton wrote: > Excerpts from Mohamed Lrhazi's message of Wed Apr 06 20:15:06 -0400 2011: > > Hi Mohamed, > >> What do I need to install to get this to work: > > Are you running the current ruby version? ?Can you provide the output > of the following please: > > pkgparam CSWruby18 VERSION > which make > alternatives --display rbconfig18 > > Thanks > -Ben > -- > Ben Walton > Systems Programmer - CHASS > University of Toronto > C:416.407.5610 | W:416.978.4302 > > _______________________________________________ > users mailing list > users at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/users > From bwalton at opencsw.org Thu Apr 7 03:24:49 2011 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 06 Apr 2011 21:24:49 -0400 Subject: [csw-users] Error buiding ruby gem sys-proctable (missing procfs.h) In-Reply-To: References: <1302137837-sup-5252@pinkfloyd.chass.utoronto.ca> Message-ID: <1302138816-sup-8530@pinkfloyd.chass.utoronto.ca> Excerpts from Mohamed Lrhazi's message of Wed Apr 06 21:09:44 -0400 2011: Hi Mohamed, > [root at albany csw]$ pkgparam CSWruby18 VERSION > pkgparam: ERROR: unable to locate parameter information for "CSWruby18" Ok, first you should update to the current ruby packages. Make sure you add CSWruby18-gcc4 to you can build with gcc4. This handles the move away from the cswrbconfig tool. These packages should have hit the mirrors a few days ago. > I had no 'make" in my path, so I set it: I may need to update the extconf.rb handling to use gmake and/or force /opt/csw/gnu into the path to make this nicer. I run with that on my PATH by default, so I've missed this particular problem. > [root at albany csw]$ ch)`gem ': gem install --no-rdoc --no-ri sys-proctable > Building native extensions. This could take a while... > ERROR: Error installing sys-proctable: > ERROR: Failed to build gem native extension. > > /opt/csw/bin/ruby extconf.rb > checking for rb_pid_t in ruby.h... yes > checking for procfs.h... no > creating Makefile > > make > /opt/csw/gcc4/bin/gcc -I. -I/opt/csw/lib/ruby/1.8/sparc-solaris2.9 > -I/opt/csw/lib/ruby/1.8/sparc-solaris2.9 -I. -DHAVE_TYPE_RB_PID_T > -I/opt/csw/include -D_FILE_OFFSET_BITS=64 -fPIC -O2 -pipe -mcpu=v8 > -fPIC -c proctable.c > proctable.c: In function 'proctable_ps': > proctable.c:224: error: 'as_file' undeclared (first use in this function) > proctable.c:224: error: (Each undeclared identifier is reported only once > proctable.c:224: error: for each function it appears in.) > make: *** [proctable.o] Error 1 This is a bug in the gem: --snip-- #ifdef HAVE_PROCFS_H struct psinfo p; char as_file[MAXPATHLEN]; #else struct prpsinfo p; #endif ... strcpy(as_file, "/proc/"); --snip-- It's using a variable that may not be defined. You should report this upstream. The larger issue though is that have_header in extconf.rb isn't locating procps.h in /usr/include. I'll see if I can track down either or both of a) why not, b) a work around. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From lrhazi at gmail.com Thu Apr 7 03:45:01 2011 From: lrhazi at gmail.com (Mohamed Lrhazi) Date: Wed, 6 Apr 2011 21:45:01 -0400 Subject: [csw-users] Error buiding ruby gem sys-proctable (missing procfs.h) In-Reply-To: <1302138816-sup-8530@pinkfloyd.chass.utoronto.ca> References: <1302137837-sup-5252@pinkfloyd.chass.utoronto.ca> <1302138816-sup-8530@pinkfloyd.chass.utoronto.ca> Message-ID: Thanks a lot Ben. On Wed, Apr 6, 2011 at 9:24 PM, Ben Walton wrote: > Excerpts from Mohamed Lrhazi's message of Wed Apr 06 21:09:44 -0400 2011: > > Hi Mohamed, > >> [root at albany csw]$ pkgparam CSWruby18 VERSION >> pkgparam: ERROR: unable to locate parameter information for "CSWruby18" > > Ok, first you should update to the current ruby packages. ?Make sure > you add CSWruby18-gcc4 to you can build with gcc4. ?This handles the > move away from the cswrbconfig tool. ?These packages should have hit > the mirrors a few days ago. > >> I had no 'make" in my path, so I set it: > > I may need to update the extconf.rb handling to use gmake and/or force > /opt/csw/gnu into the path to make this nicer. ?I run with that on my > PATH by default, so I've missed this particular problem. > >> [root at albany csw]$ ch)`gem ': gem install ?--no-rdoc --no-ri sys-proctable >> Building native extensions. ?This could take a while... >> ERROR: ?Error installing sys-proctable: >> ? ? ? ? ERROR: Failed to build gem native extension. >> >> /opt/csw/bin/ruby extconf.rb >> checking for rb_pid_t in ruby.h... yes >> checking for procfs.h... no >> creating Makefile >> >> make >> /opt/csw/gcc4/bin/gcc -I. -I/opt/csw/lib/ruby/1.8/sparc-solaris2.9 >> -I/opt/csw/lib/ruby/1.8/sparc-solaris2.9 -I. -DHAVE_TYPE_RB_PID_T >> -I/opt/csw/include -D_FILE_OFFSET_BITS=64 ?-fPIC -O2 -pipe -mcpu=v8 >> -fPIC ? -c proctable.c >> proctable.c: In function 'proctable_ps': >> proctable.c:224: error: 'as_file' undeclared (first use in this function) >> proctable.c:224: error: (Each undeclared identifier is reported only once >> proctable.c:224: error: for each function it appears in.) >> make: *** [proctable.o] Error 1 > > This is a bug in the gem: > > --snip-- > #ifdef HAVE_PROCFS_H > ? struct psinfo p; > ? char as_file[MAXPATHLEN]; > #else > ? struct prpsinfo p; > #endif > > ... > > ? ? strcpy(as_file, "/proc/"); > > --snip-- > > It's using a variable that may not be defined. ?You should report this > upstream. ?The larger issue though is that have_header in extconf.rb > isn't locating procps.h in /usr/include. ?I'll see if I can track down > either or both of a) why not, b) a work around. > > Thanks > -Ben > -- > Ben Walton > Systems Programmer - CHASS > University of Toronto > C:416.407.5610 | W:416.978.4302 > > _______________________________________________ > users mailing list > users at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/users > From lrhazi at gmail.com Thu Apr 7 03:54:08 2011 From: lrhazi at gmail.com (Mohamed Lrhazi) Date: Wed, 6 Apr 2011 21:54:08 -0400 Subject: [csw-users] upgrade all lost bin/ruby ! Message-ID: It seems I lost this after a pkg-get -U;pkg-get -u How do I restore /opt/csw/bin/ruby [root at albany csw]$ ch)`gem ': gem install --no-rdoc --no-ri sys-proctable bash: /opt/csw/bin/gem: /opt/csw/bin/ruby: bad interpreter: No such file or directory [root at albany csw]$ /opt/csw/bin/ruby bash: /opt/csw/bin/ruby: No such file or directory [root at albany csw]$ pkg-get -l|grep ruby libruby1 libruby18_1 ruby18 ruby18_dev ruby18_gcc4 ruby_stub rubydev_stub rubygems [root at albany csw]$ ls /opt/csw/bin/ruby* /opt/csw/bin/ruby18 From bwalton at opencsw.org Thu Apr 7 04:00:28 2011 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 06 Apr 2011 22:00:28 -0400 Subject: [csw-users] upgrade all lost bin/ruby ! In-Reply-To: References: Message-ID: <1302141549-sup-640@pinkfloyd.chass.utoronto.ca> Excerpts from Mohamed Lrhazi's message of Wed Apr 06 21:54:08 -0400 2011: > It seems I lost this after a pkg-get -U;pkg-get -u > How do I restore /opt/csw/bin/ruby /opt/csw/bin/ruby is supposed to be a symlink to /opt/csw/bin/ruby18. This is handled by the alternatives mechanism. What is the output of: alternatives --list alternatives --display ruby ?? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From bwalton at opencsw.org Thu Apr 7 04:13:11 2011 From: bwalton at opencsw.org (Ben Walton) Date: Wed, 06 Apr 2011 22:13:11 -0400 Subject: [csw-users] Error buiding ruby gem sys-proctable (missing procfs.h) In-Reply-To: References: <1302137837-sup-5252@pinkfloyd.chass.utoronto.ca> <1302138816-sup-8530@pinkfloyd.chass.utoronto.ca> Message-ID: <1302142246-sup-6214@pinkfloyd.chass.utoronto.ca> Excerpts from Mohamed Lrhazi's message of Wed Apr 06 21:45:01 -0400 2011: > Thanks a lot Ben. Ok, the failure to find procfs.h is based on: --snipped from mkmf.log -- have_header: checking for procfs.h... -------------------- no "/opt/csw/gcc4/bin/gcc -E -I. -I/opt/csw/lib/ruby/1.8/i386-solaris2.9 -I. -I/opt/csw/include -D_FILE_OFFSET_BITS=64 -I/opt/csw/include -mtune=i686 -O2 -pipe -m32 -march=i386 -fPIC conftest.c -o conftest.i" In file included from /usr/include/procfs.h:26, from conftest.c:1: /usr/include/sys/procfs.h:45:2: error: #error "Cannot use procfs in the large file compilation environment" checked program was: /* begin */ 1: #include /* end */ --snip-- You've hit a lovely little issue that's not going to be easy to work around... http://opensolaris.org/jive/thread.jspa?threadID=76693 HTH. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From lrhazi at gmail.com Thu Apr 7 04:22:24 2011 From: lrhazi at gmail.com (Mohamed Lrhazi) Date: Wed, 6 Apr 2011 22:22:24 -0400 Subject: [csw-users] pkg-get -i pkgutil removed my /opt/csw symlink!! Message-ID: My /opt/csw was a symlink to soem other place (an nfs mount point)... After runinng pkg-get -i pkgutil && pkgrm CSWpkgget It seems I have a brand new, mostly empty, /opt/csw, which is a real dir, not a symlink... Is that expected? maybe I should be reading those prompts that ask if I want stuff done :) Thanks, Mohamed. From bonivart at opencsw.org Thu Apr 7 09:10:19 2011 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 7 Apr 2011 09:10:19 +0200 Subject: [csw-users] pkg-get -i pkgutil removed my /opt/csw symlink!! In-Reply-To: References: Message-ID: On Thu, Apr 7, 2011 at 4:22 AM, Mohamed Lrhazi wrote: > My /opt/csw was a symlink to soem other place (an nfs mount point)... > After runinng pkg-get -i pkgutil && pkgrm CSWpkgget > > It seems I have a brand new, mostly empty, /opt/csw, which is a real > dir, not a symlink... > > Is that expected? maybe I should be reading those prompts that ask if > I want stuff done :) Sorry about that. Pkgadd is a little brutal in these edge cases but there should be no real harm done, pkgutil doesn't contain many files so if you just move them to their respective place where you have your CSW packages and recreate the link you should be good. /peter From maciej at opencsw.org Thu Apr 7 10:15:24 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Thu, 7 Apr 2011 09:15:24 +0100 Subject: [csw-users] pkg-get -i pkgutil removed my /opt/csw symlink!! In-Reply-To: References: Message-ID: 2011/4/7 Peter Bonivart : > On Thu, Apr 7, 2011 at 4:22 AM, Mohamed Lrhazi wrote: >> My /opt/csw was a symlink to soem other place (an nfs mount point)... >> After runinng pkg-get -i pkgutil && pkgrm CSWpkgget >> >> It seems I have a brand new, mostly empty, /opt/csw, which is a real >> dir, not a symlink... >> >> Is that expected? maybe I should be reading those prompts that ask if >> I want stuff done :) > > Sorry about that. Pkgadd is a little brutal in these edge cases Is there a way to make things better in such a case? For example, such symlink could be detected in a preinstall script, and a informative message could be displayed, along the lines of: """/opt/csw is a symlink to . pkgadd will remove the symlink and replace it with a directory. There is no easy workaround for that. Files from /opt/csw will have to be moved to and the symlink will have to be re-created by the system administrator (you). Continuing in 5... 4... 3... """ The same test could be done for /opt. Maciej From lrhazi at gmail.com Thu Apr 7 13:29:54 2011 From: lrhazi at gmail.com (Mohamed Lrhazi) Date: Thu, 7 Apr 2011 07:29:54 -0400 Subject: [csw-users] pkg-get -i pkgutil removed my /opt/csw symlink!! In-Reply-To: References: Message-ID: One other thing I wish pkg-get and pkgutil did is simply to prompt me for a confirmation to install the pkg and all its deps, like yum does, before actualy starting. RFE. Thanks. 2011/4/7 Maciej Blizi?ski : > 2011/4/7 Peter Bonivart : >> On Thu, Apr 7, 2011 at 4:22 AM, Mohamed Lrhazi wrote: >>> My /opt/csw was a symlink to soem other place (an nfs mount point)... >>> After runinng pkg-get -i pkgutil && pkgrm CSWpkgget >>> >>> It seems I have a brand new, mostly empty, /opt/csw, which is a real >>> dir, not a symlink... >>> >>> Is that expected? maybe I should be reading those prompts that ask if >>> I want stuff done :) >> >> Sorry about that. Pkgadd is a little brutal in these edge cases > > Is there a way to make things better in such a case? ?For example, > such symlink could be detected in a preinstall script, and a > informative message could be displayed, along the lines of: > > """/opt/csw is a symlink to . ?pkgadd will remove the symlink > and replace it with a directory. ?There is no easy workaround for > that. ?Files from /opt/csw will have to be moved to and the > symlink will have to be re-created by the system administrator (you). > > Continuing in 5... 4... 3... > """ > > The same test could be done for /opt. > > Maciej > _______________________________________________ > users mailing list > users at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/users > From bonivart at opencsw.org Thu Apr 7 13:34:55 2011 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 7 Apr 2011 13:34:55 +0200 Subject: [csw-users] pkg-get -i pkgutil removed my /opt/csw symlink!! In-Reply-To: References: Message-ID: On Thu, Apr 7, 2011 at 1:29 PM, Mohamed Lrhazi wrote: > One other thing I wish pkg-get and pkgutil did is simply to prompt me > for a confirmation to install the pkg and all its deps, like yum does, > before actualy starting. RFE. Pkgutil does ask you if there's more than one package to be installed. /peter From lrhazi at gmail.com Thu Apr 7 13:38:45 2011 From: lrhazi at gmail.com (Mohamed Lrhazi) Date: Thu, 7 Apr 2011 07:38:45 -0400 Subject: [csw-users] pkg-get -i pkgutil removed my /opt/csw symlink!! In-Reply-To: References: Message-ID: Oh... thought I tested, but your right, that's perfect.thanks. On Thu, Apr 7, 2011 at 7:34 AM, Peter Bonivart wrote: > On Thu, Apr 7, 2011 at 1:29 PM, Mohamed Lrhazi wrote: >> One other thing I wish pkg-get and pkgutil did is simply to prompt me >> for a confirmation to install the pkg and all its deps, like yum does, >> before actualy starting. RFE. > > Pkgutil does ask you if there's more than one package to be installed. > > /peter > _______________________________________________ > users mailing list > users at lists.opencsw.org > https://lists.opencsw.org/mailman/listinfo/users > From maciej at opencsw.org Thu Apr 7 13:42:18 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Thu, 7 Apr 2011 12:42:18 +0100 Subject: [csw-users] pkg-get -i pkgutil removed my /opt/csw symlink!! In-Reply-To: References: Message-ID: 2011/4/7 Peter Bonivart : > Pkgutil does ask you if there's more than one package to be installed. Yes. By adding the -y flag you can make pkgutil install packages without asking questions. This is useful if you're working on automation, where pkgutil needs to run non-interactively. Maciej From bwalton at opencsw.org Thu Apr 7 15:20:59 2011 From: bwalton at opencsw.org (Ben Walton) Date: Thu, 07 Apr 2011 09:20:59 -0400 Subject: [csw-users] apache2 updates Message-ID: <1302182335-sup-1495@pinkfloyd.chass.utoronto.ca> Hi All, A quick note about some changes in the apache2 updates... If you don't have CSWapache2 installed, you'll want to install it. It now contains the actual files (binaries, config, etc) and the smf integration. As it was possible to have a working apache2 install without CSWapache2 previously[1], this is something you'll want to pay attention to. Thanks -Ben [1] It's still possible to get a non-working install due to external dependencies, but bugs have been filed against the apprporiate packages. -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From Nitin.Kapoor at Sensis.com Thu Apr 7 21:41:39 2011 From: Nitin.Kapoor at Sensis.com (Kapoor, Nitin) Date: Thu, 7 Apr 2011 15:41:39 -0400 Subject: [csw-users] GCC4 Warnings Message-ID: Hi Everyone, I am running Solaris 10 on a Sparc box. -bash-3.00$ uname -a SunOS starshot 5.10 Generic_142909-17 sun4v sparc SUNW,SPARC-Enterprise-T5120 I installed GCC4 package vis pkg-get command. Pkg-get installed all the dependencies and everything looked ok. But there were couple of issues:- 1. When Pkg-get installed these GCC4 and its dependencies, it looked as if these packages were for SunOS5.8 or SunOS5.9. Following are the exact names of the packages:- * binutils-2.19,REV=2008.11.17-SunOS5.8-sparc-CSW.pkg * cas_texinfo-1.42,REV=2010.11.26-SunOS5.9-all-CSW.pkg * gcc4core-4.3.3,REV=2009.05.07-SunOS5.8-sparc-CSW.pkg * gcc4corert-4.3.3,REV=2009.05.07-SunOS5.8-sparc-CSW.pkg * gcc4g++-4.3.3,REV=2009.05.07-SunOS5.8-sparc-CSW.pkg * gcc4g++rt-4.3.3,REV=2009.05.07-SunOS5.8-sparc-CSW.pkg * ... 2. When I build packages using GCC4 I get the following warning: ld: warning: file /opt/csw/gcc4/lib/gcc/sparc-sun-solaris2.8/4.3.3/../../../libstdc++.so: linked to /opt/csw/gcc4/lib/libstdc++.so: attempted multiple inclusion of file Thanks!!!! - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - -------------- next part -------------- An HTML attachment was scrubbed... URL: From bonivart at opencsw.org Thu Apr 7 22:52:31 2011 From: bonivart at opencsw.org (Peter Bonivart) Date: Thu, 7 Apr 2011 22:52:31 +0200 Subject: [csw-users] GCC4 Warnings In-Reply-To: References: Message-ID: On Thu, Apr 7, 2011 at 9:41 PM, Kapoor, Nitin wrote: > 1.?????? When Pkg-get installed these GCC4 and its dependencies, it looked > as if these packages were for SunOS5.8 or SunOS5.9. Following are the exact > names of the packages:- It's very common that we use Solaris 8 (or currently 9) as base OS. Only in some cases we build on each OS to avoid bugs, enable features or enhance performance. /peter From Nitin.Kapoor at Sensis.com Fri Apr 8 17:42:39 2011 From: Nitin.Kapoor at Sensis.com (Kapoor, Nitin) Date: Fri, 8 Apr 2011 11:42:39 -0400 Subject: [csw-users] GCC4 ld Warnings Message-ID: Hi Everyone, I am running Solaris 10 on a Sparc box. -bash-3.00$ uname -a SunOS starshot 5.10 Generic_142909-17 sun4v sparc SUNW,SPARC-Enterprise-T5120 I installed GCC4 package vis pkg-get command. Pkg-get installed all the dependencies and everything looked ok, but when I compile using GCC4 I get the following warning: ld: warning: file /opt/csw/gcc4/lib/gcc/sparc-sun-solaris2.8/4.3.3/../../../libstdc++.so: linked to /opt/csw/gcc4/lib/libstdc++.so: attempted multiple inclusion of file Thanks!!!! - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - -------------- next part -------------- An HTML attachment was scrubbed... URL: From maciej at opencsw.org Sat Apr 9 10:28:31 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Sat, 9 Apr 2011 09:28:31 +0100 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: References: Message-ID: 2011/4/8 Kapoor, Nitin : > ld: warning: file > /opt/csw/gcc4/lib/gcc/sparc-sun-solaris2.8/4.3.3/../../../libstdc++.so: > linked to /opt/csw/gcc4/lib/libstdc++.so: attempted multiple inclusion of > file I'm not sure whether this has got to do with OpenCSW gcc packages, or the compilation procedure you're using. Are you able to provide a minimal example reproducing the issue? E.g. gtar xfvz foo.tar.gz cd foo gmake ... ...attempted multiple inclusion of file Maciej From lrhazi at gmail.com Sun Apr 10 22:47:46 2011 From: lrhazi at gmail.com (Mohamed Lrhazi) Date: Sun, 10 Apr 2011 16:47:46 -0400 Subject: [csw-users] Disable sudo logfile Message-ID: How do I force sudo to not use a logfile, and use syslog only? It seems to default to: /var/opt/csw/log/sudo/sudolog The man page says to negate "logfile", in the sudoers config file, but cannot figure out how to do that. the man page also says that by default sudo does not use a file, but apparently in csw, it does. My current workaround is to put this in sudoers: Defaults syslog=auth Defaults logfile=/dev/null Thanks, Mohamed. From Nitin.Kapoor at Sensis.com Mon Apr 11 15:21:31 2011 From: Nitin.Kapoor at Sensis.com (Kapoor, Nitin) Date: Mon, 11 Apr 2011 09:21:31 -0400 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: References: Message-ID: Thanks Maciej for looking into this. So for example I am trying to compile xerces, xqilla, or Google protobuf etc... etc... Step that I took to build were: MY LD_LIBRARY_PATH is set to /opt/csw/gcc4/lib 1). gunzip xerces-c-3.1.1.tar.gz 2). Tar xvf xerces-c-3.1.1.tar 3). Cd xerces-c-3.1.1 4). ./configure 5). make ...after a while into make it starts outputting these ld warnings. ld: warning: file /opt/csw/gcc4/lib/gcc/sparc-sun-solaris2.8/4.3.3/../../../libstdc++.so: linked to /opt/csw/gcc4/lib/libstdc++.so: attempted multiple inclusion of file Thanks!!! -----Original Message----- From: users-bounces+nkapoor=sensis.com at lists.opencsw.org [mailto:users-bounces+nkapoor=sensis.com at lists.opencsw.org] On Behalf Of Maciej Blizinski Sent: Saturday, April 09, 2011 4:29 AM To: Questions and discussions Subject: Re: [csw-users] GCC4 ld Warnings 2011/4/8 Kapoor, Nitin : > ld: warning: file > /opt/csw/gcc4/lib/gcc/sparc-sun-solaris2.8/4.3.3/../../../libstdc++.so: > linked to /opt/csw/gcc4/lib/libstdc++.so: attempted multiple inclusion of > file I'm not sure whether this has got to do with OpenCSW gcc packages, or the compilation procedure you're using. Are you able to provide a minimal example reproducing the issue? E.g. gtar xfvz foo.tar.gz cd foo gmake ... ...attempted multiple inclusion of file Maciej _______________________________________________ users mailing list users at lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/users - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - From bwalton at opencsw.org Mon Apr 11 15:26:23 2011 From: bwalton at opencsw.org (Ben Walton) Date: Mon, 11 Apr 2011 09:26:23 -0400 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: References: Message-ID: <1302528310-sup-2363@pinkfloyd.chass.utoronto.ca> Excerpts from Kapoor, Nitin's message of Mon Apr 11 09:21:31 -0400 2011: Hi Nitin, > So for example I am trying to compile xerces, xqilla, or Google protobuf etc... etc... > Step that I took to build were: > MY LD_LIBRARY_PATH is set to /opt/csw/gcc4/lib You shouldn't need to set this variable and it may be the cause of your issue. Pass -L /opt/csw/gcc4/lib and -R /opt/csw/gcc4/lib if gcc isn't adding the required paths itself. This may not be the whole story, but it won't be helping you. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 From maciej at opencsw.org Mon Apr 11 16:14:27 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Mon, 11 Apr 2011 15:14:27 +0100 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: References: Message-ID: 2011/4/11 Kapoor, Nitin : > So for example I am trying to compile xerces, xqilla, or Google protobuf etc... etc... I believe we have packages with xerces and protobuf: http://www.opencsw.org/packages/CSWlibxerces-c3-1/ http://www.opencsw.org/packages/CSWprotobuf/ Is the issue that you need them to be compiled with gcc? If this is the case, we can look into building gcc packages as well. Maciej From Nitin.Kapoor at Sensis.com Mon Apr 11 16:18:18 2011 From: Nitin.Kapoor at Sensis.com (Kapoor, Nitin) Date: Mon, 11 Apr 2011 10:18:18 -0400 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: References: Message-ID: Well the issue remains when we build our own software with GCC4. -----Original Message----- From: users-bounces+nkapoor=sensis.com at lists.opencsw.org [mailto:users-bounces+nkapoor=sensis.com at lists.opencsw.org] On Behalf Of Maciej Blizinski Sent: Monday, April 11, 2011 10:14 AM To: Questions and discussions Subject: Re: [csw-users] GCC4 ld Warnings 2011/4/11 Kapoor, Nitin : > So for example I am trying to compile xerces, xqilla, or Google protobuf etc... etc... I believe we have packages with xerces and protobuf: http://www.opencsw.org/packages/CSWlibxerces-c3-1/ http://www.opencsw.org/packages/CSWprotobuf/ Is the issue that you need them to be compiled with gcc? If this is the case, we can look into building gcc packages as well. Maciej _______________________________________________ users mailing list users at lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/users - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - From maciej at opencsw.org Mon Apr 11 17:36:52 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Mon, 11 Apr 2011 16:36:52 +0100 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: References: Message-ID: 2011/4/11 Kapoor, Nitin : > Well the issue remains when we build our own software with GCC4. Yes, so these are 2 separate issues: one is multiple inclusions. Ben's advice is most probably the way to go: do not use LD_LIBRARY_PATH, use -L and -R instead. The second issue is what seems to be effort duplication. Are there any reasons not to use OpenCSW xerces and/or protobuf? I'm asking, because if you don't use these packages because there's something that doesn't work for you, we need to fix the packages. Regards, Maciej From Nitin.Kapoor at Sensis.com Mon Apr 11 21:38:22 2011 From: Nitin.Kapoor at Sensis.com (Kapoor, Nitin) Date: Mon, 11 Apr 2011 15:38:22 -0400 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: <1302528310-sup-2363@pinkfloyd.chass.utoronto.ca> References: <1302528310-sup-2363@pinkfloyd.chass.utoronto.ca> Message-ID: OK. Installed Solaris 10 to start fresh and then installed GCC4. I did not set LD_LIBRARY_PATH this time. Updated $PATH to include /opt/csw/gcc4/bin Then, I configured the source with the following command:- ./configure LDFLAGS=-R/opt/csw/gcc4/lib ( I had to pass the LDFLAGS to the configure script otherwise it was not able to locate libstdc++ libs.) make But I am still getting those warnings. -----Original Message----- From: users-bounces+nkapoor=sensis.com at lists.opencsw.org [mailto:users-bounces+nkapoor=sensis.com at lists.opencsw.org] On Behalf Of Ben Walton Sent: Monday, April 11, 2011 9:26 AM To: users Subject: Re: [csw-users] GCC4 ld Warnings Excerpts from Kapoor, Nitin's message of Mon Apr 11 09:21:31 -0400 2011: Hi Nitin, > So for example I am trying to compile xerces, xqilla, or Google protobuf etc... etc... > Step that I took to build were: > MY LD_LIBRARY_PATH is set to /opt/csw/gcc4/lib You shouldn't need to set this variable and it may be the cause of your issue. Pass -L /opt/csw/gcc4/lib and -R /opt/csw/gcc4/lib if gcc isn't adding the required paths itself. This may not be the whole story, but it won't be helping you. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 _______________________________________________ users mailing list users at lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/users - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - From Nitin.Kapoor at Sensis.com Mon Apr 11 21:43:41 2011 From: Nitin.Kapoor at Sensis.com (Kapoor, Nitin) Date: Mon, 11 Apr 2011 15:43:41 -0400 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: References: Message-ID: Here is the exact warning:- libtool: link: g++ -Wall -Werror -ggdb -O0 -o recorder recorder-RecorderMain.o -L/usr/local/lib -L/opt/csw/gcc4/lib -L/export/home/sbsmlat/workspace/system/app/recorder/Debug/.lib -L/export/home/sbsmlat/install/Debug/lib -L/export/home/sbsmlat/workspace/system_libs/Debug/.lib -L/usr/local/boost/lib -L/export/home/sbsmlat/xerces-c-3.1.1/src /export/home/sbsmlat/workspace/system/app/recorder/Debug/recorder/.libs/librecorder.a /export/home/sbsmlat/install/Debug/lib/libmlat_component.so /export/home/sbsmlat/install/Debug/lib/libmlat_adaptation.so /export/home/sbsmlat/install/Debug/lib/libmlat_comm.so /export/home/sbsmlat/install/Debug/lib/libmlat_message.so /usr/local/lib/libprotobuf.so -lz /export/home/sbsmlat/install/Debug/lib/libmlat_repository.so -lboost_filesystem /export/home/sbsmlat/install/Debug/lib/libmlat_utility.so /export/home/sbsmlat/install/Debug/lib/libmlat_transform.so -lboost_system -lboost_thread -lboost_date_time -lboost_program_options /usr/local/lib/libxqilla.so /usr/local/lib/libxerces-c.so -licuuc -licudata -lnsl -lsocket -lpthread -ldl /opt/csw/gcc4/lib/libstdc++.so -lm -pthreads -Wl,-R -Wl,/export/home/sbsmlat/install/Debug/lib -Wl,-R -Wl,/usr/local/lib -Wl,-R -Wl,/opt/csw/gcc4/lib -Wl,-R -Wl,/export/home/sbsmlat/install/Debug/lib -Wl,-R -Wl,/usr/local/lib -Wl,-R -Wl,/opt/csw/gcc4/lib ld: warning: file /opt/csw/gcc4/lib/libstdc++.so: attempted multiple inclusion of file Thanks!!! -----Original Message----- From: users-bounces+nitin.kapoor=sensis.com at lists.opencsw.org [mailto:users-bounces+nitin.kapoor=sensis.com at lists.opencsw.org] On Behalf Of Maciej Blizinski Sent: Monday, April 11, 2011 11:37 AM To: Questions and discussions Subject: Re: [csw-users] GCC4 ld Warnings 2011/4/11 Kapoor, Nitin : > Well the issue remains when we build our own software with GCC4. Yes, so these are 2 separate issues: one is multiple inclusions. Ben's advice is most probably the way to go: do not use LD_LIBRARY_PATH, use -L and -R instead. The second issue is what seems to be effort duplication. Are there any reasons not to use OpenCSW xerces and/or protobuf? I'm asking, because if you don't use these packages because there's something that doesn't work for you, we need to fix the packages. Regards, Maciej _______________________________________________ users mailing list users at lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/users - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - From maciej at opencsw.org Tue Apr 12 00:34:42 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Mon, 11 Apr 2011 23:34:42 +0100 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: References: Message-ID: 2011/4/11 Kapoor, Nitin : > (...) -licuuc -licudata -lnsl -lsocket -lpthread -ldl /opt/csw/gcc4/lib/libstdc++.so I believe that the culprit is the explicit "/opt/csw/gcc4/lib/libstdc++.so" parameter given to the linker, you can see it up there in the output. Here's a minimal example to reproduce this behavior: maciej at netra ~/src/gcc-test $ cat Makefile PATH := /opt/csw/bin:/opt/csw/gcc4/bin:$(PATH) LDFLAGS = -R/opt/csw/gcc4/lib -L/opt/csw/gcc4/lib $(EXTRA_LDFLAGS) CC = gcc CXX = g++ all: foo foo: foo.cpp foo.cpp: Makefile echo '#include ' > foo.cpp echo 'main(void) { printf("Hello world!\\n"); }' >> foo.cpp clean: rm -f foo foo.o foo.cpp maciej at netra ~/src/gcc-test $ gmake echo '#include ' > foo.cpp echo 'main(void) { printf("Hello world!\\n"); }' >> foo.cpp g++ -R/opt/csw/gcc4/lib -L/opt/csw/gcc4/lib foo.cpp -o foo maciej at netra ~/src/gcc-test $ gmake clean rm -f foo foo.o foo.cpp maciej at netra ~/src/gcc-test $ gmake EXTRA_LDFLAGS=/opt/csw/gcc4/lib/libstdc++.so echo '#include ' > foo.cpp echo 'main(void) { printf("Hello world!\\n"); }' >> foo.cpp g++ -R/opt/csw/gcc4/lib -L/opt/csw/gcc4/lib /opt/csw/gcc4/lib/libstdc++.so foo.cpp -o foo ld: warning: file /opt/csw/gcc4/lib/libstdc++.so: attempted multiple inclusion of file maciej at netra ~/src/gcc-test $ To fix the warning in your case, you need to analyze the build system of the software you're building, and find out why the explicit reference to libstdc++.so appears in the linker invocation. If you manage to remove it, the warning should disappear. Maciej From maciej at opencsw.org Tue Apr 12 11:45:35 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Tue, 12 Apr 2011 10:45:35 +0100 Subject: [csw-users] Disable sudo logfile In-Reply-To: References: Message-ID: 2011/4/10 Mohamed Lrhazi : > How do I force sudo to not use a logfile, and use syslog only? > > It seems to default to: ?/var/opt/csw/log/sudo/sudolog > > The man page says to negate "logfile", in the sudoers config file, but > cannot figure out how to do that. > the man page also says that by default sudo does not use a file, but > apparently in csw, it does. > > My current workaround is to put this in sudoers: > > > Defaults syslog=auth > Defaults logfile=/dev/null The build description for sudo passes an explicit option to set the logging path. Perhaps it has the side effect that it starts ignoring the configuration file. It sounds like a problem that should be addressed upstream. Reading sudo website, it looks like version 1.8.x has made changes to logging, so perhaps the issue is not present any more in new versions. I've looked into upgrading sudo, but there are some issues with it. I'll keep you posted if I have an update for it. Maciej [1] http://www.gratisoft.us/sudo/ From Nitin.Kapoor at Sensis.com Tue Apr 12 19:32:10 2011 From: Nitin.Kapoor at Sensis.com (Kapoor, Nitin) Date: Tue, 12 Apr 2011 13:32:10 -0400 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: References: Message-ID: Do you know where it would come from ("/opt/csw/gcc4/lib/libstdc++.so") ? The only place where I have to pass the /opt/csw/gcc4/lib is when I configure a package. ( ./configure LDFLAGS=-R/opt/csw/gcc4/lib) -bash-3.00$ env TERM=xterm SHELL=/usr/bin/bash SSH_CLIENT=172.21.9.118 1585 22 SSH_TTY=/dev/pts/1 USER=sbsmlat MAIL=/var/mail//sbsmlat PATH=/usr/ccs/bin:/usr/local/bin:/usr/bin PWD=/export/home/sbsmlat/PKGS TZ=US/Eastern SHLVL=1 HOME=/export/home/sbsmlat LOGNAME=sbsmlat SSH_CONNECTION=172.21.9.118 1585 192.168.40.25 22 _=/usr/bin/env OLDPWD=/export/home/sbsmlat Thanks, Nitin. -----Original Message----- From: users-bounces+nkapoor=sensis.com at lists.opencsw.org [mailto:users-bounces+nkapoor=sensis.com at lists.opencsw.org] On Behalf Of Maciej Blizinski Sent: Monday, April 11, 2011 6:35 PM To: Questions and discussions Subject: Re: [csw-users] GCC4 ld Warnings 2011/4/11 Kapoor, Nitin : > (...) -licuuc -licudata -lnsl -lsocket -lpthread -ldl /opt/csw/gcc4/lib/libstdc++.so I believe that the culprit is the explicit "/opt/csw/gcc4/lib/libstdc++.so" parameter given to the linker, you can see it up there in the output. Here's a minimal example to reproduce this behavior: maciej at netra ~/src/gcc-test $ cat Makefile PATH := /opt/csw/bin:/opt/csw/gcc4/bin:$(PATH) LDFLAGS = -R/opt/csw/gcc4/lib -L/opt/csw/gcc4/lib $(EXTRA_LDFLAGS) CC = gcc CXX = g++ all: foo foo: foo.cpp foo.cpp: Makefile echo '#include ' > foo.cpp echo 'main(void) { printf("Hello world!\\n"); }' >> foo.cpp clean: rm -f foo foo.o foo.cpp maciej at netra ~/src/gcc-test $ gmake echo '#include ' > foo.cpp echo 'main(void) { printf("Hello world!\\n"); }' >> foo.cpp g++ -R/opt/csw/gcc4/lib -L/opt/csw/gcc4/lib foo.cpp -o foo maciej at netra ~/src/gcc-test $ gmake clean rm -f foo foo.o foo.cpp maciej at netra ~/src/gcc-test $ gmake EXTRA_LDFLAGS=/opt/csw/gcc4/lib/libstdc++.so echo '#include ' > foo.cpp echo 'main(void) { printf("Hello world!\\n"); }' >> foo.cpp g++ -R/opt/csw/gcc4/lib -L/opt/csw/gcc4/lib /opt/csw/gcc4/lib/libstdc++.so foo.cpp -o foo ld: warning: file /opt/csw/gcc4/lib/libstdc++.so: attempted multiple inclusion of file maciej at netra ~/src/gcc-test $ To fix the warning in your case, you need to analyze the build system of the software you're building, and find out why the explicit reference to libstdc++.so appears in the linker invocation. If you manage to remove it, the warning should disappear. Maciej _______________________________________________ users mailing list users at lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/users - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - From maciej at opencsw.org Tue Apr 12 21:19:47 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Tue, 12 Apr 2011 20:19:47 +0100 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: References: Message-ID: 2011/4/12 Kapoor, Nitin : > Do you know where it would come from ("/opt/csw/gcc4/lib/libstdc++.so") ? The only place where I have to pass the /opt/csw/gcc4/lib is when I configure a package. Two ideas about the libstdc++.so reference: - it's volunteered by the build system - it comes from a *-config command of one of the dependencies The *-config commands can return ldflags which are later used in the build process. For example: $ libpng-config --ldflags -L/opt/csw/lib -lpng12 Try looking at the config.log file of your build, maybe it'll contain some hints. If not, look at all the dependencies, locate their *-config scripts and see if they return libstdc++.so if you call them with e.g. --libs or --ldflags. Maciej From Nitin.Kapoor at Sensis.com Wed Apr 13 16:48:58 2011 From: Nitin.Kapoor at Sensis.com (Kapoor, Nitin) Date: Wed, 13 Apr 2011 10:48:58 -0400 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: References: Message-ID: Hi, Following is the part of libtool script:- # The directories searched by this compiler when creating a shared library. compiler_lib_search_dirs="/usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6 /usr/ccs/bin /usr/ccs/lib /usr/ local/lib/gcc/sparc-sun-solaris2.10/3.4.6/../../.." # Dependencies to place before and after the objects being linked to # create a shared library. predep_objects="/usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6/crti.o /usr/ccs/lib/values-Xa.o /usr/loca l/lib/gcc/sparc-sun-solaris2.10/3.4.6/crtbegin.o" postdep_objects="/usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6/crtend.o /usr/local/lib/gcc/sparc-sun-so laris2.10/3.4.6/crtn.o" predeps="" postdeps="-lstdc++ -lm -lgcc_s -lgcc_s" # The library search path used internally by the compiler when linking # a shared library. compiler_lib_search_path="-L/usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6 -L/usr/ccs/bin -L/usr/ccs/lib -L/usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6/../../.." This libtool script gets created when I configure a package prior to compile. In the script ( pasted above) there is a postdeps flags that seems to cause problems. Any ideas on how to disable this ? Thanks!!! -----Original Message----- From: users-bounces+nkapoor=sensis.com at lists.opencsw.org [mailto:users-bounces+nkapoor=sensis.com at lists.opencsw.org] On Behalf Of Maciej Blizinski Sent: Tuesday, April 12, 2011 3:20 PM To: Questions and discussions Subject: Re: [csw-users] GCC4 ld Warnings 2011/4/12 Kapoor, Nitin : > Do you know where it would come from ("/opt/csw/gcc4/lib/libstdc++.so") ? The only place where I have to pass the /opt/csw/gcc4/lib is when I configure a package. Two ideas about the libstdc++.so reference: - it's volunteered by the build system - it comes from a *-config command of one of the dependencies The *-config commands can return ldflags which are later used in the build process. For example: $ libpng-config --ldflags -L/opt/csw/lib -lpng12 Try looking at the config.log file of your build, maybe it'll contain some hints. If not, look at all the dependencies, locate their *-config scripts and see if they return libstdc++.so if you call them with e.g. --libs or --ldflags. Maciej _______________________________________________ users mailing list users at lists.opencsw.org https://lists.opencsw.org/mailman/listinfo/users - This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. - -------------- next part -------------- An HTML attachment was scrubbed... URL: From maciej at opencsw.org Sun Apr 17 12:23:47 2011 From: maciej at opencsw.org (=?UTF-8?Q?Maciej_Blizi=C5=84ski?=) Date: Sun, 17 Apr 2011 11:23:47 +0100 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: References: Message-ID: 2011/4/13 Kapoor, Nitin : > postdeps="-lstdc++ -lm -lgcc_s -lgcc_s" > > # The library search path used internally by the compiler when linking > > # a shared library. > > compiler_lib_search_path="-L/usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6 > -L/usr/ccs/bin -L/usr/ccs/lib > > ?-L/usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6/../../.." > > This libtool script gets created when I configure a package prior to > compile. > > In the script ( pasted above) there is a postdeps flags that seems to cause > problems. Any ideas on how to disable this ? This looks like a libtool-specific issue, can someone more knowledgeable in libtool chime in? From dam at opencsw.org Sun Apr 17 14:03:07 2011 From: dam at opencsw.org (Dagobert Michelsen) Date: Sun, 17 Apr 2011 14:03:07 +0200 Subject: [csw-users] GCC4 ld Warnings In-Reply-To: References: Message-ID: <8DDFF37E-D374-4E1A-87F4-1FE27F8EDD71@opencsw.org> Hi, Am 17.04.2011 um 12:23 schrieb Maciej Blizi?ski: > 2011/4/13 Kapoor, Nitin : >> postdeps="-lstdc++ -lm -lgcc_s -lgcc_s" >> >> # The library search path used internally by the compiler when linking >> >> # a shared library. >> >> compiler_lib_search_path="-L/usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6 >> -L/usr/ccs/bin -L/usr/ccs/lib >> >> -L/usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6/../../.." >> >> This libtool script gets created when I configure a package prior to >> compile. >> >> In the script ( pasted above) there is a postdeps flags that seems to cause >> problems. Any ideas on how to disable this ? > > This looks like a libtool-specific issue, can someone more > knowledgeable in libtool chime in? From my understanding the workflow is like this: - compilation of libtool package with a specific compiler. This sets several configuration variables in the installed libtool - A program foo uses libtool by "libtoolizing" which grabs scripts and configuration files from the installed libtool. - When foo is compiled the libtool from the libtoolized version by upstream is used. When the upstream configuration of the compiler is too different from the configuration in the users configuration trying to compile foo problems like this occurs. In the OpenCSW packages it is sometimes necessary to rebootstrap the libtool configuration. You can peek at some of the methods at http://sourceforge.net/apps/trac/gar/browser/csw/mgar/pkg/gobject-introspection/trunk/Makefile http://sourceforge.net/apps/trac/gar/browser/csw/mgar/pkg/gettext/trunk/files/0002-Update-ltmain.sh-to-prevent-libtool-stripping-runpat.patch Best regards -- Dago From leslie.wood at oracle.com Fri Apr 29 00:06:52 2011 From: leslie.wood at oracle.com (Leslie H Wood) Date: Thu, 28 Apr 2011 15:06:52 -0700 Subject: [csw-users] CSWsvn installs but svn does not work Message-ID: <4DB9E4FC.5080301@oracle.com> An HTML attachment was scrubbed... URL: From bonivart at opencsw.org Fri Apr 29 00:15:32 2011 From: bonivart at opencsw.org (Peter Bonivart) Date: Fri, 29 Apr 2011 00:15:32 +0200 Subject: [csw-users] CSWsvn installs but svn does not work In-Reply-To: <4DB9E4FC.5080301@oracle.com> References: <4DB9E4FC.5080301@oracle.com> Message-ID: On Fri, Apr 29, 2011 at 12:06 AM, Leslie H Wood wrote: > > Issue seen on both Solaris 10 Update 9 for Sparc and x86. > > The following "/opt/csw/bin/pkg-get install CSWsvn" worked a week ago but now I get the following on a new installs.?? Are the dependencies for CSWsvn now broken? Yes, there was a bad neon release, it has just gone out fixed but if you can't wait for the mirrors to update you can get it here directly: http://buildfarm.opencsw.org/experimental.html#libneon /peter