Discuss

discuss@lists.centos.org

34753 discussions

Re: [CentOS] libtiff build error
by Robert Moskowitz 02 Jun '06

02 Jun '06

At 04:24 PM 6/1/2006, Jim Perrin wrote: >>But there is no rpm for libtiff v 3.8.2 for Centos. Every indication >>is that I need this. Well we will see what is supplied in the new >>Trixbox (Asterisk@home's new name). > >Very true, but you can always build your own. In any even, I won't >preach about this one too much. Thanks for your pointers. Almost time to quit for holiday (Shavous), so this will be resumed monday. I think I see how to proceed. I have two A@H systems, replace one wiht Trixbox and see what if haves, if not shotgun everything I need onto other box, move the files over and make install.... And figure out the necessary symbolic links. Gee I have not done any of that since working on Suns 12+ years ago..... >> >> But the make had the following error: >> >> >> >> ./libtool: line 837: g++: command not found >> > >> >This one line has your winner. You lack the proper build tools to >> >complete your desired task. You're missing the gcc-c++, and probably >> >several other things you'll need. >> >>?? yum groupinstall gcc-c++ > >There's no group by that name. If you're going to do the shotgun >approach like that then >yum groupinstall "Development Tools" is probably what you want > >> >> >> make[2]: Leaving directory `/root/tiff-3.8.2/libtiff' > >>So I log in as user foo. I do all the makes as foo. But everything >>in /usr/var is owned by root... ?? > >configure and make are run as your user. Make install (which should >really just be moving files to their final location) is the only thing >you need to run as root or with sudo. > > >>I have looked for some reasonable howtos but so far have come up short. > >I don't really have any to offer. Maybe someone else on the list will. > >> >>1104 -r--r--r-- 1 root root 1126338 May 9 07:38 libtiff.a >> 0 lrwxrwxrwx 1 root root 14 May 24 11:07 libtiff.so -> >>libtiff.so.3.6 >> 0 lrwxrwxrwx 1 root root 14 May 24 11:07 libtiff.so.3 -> >>libtiff.so.3.6 >> 308 -rwxr-xr-x 1 root root 311088 May 9 07:38 libtiff.so.3.6 > >This may not be as obvious as you think. The way you're doing things >right now would install libtiff in /usr/local/ so you'd end up with >both versions. and your asterisk application would have to be >specifically told which one to use, as it'll probably link against the >files in /usr before the files in /usr/local > > >-- >This message has been double ROT13 encoded for security. Anyone other >than the intended recipient attempting to decode this message will be >in violation of the DMCA >_______________________________________________ >CentOS mailing list >CentOS(a)centos.org >http://lists.centos.org/mailman/listinfo/centos

1 0

Re: [CentOS] libtiff build error
by Robert Moskowitz 02 Jun '06

02 Jun '06

It would be nice if the world were flat... At 02:48 PM 6/1/2006, Jim Perrin wrote: >> ./configure >> make clean >> make > >Not going to get into how much of a bad idea this is, or how it should >really be in an rpm. But there is no rpm for libtiff v 3.8.2 for Centos. Every indication is that I need this. Well we will see what is supplied in the new Trixbox (Asterisk@home's new name). >> But the make had the following error: >> >> ./libtool: line 837: g++: command not found > >This one line has your winner. You lack the proper build tools to >complete your desired task. You're missing the gcc-c++, and probably >several other things you'll need. ?? yum groupinstall gcc-c++ >> make[2]: Leaving directory `/root/tiff-3.8.2/libtiff' > >This line would seem to imply that you're building software as root. >This is generally a very bad idea. If the code's cleanup scripts are >wrong, or if there's a typo... it's running as root and could very >easily rm -rf your system, instead or rm -rf the buildroot or tmp >files its using, not to mention other nefarious code tricks that make >this a bad idea. So I log in as user foo. I do all the makes as foo. But everything in /usr/var is owned by root... ?? >> and make install did not work: > >that's because you had prior errors. Just making sure. Obvious answer, but I have been seeing some non-obvious stuff lately. >> So what is missing? And where do I start from. > >You should really consider reading up on compiling software and/or >building custom rpms. I have looked for some reasonable howtos but so far have come up short. >> It looks like things are not 'broken' from how far it got. > >They're not broken because they haven't gotten that far yet. You're >missing the compiler required to make/break them. Again, obvious from: 1104 -r--r--r-- 1 root root 1126338 May 9 07:38 libtiff.a 0 lrwxrwxrwx 1 root root 14 May 24 11:07 libtiff.so -> libtiff.so.3.6 0 lrwxrwxrwx 1 root root 14 May 24 11:07 libtiff.so.3 -> libtiff.so.3.6 308 -rwxr-xr-x 1 root root 311088 May 9 07:38 libtiff.so.3.6 thanks. >-- >This message has been double ROT13 encoded for security. Anyone other >than the intended recipient attempting to decode this message will be >in violation of the DMCA Illegitimi non Carborundum

2 1

RE: [CentOS] Assistance with startup script
by Bowie Bailey 02 Jun '06

02 Jun '06

Will McDonald wrote: > > If you added something like... > > # chkconfig: 345 20 80 > # description: Does LDM stuff > > ... after your shabang #!/bin/sh line that should suffice. That would > start your LDM script after networking in runlevels 345 and stop it > before networking's stopped when hopping back down through the > runleves. > > I can't recall if you need a "chkconfig --add ldm" but if your > script's not visible in "chkconfig --list" then try it. The chkconfig > man page's RUNLEVEL FILES section should have all the info you need. Yes, you do need the "chkconfig --add ldm". This is what creates the links in the runlevel directories. > If you wanted to go the whole hog you could also look at integrating > your startup stuff into /var/lock/subsys etc. Just have a look through > an existing init script. If you want init to shutdown the service for you, you need a lock file in /var/lock/subsys with the same name as your main script. Just have the start routine touch it and the stop routine remove it. -- Bowie

4 5

Assistance with startup script
by Sam Drinkard 02 Jun '06

02 Jun '06

Could someone give me some assistance in getting this startup script to conform to chkconfig and such where the service will start up after networking comes up, and then shut down when networking goes away? Where all do entries need to be made, and what would they consist of? Many thanks..... Sam ------------------------------------------------------------------------ #! /bin/sh export PATH=/bin:/usr/bin LDMHOME=/usr/local/ldm LDMBIN=$LDMHOME/bin LDMADMIN=$LDMBIN/ldmadmin PQCHECK=$LDMBIN/pqcheck PQCAT=$LDMBIN/pqcat PQ=$LDMHOME/data/ldm.pq LOG="logger -p local0.err $0:" case "$1" in start) $LOG 'Starting LDM system...' if [ -x $LDMADMIN ] ; then if su - ldm -c "$LDMADMIN isrunning"; then $LOG "LDM system is already running." else if [ ! -f $PQ ] ; then $LOG "Product-queue doesn't exist. Creating..." if ! su - ldm -c "$LDMADMIN mkqueue"; then $LOG "Aborting..." exit 1 fi else # # Test the product-queue for corruption. # if ! $PQCHECK -l /dev/null -q $PQ; then case $? in 1) $LOG "System error checking product-queue. Aborting..." exit 1 ;; 2) $LOG "Adding writer-counter to product-queue..." if ! $PQCHECK -F -q $PQ; then $LOG "Aborting..." exit 1 fi ;; 3) $LOG "Product-queue was incorrectly closed. " \ "Checking..." if $PQCAT -s -l /dev/null; then $LOG "Product-queue appears OK. " $LOG "Clearing writer-counter..." if ! $PQCHECK -F -q $PQ; then $LOG "Couldn't clear counter. Aborting..." exit 1 fi else $LOG "Product-queue appears corrupt. Deleting." rm $PQ if ! su - ldm -c "$LDMADMIN mkqueue -f"; then $LOG "Couldn't make new product-queue. Aborting..." exit 1 fi fi ;; 4) $LOG "Product-queue is corrupt. Deleting." rm $PQ if ! su - ldm -c "$LDMADMIN mkqueue -f"; then $LOG "Couldn't make new product-queue. Aborting..." exit 1 fi ;; esac fi fi su - ldm -c "$LDMADMIN clean" su - ldm -c "$LDMADMIN start" fi fi ;; stop) $LOG 'Stopping the LDM system.' if [ -x $LDMADMIN ] ; then su - ldm -c "$LDMADMIN stop" fi ;; esac -- Sam W.Drinkard -- sam(a)wa4phy.net WEB http://wa4phy.net Augusta Mesonet cell 706.825.8513 Home 706.868.7253 MAIL 4438 Branchwood Drive, Martinez Georgia, 30907-1304

4 4

libtiff build error
by Robert Moskowitz 02 Jun '06

02 Jun '06

OK. Trying to build libtiff here. Info from http://www.asteriskguru.com/tutorials/spandsp.html Libtiff from tar: ftp://ftp.remotesensing.org/pub/libtiff 3.8.2 put tiff-3.8.2.tar.gz in /root then tar -zxvf tiff-3.8.2.tar.gz followed by: /configure make clean make But the make had the following error: ./libtool: line 837: g++: command not found make[2]: *** [tif_stream.lo] Error 1 make[2]: Leaving directory `/root/tiff-3.8.2/libtiff' make[1]: *** [all] Error 2 make[1]: Leaving directory `/root/tiff-3.8.2/libtiff' make: *** [all-recursive] Error 1 and make install did not work: Making install in port make[1]: Entering directory `/root/tiff-3.8.2/port' make[2]: Entering directory `/root/tiff-3.8.2/port' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/root/tiff-3.8.2/port' make[1]: Leaving directory `/root/tiff-3.8.2/port' Making install in libtiff make[1]: Entering directory `/root/tiff-3.8.2/libtiff' source='tif_stream.cxx' object='tif_stream.lo' libtool=yes \ DEPDIR=.deps depmode=none /bin/sh ../config/depcomp \ /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I. -I. -c -o tif_stream.lo tif_stream.cxx libtool: compile: g++ -DHAVE_CONFIG_H -I. -I. -I. -I. -c tif_stream.cxx -o .libs/tif_stream.o ./libtool: line 837: g++: command not found make[1]: *** [tif_stream.lo] Error 1 make[1]: Leaving directory `/root/tiff-3.8.2/libtiff' make: *** [install-recursive] Error 1 So what is missing? And where do I start from. It looks like things are not 'broken' from how far it got.

2 1

latest kernel-devel,kernel-smp-devel install vs. update
by Tony Schreiner 01 Jun '06

01 Jun '06

WIth the latest kernel 2.6.9-34.0.1 the kernel-devel is an install, but kernel-smp-devel is an update for example $ sudo yum update kernel\* --disablerepo=dell-software -- disablerepo=jpackage-generic Setting up Update Process Setting up repositories Reading repository metadata in from local files Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package kernel-smp-devel.i686 0:2.6.9-34.0.1.EL set to be updated ---> Package kernel-devel.i686 0:2.6.9-34.0.1.EL set to be installed ---> Package kernel.i686 0:2.6.9-34.0.1.EL set to be installed ---> Package kernel-smp.i686 0:2.6.9-34.0.1.EL set to be installed --> Running transaction check Dependencies Resolved ======================================================================== ===== Package Arch Version Repository Size ======================================================================== ===== Installing: kernel i686 2.6.9-34.0.1.EL update 10 M kernel-devel i686 2.6.9-34.0.1.EL update 3.7 M kernel-smp i686 2.6.9-34.0.1.EL update 9.9 M Updating: kernel-smp-devel i686 2.6.9-34.0.1.EL update 3.7 M Transaction Summary ======================================================================== ===== Install 3 Package(s) Update 1 Package(s) Remove 0 Package(s) Total download size: 28 M Is this ok [y/N]: n I would like for both devel packages to be installed rather than updated. Looking back in the archives, this happened before. It was suggested to use installonlypackages=kernel-smp-devel I have put this line in my CentOS-Base.repo file, in the updates section, but it doesn't seem to have any effect. Is that the right place? Thanks, Tony Schreiner Boston College

3 4

RE: [CentOS] Assistance with startup script
by Alex Palenschat 01 Jun '06

01 Jun '06

> Could someone give me some assistance in getting this startup > script to > conform to chkconfig and such where the service will start up after > networking comes up, and then shut down when networking goes away? > Where all do entries need to be made, and what would they consist of? > > Many thanks..... > > Sam > -------------------------------------------------------------- > ---------- > man chkconfig Seriously, it has most of the info you need. If I recall a similar circumstance all I needed to do was to drop the script in /etc/init.d/ and do a chkconfig --add <name of script> and then it was ready to rock. alex

1 0

CentOS 4.3 Server spontaneously rebooting (over and over again)
by Rob van Eerd 01 Jun '06

01 Jun '06

Hi there, This post has also been posted in the Hardware and General forums but I thought it might be wise to post it here as well! My CentOS 4.3 (upgraded from CentOS 4.2 installed from Linux Magazine's April 2006 issue) server is rebooting spontaneously (over and over again). It started while I was copying from USB-device (iPod) to another USB-device (Freecom Portable-Hard-disk) but it happens now even when both devices aren't plugged in. I noticed it reboots most of the time during the boot process around the messages: "Starting udev:" and "Initializing hardware". I tried rebooting into single user mode without any luck and even starting with the Installation DVD (from Linux Magazine's April 2006 issue) gives me the same results. In doing so I noticed that it took a might long time to load my SCSI drivers and after removing both SCSI adapters (just connected for oldish CD- and tape-drives) it got a little better for just a few hours. Now my system is back to his anoying reboot habbit during the boot-process I've juggled around with the memory because sometimes the reboot occurred during initialization of the RAM disks. I was also starting to think that it may have to do something with networking activity because when it (only now and then) comes up properly, I can login (straight from the console) but as soon as I try to send something across the network (for instance my /var/log/message* files) the server reboots again. However removing the NIC (including the configuration) didn't solve my problem I've attached my lateste message file for reference. I've managed to get that off the system using a simple USB-stick. When trying to get it off using SCP or something alike, my server rebooted. Can anyone point me into the right direction to tame this beast? Thanks for any help! Regards, Rob van Eerd Rosmalen, Netherlands

3 2

CentOS 3.5 system hanging
by Mark Belanger 01 Jun '06

01 Jun '06

Our very large and very complex application is running on CentOS 3.5 and Solaris. The CentOS machines are hanging about once per day. By "hanging" I mean the system is completely unresponsive either from the console or remotely via ssh. Totally locked. Does anyone have any tips for troubleshooting this sort of problem? -Mark -- Mark Belanger LTX Corporation

2 1

OT - yum missing from a RHEL4 server???
by kevin＠kevinkempterllc.com 01 Jun '06

01 Jun '06

Hi List; Sorry for the OT post. However I suspect if anyone outside of RH can help with this question it would be this list. I'm starting a new contract with a shop that knows little about Linux and I'm helping pave the way. I've "inherited" an existing Linux install (RHEL4). I want to setup some tools but I find that yum is not installed. Is this normal for a RH box ? I thought that the RH up2date tool used yum under the covers. Anyhow, is there an easy way to get yum installed on this box ? I do have VNC access - and I can run KDE in the VNC connection even though according to the add/remove software tool KDE is not installed by changing the xstartup file forthat user under ~/.vnc (wierd!!) I suspect the answer is to find & download a yum rpm for redhat and install it via rpm but I want to be sure I dont do something stupid on a client system. Thanks in advance...

5 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss