I've done it, but not on a SLES7 system. It was a SuSE 7.0 system. I started downloading SRPM files from the SuSE 8.1 distribution and compiling them. (talk about a _lot_ of compiles!) I just tested it, and I was able to print a file using the lpr command.
autoconf-2.53-148 automake-1.6.3-36 binutils-2.12.90.0.15-49 bison-1.33-50 cpp-3.2-44 flex-2.5.4-284 gcc-3.2-44 gcc-c++-3.2-44 glibc-2.2.5-161 glibc-info-2.2.5-161 glibc-html-2.2.5-161 glibc-devel-2.2.5-161 glibc-locale-2.2.5-161 libgcc-3.2-44 libstdc++-3.2-44 libstdc++-devel-3.2-44 libtool-1.4.2-345 lprng-3.7.4-1 perl-5.6.1-175 strace-4.4-223 timezone-2.2.5-161 yacc-91.7.30-270 Mark Post -----Original Message----- From: Steven A. Adams [mailto:[EMAIL PROTECTED] Sent: Monday, March 17, 2003 6:05 PM To: [EMAIL PROTECTED] Subject: Re: LPRng Seg Faulting On Mon, 2003-03-17 at 14:46, Post, Mark K wrote: > Your questions are a little confusing. The title talks about segmentation > faults, but you ask about successful compiles. > Sorry Mark, to clarify: 1. The linux guest has been updated with gcc3.2 and glibc2.5. 2. Many products have been compiled and function without issue on this SLES7 guest (after the gcc/glibc update). 3. LPRng compiled without error and the CFLAGS=-O1 was used on the make command line. I am aware that optimization level 2 is an issue for some software on the linux/390 platform. 4. When any of the LPR tools or LPD are attempted, the command ends abnormally with a segmentation fault in libc6. Now for the question; Is there anyone here that has successfully completed a source installation of LPRng under gcc 3.2 on a linux guest? My reason for asking? I'm trying to pinpoint where my problem might be (e.g. gcc, glib, libtools, LPRng, PEBCAK). Oh yeah, I've read several f'ing manuals and either don't see the problem addresses or have missed it. Hope that ends the confusion. Steve
