Perl won't compile
I've got a 4.7-STABLE system, and perl or the port won't compile... Does anyone have any clue what the problem might be? Haven't had any other issues compiling... other than Base 64 for perl. If I try to install the Base 64 module for the currently installed perl(5.6.0) it bombs with the same error : Making MIME::Base64 (dynamic) cc -c-DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.2/BSDPAN -DHAS_FPSETMASK -DHAS _FLOATINGPOINT_H -fno-strict-aliasing -I/usr/local/include -O -pipe-DVERSION =\2.21\ -DXS_VERSION=\2.21\ -DPIC -fPIC -I../../.. Base64.c Base64.xs: In function `XS_MIME__Base64_decode_base64': Base64.xs:219: `dowarn' undeclared (first use in this function) Base64.xs:219: (Each undeclared identifier is reported only once Base64.xs:219: for each function it appears in.) *** Error code 1 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Perl won't compile
* Shawn Ramsey [EMAIL PROTECTED] [2004-03-18 07:31]: I've got a 4.7-STABLE system, and perl or the port won't compile... Does anyone have any clue what the problem might be? Haven't had any other issues compiling... other than Base 64 for perl. If I try to install the Base 64 module for the currently installed perl(5.6.0) it bombs with the same error : This may not be the answer you are looking for, but you might try upgrading your system to 4.9 or 4-STABLE and having another go at it. Yeah, that isn't the answer I was looking for... :) I have other old release machines and Perl compiles just fine on them. Another 4.7-RELEASE system is running the latest perl... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
compile problems
I am having trouble compiling perl (as well as others, such as GD). Here is th error message : Making List::Util (dynamic) Making MIME::Base64 (dynamic) cc -c-DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.2/BSDPAN -DHAS_FPSETMASK -DHAS _FLOATINGPOINT_H -fno-strict-aliasing -I/usr/local/include -O -pipe-DVERSION =\2.21\ -DXS_VERSION=\2.21\ -DPIC -fPIC -I../../.. Base64.c Base64.xs: In function `XS_MIME__Base64_decode_base64': Base64.xs:219: `dowarn' undeclared (first use in this function) Base64.xs:219: (Each undeclared identifier is reported only once Base64.xs:219: for each function it appears in.) *** Error code 1 Stop in /usr/ports/lang/perl5.8/work/perl-5.8.2/ext/MIME/Base64. *** Error code 1 Stop in /usr/ports/lang/perl5.8/work/perl-5.8.2. *** Error code 1 Stop in /usr/ports/lang/perl5.8. This is on a 4.7-STABLE system from 2002... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Hosed system
/usr/libexec/ld-elf.so.1: /usr/lib/libcrypt.so.2: Shared object has no run-time symbol table I was messing around with libdes trying to get Diablo to compile... and am now getting this error :( Pretty much hosed the system. Any idea how I can fix this? HELP. :) Reinstalling the crypto package made no difference running 4.8-RELEASE ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hosed system
/usr/libexec/ld-elf.so.1: /usr/lib/libcrypt.so.2: Shared object has no run-time symbol table I was messing around with libdes trying to get Diablo to compile... and am now getting this error :( Pretty much hosed the system. Any idea how I can fix this? HELP. :) Reinstalling the crypto package made no difference running 4.8-RELEASE Try installing openssl from ports Running ./Configure from openssl results in the same error... and the port bombs with so : Operating system: i386-pc-freebsd4.8 /usr/libexec/ld-elf.so.1: /usr/lib/libcrypt.so.2: Shared object has no run-time symbol table /usr/libexec/ld-elf.so.1: /usr/lib/libcrypt.so.2: Shared object has no run-time symbol table This system (FreeBSD-elf) is not supported. See file INSTALL for details. === Building for openssl-0.9.7b_1 make: don't know how to make freebsd-shared. Stop *** Error code 2 Stop in /usr/ports/security/openssl. :( ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hosed system
Operating system: i386-pc-freebsd4.8 /usr/libexec/ld-elf.so.1: /usr/lib/libcrypt.so.2: Shared object has no run-time symbol table /usr/libexec/ld-elf.so.1: /usr/lib/libcrypt.so.2: Shared object has no run-time symbol table This system (FreeBSD-elf) is not supported. See file INSTALL for details. === Building for openssl-0.9.7b_1 make: don't know how to make freebsd-shared. Stop *** Error code 2 Stop in /usr/ports/security/openssl. pkg_add -r openssl ? Well... thought it was fixed, but am now getting this : /usr/libexec/ld-elf.so.1: /usr/lib/libskey.so.2: Undefined symbol crypt any insight appreciated... thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lots of input errors...
1) You have a bad cable. CRC and framing errors are usually a result of bad media. 2) You should set the port to auto/auto, not 100/Full hard set, unless you have specifically set that up in rc.conf. If one side is hard set and the other is set to auto, you will see lots of runts because of a duplex mismatch. I think the RFC states you have to go to half duplex if you are autosensing and the other side doesn't respond, which is the case if it's hard set. Ok.. It is set hard to 100BT/FD on both ends. I don't know if you saw this, but since resetting the stats a few hours ago, it shows no errors at all on their end, but were still getting errors on our end... The CRC and frame errors could have been from a media mismatch when things were first setup. Im not sure if the stats have ever been reset. Assuming the errors stay at zero on their end, any ideas? Am going to try another server/router, and if things look better, start replacing hardware on this router... I would say the physical wire is probably bad. Seeing unidirectional errors in this case wouldn't be uncommon; one of the pair of the receive wires may have issues. Have you swapped the cable? Most of the time you won't see framing errors related to duplex mismatching. Also, although this sounds contrary to sane thinking about hard coding of duplex and speed, the Cisco will do better autosensing if you are using an Intel ethernet card on the server. I'm not sure why, but I've seen this happen in the past. For what its worth, changing the NIC fixed it. I've got an onboard rl0, called the worst ethernet controller ever made in the source to atleast 170Mb total, I think it will go higher, thats just our internet traffic, I haven't done any local tests yet to see if we can max it out... The controller in question was a 3COM 3c980C-TXM. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Unable to compile gigabit driver?
I am not able to compile either the ti, or em driver, and get the following errror: linking kernel if_ti.o: In function `ti_rxeof': if_ti.o(.text+0x297b): undefined reference to `vlan_input_tag_p' if_ti.o(.text+0x29d2): undefined reference to `vlan_input_tag_p' if_em.o: In function `em_process_receive_interrupts': if_em.o(.text+0x2d0e): undefined reference to `vlan_input_tag_p' if_em.o(.text+0x2d31): undefined reference to `vlan_input_tag_p' *** Error code 1 Stop in /usr/src/sys/compile/Hssi. This is under FreeBSD 4.7-RELEASE. I also tried the bge driver for kicks and it gives a similar error, but all the fast ethernet drivers I tried compile just fine... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Performace
That's certainly a step in the right direction :) But something is still very wrong performance wise. It has helped, but I still can't push in/out nearly 100Mb/sec. (100Mb in, 100Mb out I mean). A simple FTP transfer locally through the routers gigabit interface causes our internet performance to plummet. I've disabled all the onboard stuff that was sharing IRQs with PCI cards, but I didn't figure that was an issue, didn't make a difference either way. Would the fact the gigabit is on the same PCI bus have any bearing? I would expect to at least get 100BT performance even so, but I don't have any experience with gigabit ethernet... The only thing I can suggest is try different PCI slots, or Gigabit cards, or, worst case a different system. Having NIC's on separate PCI busses (as opposed to both on the same PCI bus) may help it [But that's probably going to need a new board etc.] Thats what I was going to try next, but i've noticed this : gw# netstat -I xl0 -w 1 input (xl0) output packets errs bytespackets errs bytes colls 7120119118416 5566 02507132 0 6754 68498898 5649 03009719 0 7104 98856812 5802 03004529 0 7737199787501 6429 02994557 0 7551169670490 5948 02761794 0 I would guess such a large number of errors per second could be causing the interrupt usuage? From what i've been able to find such input errors are usually caused by a bad cable, or switch... You don't say what Gigabit nic's your using? - I've had a lot of varied results with different nic's, with surprisingly cheap 10/100/1000Mbit cards giving 'reasonable' performance - but get left standing for dust by other more expensive cards. Its an Intel Fiber card, don't know the exact model offhand... The only other thing I can think of is, check the duplex/media options are all setup properly on the cards / switches etc. - or try forcing things to fdx etc. Been there, done that, full duplex/autoselect makes no difference, but its currently set for full/1000SX on both ends. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network Performace
with unused USB and onboard NIC which is also not used. Should I be able to push more than 100Mb sec with such a system? It is not doing anything else, no NAT, one IPFW rule. OS is FreeBSD 4.7-RELEASE. All depends how big the packets are etc. - 90% interrupt time is fairly typical of x86/PC kit shoveling lots of small packets. Try looking into FreeBSD's polling mode - i.e. interrupt free Network cards. If your shifting a lot of small packets (such as online gaming stuff etc.) - you may find your milage pretty limited using standard PC kit - as the x86 architecture wasn't really designed for shifting lots of small packets around [as I've seen many a time in the past :(] This router is routing 99% NNTP traffic, so I wouldn't think small packet size would be it. I tried polling, and its greatly increased the amount of idle CPU, and Interupt is around 20% now... But something is still very wrong performance wise. It has helped, but I still can't push in/out nearly 100Mb/sec. (100Mb in, 100Mb out I mean). A simple FTP transfer locally through the routers gigabit interface causes our internet performance to plummet. I've disabled all the onboard stuff that was sharing IRQs with PCI cards, but I didn't figure that was an issue, didn't make a difference either way. Would the fact the gigabit is on the same PCI bus have any bearing? I would expect to at least get 100BT performance even so, but I don't have any experience with gigabit ethernet... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
perl 5.8 port
Making Digest::MD5 (dynamic) Writing Makefile for Digest::MD5 cp MD5.pm ../../../lib/Digest/MD5.pm /raid/usr/ports/lang/perl5.8/work/perl-5.8.0/miniperl -I../../../lib -I../../ ../lib ../../../lib/ExtUtils/xsubpp -typemap ../../../lib/ExtUtils/typemap -ty pemap typemap MD5.xs MD5.xsc mv MD5.xsc MD5.c cc -c-DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.0/BSDPAN -DHAS_FPSETMASK - DHAS _FLOATINGPOINT_H -fno-strict-aliasing -I/usr/local/include -O -pipe-DVER SION =\2.20\ -DXS_VERSION=\2.20\ -DPIC -fPIC -I../../.. MD5.c MD5.xs: In function `XS_Digest__MD5_md5': MD5.xs:645: `dowarn' undeclared (first use in this function) MD5.xs:645: (Each undeclared identifier is reported only once MD5.xs:645: for each function it appears in.) *** Error code 1 Stop in /raid/usr/ports/lang/perl5.8/work/perl-5.8.0/ext/Digest/MD5. *** Error code 1 Stop in /raid/usr/ports/lang/perl5.8/work/perl-5.8.0. *** Error code 1 This is what happens when I try to compile the perl 5.8 port... same thing happens when compiling perl modules, it exits with similar type errors. Anyone have any idea what might be wrong? This is a recently upgraded machine to 4.7-STABLE, and upgraded all the ports... any ideas? Most of the perl module ports compile, but if I try the same thing from source, they fail. If anyone wants to see an example, i'll post it Thanks. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Perl Problems
I am having problems getting almost any perl module to compile... If I
install from the ports (assuming there is one) they compile fine. But
installing from source fails on just about every module that needs to be
compiled. This is on both perl 5.005_03 (system perl, I believe, this is a
4.5-STABLE system, but is several months old) Here are the failed module
installs :
/home/shawn/mods/Unicode-Map-0.112 {491}make
cc -c-DVERSION=\0.112\ -DXS_VERSION=\0.112\ -DPIC -fpic -I/usr/
libd
ata/perl/5.00503/mach/CORE Map.c
Map.c: In function `XS_Unicode__Map__reverse_unicode':
Map.c:554: `aTHX_' undeclared (first use in this function)
Map.c:554: (Each undeclared identifier is reported only once
Map.c:554: for each function it appears in.)
Map.c:554: syntax error before string constant
Map.c: In function `XS_Unicode__Map__map_hash':
Map.c:602: `aTHX_' undeclared (first use in this function)
Map.c:602: syntax error before string constant
Map.c: In function `XS_Unicode__Map__map_hashlist':
Map.c:649: `aTHX_' undeclared (first use in this function)
Map.c:649: syntax error before string constant
Map.c: In function `XS_Unicode__Map__read_binary_mapping':
Map.c:719: `aTHX_' undeclared (first use in this function)
Map.c:719: syntax error before string constant
Map.c: In function `XS_Unicode__Map__system_test':
Map.c:741: `aTHX_' undeclared (first use in this function)
Map.c:741: syntax error before string constant
*** Error code 1
Stop in /raid/home/shawn/mods/Unicode-Map-0.112.
/home/shawn/mods/IPC-SysV-1.03 {500}make
cc -c-I/usr/local/include -O-DVERSION=\1.03\ -DXS_VERSION=\1.03\
-D
PIC -fpic -I/usr/local/lib/perl5/5.6.0/i386-freebsd/CORE SysV.c
SysV.xs: In function `XS_IPC__SysV_ftok':
SysV.xs:192: `sv_undef' undeclared (first use in this function)
SysV.xs:192: (Each undeclared identifier is reported only once
SysV.xs:192: for each function it appears in.)
*** Error code 1
Stop in /raid/home/shawn/mods/IPC-SysV-1.03.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
