Re: CURRENT: arptools and libpcap
On Tue, May 08, 2007, Scott Cruzen wrote: > * Ralf S. Engelschall <[EMAIL PROTECTED]> [070507 23:20]: > > On Mon, May 07, 2007, Scott Cruzen wrote: > > > > > "openpkg build arptools | sh" fails on Solaris 10/amd64 (32 bit) > > > adding LIBS="-lnsl -lsocket" to the configure line seems to fix it. > > > > Thanks for the hint. Now fixed. > > > > Thanks for fixing this, but it looks like it needs -lresolv too. > > Also, I noticed that it ends up with > LIBS=' -lnsl -lsocket -lpcap -lsocket -lnsl -lnet' > > I'm not sure why some libraries are listed twice, but it's obviously not > a serious problem. The doubling of the libs results from the fact that arptools' "configure" script already determines that it needs "-lnsl -lsocket" under Solaris but unfortunately places them into LIBS in the wrong order (they would have to check for -lpcap before). The -lresolv I've now added, too. The package now finally builds just fine for me under Solaris. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: OpenSSH Crashes on AMD64
Ralf S. Engelschall wrote: On Wed, May 02, 2007, Doug Summers wrote: Ralf S. Engelschall wrote: On Tue, Apr 24, 2007, Ralf S. Engelschall wrote: On Mon, Apr 23, 2007, Doug Summers wrote: Tried the latest 4.6p1 version, both STABLE & CURRENT. Right after the motd flashes by the connection closes with this error: *** glibc detected *** free(): invalid next size (fast): 0x0069d090 *** The 4.5p1 version (and below) never did this. Any ideas??? Under which AMD64-based operating system is this under? Sorry, I was not pricise enough: I see from the "glibc" above that it is Linux, of course. But what particular Linux distribution is this? I built a backdated version (1/14/2007) that works but nothing newer does. Any idea(s) why? I originally thought it was a release problem (4.5 --> 4.6) but I couldn't get the 3/20/2007 version to work either. Well, between the 20070114 release of the "openssh" package and today there is _ONLY_ the 4.5 to 4.6 vendor version change _EXCEPT_ you are using the optional LDAP or HPN patches. So, if 20070114 still works also e.g. 20070221 has to still work as it includes just a newer HPN patchset. Are you really sure that 20070114 is the latest version which works correctly. Or do you have HPN enabled? Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com I'm not using LDAP or HPN. The only options I ever use are PAM & X11. __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: CURRENT: arptools and libpcap
* Ralf S. Engelschall <[EMAIL PROTECTED]> [070507 23:20]: > On Mon, May 07, 2007, Scott Cruzen wrote: > > > "openpkg build arptools | sh" fails on Solaris 10/amd64 (32 bit) > > adding LIBS="-lnsl -lsocket" to the configure line seems to fix it. > > Thanks for the hint. Now fixed. > Thanks for fixing this, but it looks like it needs -lresolv too. Also, I noticed that it ends up with LIBS=' -lnsl -lsocket -lpcap -lsocket -lnsl -lnet' I'm not sure why some libraries are listed twice, but it's obviously not a serious problem. Thanks again, Scott __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: Man Pages
I don't mean for all packages. I just mean the openpkg specific packages. The software/tools that have been developed in-house for use in the openpkg world. That should only be 4 or 5 man pages total. It would be a nice addition to list under the "Documentation" area. On Tue, 2007-05-08 at 19:51 +0200, Ralf S. Engelschall wrote: > On Tue, May 08, 2007, David M. Fetter wrote: > > > Are the man pages for the specific openpkg software online somewhere on > > the web site? It would be nice if they were. When we build our > > software currently the man pages all fail to properly build for some > > reason. It's a low priority for us to resolve but it would be nice if > > the man pages for openpkg, openpkg-tools and the other packages that are > > specific to openpkg were online. I can't seem to find them on the site > > if they are. > > We currently don't have the manpages online. > > In case someone wants to investigate on this: In order to display all > manpages of all packages, we would either need an OpenPKG instance with > all packages installed (which is not possible anyway) or at least have > all packages staying around in unpacked format (which we currently do > not have, too). Additionally one needs a man to html formatter and a > small wrapper CGI. I think there is rman which we use at FreeBSD.org... > >Ralf S. Engelschall >[EMAIL PROTECTED] >www.engelschall.com > > __ > OpenPKG http://openpkg.org > User Communication List openpkg-users@openpkg.org > -- David M. Fetter - UNIX Systems Administrator Portland State University - www.oit.pdx.edu signature.asc Description: This is a digitally signed message part
Re: Man Pages
On Tue, May 08, 2007, David M. Fetter wrote: > Are the man pages for the specific openpkg software online somewhere on > the web site? It would be nice if they were. When we build our > software currently the man pages all fail to properly build for some > reason. It's a low priority for us to resolve but it would be nice if > the man pages for openpkg, openpkg-tools and the other packages that are > specific to openpkg were online. I can't seem to find them on the site > if they are. We currently don't have the manpages online. In case someone wants to investigate on this: In order to display all manpages of all packages, we would either need an OpenPKG instance with all packages installed (which is not possible anyway) or at least have all packages staying around in unpacked format (which we currently do not have, too). Additionally one needs a man to html formatter and a small wrapper CGI. I think there is rman which we use at FreeBSD.org... Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Man Pages
Are the man pages for the specific openpkg software online somewhere on the web site? It would be nice if they were. When we build our software currently the man pages all fail to properly build for some reason. It's a low priority for us to resolve but it would be nice if the man pages for openpkg, openpkg-tools and the other packages that are specific to openpkg were online. I can't seem to find them on the site if they are. -- David M. Fetter - UNIX Systems Administrator Portland State University - www.oit.pdx.edu signature.asc Description: This is a digitally signed message part
Re: CURRENT: building 64bit openpkg on Solaris/amd64
On Tue, May 01, 2007, Scott Cruzen wrote: > I'd like to build a 64bit OpenPKG instance on Solaris 11/06. > > I tried building OpenPKG from scratch, which succeeded for 32bit, and > found that the OpenPKG gcc package does not include 64bit libgcc. > > I also tried to follow the instructions from the email here [1] in order > to build an entirely 64bit OpenPKG instance, but it seems that things > have changed enough to prevent this from working. > > from the hello.sh script: > /openpkg/bin/gcc -o hello hello.c > hello: ELF 32-bit LSB executable 80386 Version 1 > /openpkg/bin/gcc -m32 -o hello hello.c > hello: ELF 32-bit LSB executable 80386 Version 1 > /openpkg/bin/gcc -m64 -o hello hello.c > /openpkg/bin/ld: skipping incompatible > /openpkg/lib/gcc/i386-pc-solaris2.10/4.1.2/./libgcc.a when searching for > -lgcc > /openpkg/bin/ld: cannot find -lgcc > collect2: ld returned 1 exit status > hello: cannot open: No such file or directory Seems like the latest GCC doesn't automatically build a 32 and 64 bit library by default. I'll investigate and try to find out what the reason is for this... Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: PERL-UTIL Build Stuck on RHEL4-AMD64 - UPDATE
On Wed, May 02, 2007, Doug Summers wrote: > Jeff Johnson wrote: > > On Apr 29, 2007, at 7:12 PM, Doug Summers wrote: > >> Doug Summers wrote: > >>> For some reason it's failing when selecting a location: > >>> (1) Africa > >>> (2) Asia > >>> (3) Central America > >>> (4) Europe > >>> (5) North America > >>> (6) Oceania > >>> (7) South America > >>> Select your continent (or several nearby continents) [] > >>> Sorry! since you don't have any existing picks, you must make a > >>> geographic selection. > >>> (1) Africa > >>> (2) Asia > >>> (3) Central America > >>> (4) Europe > >>> (5) North America > >>> (6) Oceania > >>> (7) South America > >>> Select your continent (or several nearby continents) [] ++ step 3: build > >>> [EMAIL PROTECTED] /]$ perl-openpkg:ERROR: neither "Build" nor "Makefile" > >>> found in working directory (No such file or directory) > >>> This happens endlessly until I hit Ctrl-C. Any ideas? perl-openpkg built > >>> just fine as far as I can tell. > >> > >> This is also happening on RHEL4-I386. > > This is also happening in MacPorts-1.4 builds. > > The script is naively expecting a monkey at a keyboard. > > Connecting up < /dev/null to the script may solve, otherwise the > > script that is expecting non-existent input will need patching. > > 73 de Jeff > I built a source RPM from CVS backdated to 2/2/2007 which works. > Ralph - any idea what changed? Sorry, already too many changes between 20070202 and today. But at least the above output does NOT occur anywhere in the sources of any Perl module which is contained in the OpenPKG "perl-util" package! Instead, these messages come from CPAN::FirstTime which is contained in the "perl" module itself. The reason why it occurs is usually because a module didn't find a dependency module and hence spawned the CPAN module to automatically install it. The first time this happens the above messages pop up. So, can you find out by looking back in the output of your "perl-util" build which module is expected and not found? Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: OpenSSH Crashes on AMD64
On Wed, May 02, 2007, Doug Summers wrote: > Ralf S. Engelschall wrote: > > On Tue, Apr 24, 2007, Ralf S. Engelschall wrote: > >> On Mon, Apr 23, 2007, Doug Summers wrote: > >> > >>> Tried the latest 4.6p1 version, both STABLE & CURRENT. Right after the > >>> motd > >>> flashes by the connection closes with this error: > >>> > >>> *** glibc detected *** free(): invalid next size (fast): > >>> 0x0069d090 > >>> *** > >>> > >>> The 4.5p1 version (and below) never did this. Any ideas??? > >> Under which AMD64-based operating system is this under? > > Sorry, I was not pricise enough: I see from the "glibc" above that it is > > Linux, of course. But what particular Linux distribution is this? > I built a backdated version (1/14/2007) that works but nothing newer does. > Any idea(s) why? I originally thought it was a release problem (4.5 --> 4.6) > but I couldn't get the 3/20/2007 version to work either. Well, between the 20070114 release of the "openssh" package and today there is _ONLY_ the 4.5 to 4.6 vendor version change _EXCEPT_ you are using the optional LDAP or HPN patches. So, if 20070114 still works also e.g. 20070221 has to still work as it includes just a newer HPN patchset. Are you really sure that 20070114 is the latest version which works correctly. Or do you have HPN enabled? Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
