Re: I made a mess. libc
On 22/02/2013 4:44 PM, Shane Ambler wrote: You missed the earlier suggestion - at the single user prompt for a shell don't just hit enter - type in /rescue/sh This suggestion was gold for me, but in a different way. I have for years lamented the passing of static binaries in /bin and /sbin. I forget who mentioned that /rescue/* are statically linked - I had never known that. Today I have just built a 5.4-RELEASE jail on a 9.1-STABLE system, and being able to include a statically linked 9.1-STABLE 'ps' is very useful. The 5.4 version of ps is useless in this jail. And just in case the significance is lost on Bernt, /rescue/sh does not rely on libc, so it won't care if libc is broken. Danny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I made a mess. libc
Thank you all for your input. Went to the office very dark in my mind. I found a cd with amd64 8.0-R and I could copy libc.so.7 I Thank you ALLnow i'm crying so I leave you now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
I made a mess. libc
Hello list! It's me again. I was happily upgrading my jail make build* and so on. Make installworld failed with som chflag set on libc.so.7 so i left jail and went to the host and tought I fixit from there. I did remove the chflag and all was well I tought, but no. Copy it to the jail, someone screamed, ok I'll do that Well the problem is I copied it to the host amd64 and jail is i386. the host locked up hard and after a reboot I get libc.so.7 invalid file format. How do I get it back. I can not burn a cd with livefs, wich should be on memorystick anyway. Thanks for any help and it's needed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I made a mess. libc
On Feb 21, 2013, at 3:34 PM, Bernt Hansson b...@bananmonarki.se wrote: Hello list! It's me again. I was happily upgrading my jail make build* and so on. Make installworld failed with som chflag set on libc.so.7 so i left jail and went to the host and tought I fixit from there. I did remove the chflag and all was well I tought, but no. Copy it to the jail, someone screamed, ok I'll do that Well the problem is I copied it to the host amd64 and jail is i386. the host locked up hard and after a reboot I get libc.so.7 invalid file format. How do I get it back. I can not burn a cd with livefs, wich should be on memorystick anyway. Thanks for any help and it's needed. This is my libc.so.7 from the 19th, for 8-stable amd64, after the patch for the security advisory. root@pf1:/usr/ports/emulators/fuse # ls -l /lib/libc.so.7 -r--r--r-- 1 root wheel 1399225 Feb 19 15:27 /lib/libc.so.7 root@pf1:/usr/ports/emulators/fuse # md5 /lib/libc.so.7 MD5 (/lib/libc.so.7) = 9e4b09aa6dbc731bf56593b736e9fef1 root@pf1:/usr/ports/emulators/fuse # shasum /lib/libc.so.7 19e856f287586f52611aca9a4aa8a4104b65fb4e /lib/libc.so.7 root@pf1:/usr/ports/emulators/fuse # uname -a FreeBSD pf1.backbone.dev 8.3-STABLE FreeBSD 8.3-STABLE #6 r247008M: Tue Feb 19 20:14:57 UTC 2013 r...@pf1.backbone.dev:/usr/obj/usr/src/sys/UNIVERSAL amd64 I can host the file over HTTP if you want. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I made a mess. libc
2013-02-21 15:43, Fleuriot Damien skrev: On Feb 21, 2013, at 3:34 PM, Bernt Hansson b...@bananmonarki.se wrote: Hello list! It's me again. I was happily upgrading my jail make build* and so on. Make installworld failed with som chflag set on libc.so.7 so i left jail and went to the host and tought I fixit from there. I did remove the chflag and all was well I tought, but no. Copy it to the jail, someone screamed, ok I'll do that Well the problem is I copied it to the host amd64 and jail is i386. the host locked up hard and after a reboot I get libc.so.7 invalid file format. How do I get it back. I can not burn a cd with livefs, wich should be on memorystick anyway. Thanks for any help and it's needed. This is my libc.so.7 from the 19th, for 8-stable amd64, after the patch for the security advisory. root@pf1:/usr/ports/emulators/fuse # ls -l /lib/libc.so.7 -r--r--r-- 1 root wheel 1399225 Feb 19 15:27 /lib/libc.so.7 root@pf1:/usr/ports/emulators/fuse # md5 /lib/libc.so.7 MD5 (/lib/libc.so.7) = 9e4b09aa6dbc731bf56593b736e9fef1 root@pf1:/usr/ports/emulators/fuse # shasum /lib/libc.so.7 19e856f287586f52611aca9a4aa8a4104b65fb4e /lib/libc.so.7 root@pf1:/usr/ports/emulators/fuse # uname -a FreeBSD pf1.backbone.dev 8.3-STABLE FreeBSD 8.3-STABLE #6 r247008M: Tue Feb 19 20:14:57 UTC 2013 r...@pf1.backbone.dev:/usr/obj/usr/src/sys/UNIVERSAL amd64 I can host the file over HTTP if you want. That was very nice of you, but how do I get the file into my machine? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: I made a mess. libc
Is it the base machine that won't boot? I got this ... My latest version of Druid has a very sophisticated Interactive Disk Repair script that will assemble your system humpty-dumpty style while booted from a CD or Thumb drive (you said you couldn't burn a CD, but it wasn't clear whether you could master a thumb drive). http://sourceforge.net/projects/druidbsd/files/FreeBSD-8.3_Druid-1.0b60.iso/download When you run the Interactive Disk Repair (IDR) Shell option, it presents you with a few questions (like, I've found a saved network interface in rc.conf(5) -- would you like me to activate it for you?), and ultimately mounts your system to present a working shell to fix your problems. Important: when it asks you if you want to chroot into the mounted filesystem, say NO (you're libc isn't working, so that would be a bad idea) -- rather, run from the LiveFS environment where /mnt is your mounted system. There's even a copy of libc in the LiveFS environment that you can copy over your old one... cp /cdrom/freebsd/rescue/lib/libc.so.7 /mnt/lib/libc.so.7 (if I recall correctly) -- Devin From: owner-freebsd-questi...@freebsd.org [owner-freebsd-questi...@freebsd.org] on behalf of Bernt Hansson [b...@bananmonarki.se] Sent: Thursday, February 21, 2013 7:51 AM To: Fleuriot Damien Cc: questions FreeBSD Subject: Re: I made a mess. libc 2013-02-21 15:43, Fleuriot Damien skrev: On Feb 21, 2013, at 3:34 PM, Bernt Hansson b...@bananmonarki.se wrote: Hello list! It's me again. I was happily upgrading my jail make build* and so on. Make installworld failed with som chflag set on libc.so.7 so i left jail and went to the host and tought I fixit from there. I did remove the chflag and all was well I tought, but no. Copy it to the jail, someone screamed, ok I'll do that Well the problem is I copied it to the host amd64 and jail is i386. the host locked up hard and after a reboot I get libc.so.7 invalid file format. How do I get it back. I can not burn a cd with livefs, wich should be on memorystick anyway. Thanks for any help and it's needed. This is my libc.so.7 from the 19th, for 8-stable amd64, after the patch for the security advisory. root@pf1:/usr/ports/emulators/fuse # ls -l /lib/libc.so.7 -r--r--r-- 1 root wheel 1399225 Feb 19 15:27 /lib/libc.so.7 root@pf1:/usr/ports/emulators/fuse # md5 /lib/libc.so.7 MD5 (/lib/libc.so.7) = 9e4b09aa6dbc731bf56593b736e9fef1 root@pf1:/usr/ports/emulators/fuse # shasum /lib/libc.so.7 19e856f287586f52611aca9a4aa8a4104b65fb4e /lib/libc.so.7 root@pf1:/usr/ports/emulators/fuse # uname -a FreeBSD pf1.backbone.dev 8.3-STABLE FreeBSD 8.3-STABLE #6 r247008M: Tue Feb 19 20:14:57 UTC 2013 r...@pf1.backbone.dev:/usr/obj/usr/src/sys/UNIVERSAL amd64 I can host the file over HTTP if you want. That was very nice of you, but how do I get the file into my machine? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I made a mess. libc
2013-02-21 18:01, Teske, Devin skrev: Is it the base machine that won't boot? I got this ... That is correct. So no cd burning no nothing...Well it want to drop in to a single shell bla bla bla press enter for /bin/sh enter libexec* libc.so.7: invalid file format I do not want to reinstall, have 4 encrypted disks. My latest version of Druid has a very sophisticated Interactive Disk Repair script that will assemble your system humpty-dumpty style while booted from a CD or Thumb drive (you said you couldn't burn a CD, but it wasn't clear whether you could master a thumb drive). http://sourceforge.net/projects/druidbsd/files/FreeBSD-8.3_Druid-1.0b60.iso/download When you run the Interactive Disk Repair (IDR) Shell option, it presents you with a few questions (like, I've found a saved network interface in rc.conf(5) -- would you like me to activate it for you?), and ultimately mounts your system to present a working shell to fix your problems. Important: when it asks you if you want to chroot into the mounted filesystem, say NO (you're libc isn't working, so that would be a bad idea) -- rather, run from the LiveFS environment where /mnt is your mounted system. There's even a copy of libc in the LiveFS environment that you can copy over your old one... cp /cdrom/freebsd/rescue/lib/libc.so.7 /mnt/lib/libc.so.7 (if I recall correctly) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I made a mess. libc
On Feb 21, 2013, at 6:22 PM, Bernt Hansson b...@bananmonarki.se wrote: 2013-02-21 18:01, Teske, Devin skrev: Is it the base machine that won't boot? I got this ... That is correct. So no cd burning no nothing...Well it want to drop in to a single shell bla bla bla press enter for /bin/sh enter libexec* libc.so.7: invalid file format I do not want to reinstall, have 4 encrypted disks. And you have absolutely no way to boot I don't know, PXE, USB ? Do you have remote console access, anything ? I'll tell you what, I'll still scp the file to a www and give you the link, if you should find a way to access your file system, you can always copy it over. http://my.gd/libc.so.7 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I made a mess. libc
On Thu, 21 Feb 2013 18:22:47 +0100 Bernt Hansson b...@bananmonarki.se wrote: 2013-02-21 18:01, Teske, Devin skrev: Is it the base machine that won't boot? I got this ... That is correct. So no cd burning no nothing...Well it want to drop in to a single shell bla bla bla press enter for /bin/sh enter libexec* libc.so.7: invalid file format IIRC you get an option at this point to enter a full path to the shell, enter /rescue/sh which will get you a statically linked shell. You should then be able to use the tools in /rescue to replace libc provided you can somehow get a copy of it where you can read it. -- Steve O'Hara-Smith st...@sohara.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: I made a mess. libc
Can you specify perhaps /rescue/sh as the single-user shell? That should get you in. Then you have to stick to static executables like /rescue/rcp to remotely transfer files. Perhaps someone can host a file on a machine that can be reached via /rescue/rcp for you. -- Devin From: Bernt Hansson [b...@bananmonarki.se] Sent: Thursday, February 21, 2013 9:22 AM To: Teske, Devin Cc: Fleuriot Damien; questions FreeBSD Subject: Re: I made a mess. libc 2013-02-21 18:01, Teske, Devin skrev: Is it the base machine that won't boot? I got this ... That is correct. So no cd burning no nothing...Well it want to drop in to a single shell bla bla bla press enter for /bin/sh enter libexec* libc.so.7: invalid file format I do not want to reinstall, have 4 encrypted disks. My latest version of Druid has a very sophisticated Interactive Disk Repair script that will assemble your system humpty-dumpty style while booted from a CD or Thumb drive (you said you couldn't burn a CD, but it wasn't clear whether you could master a thumb drive). https://urldefense.proofpoint.com/v1/url?u=http://sourceforge.net/projects/druidbsd/files/FreeBSD-8.3_Druid-1.0b60.iso/downloadk=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0Ar=LTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0Am=07piZUd2tTTVmRt2abbbhXwBr9OUC7olyXwRy6BdjoM%3D%0As=a0b244b57abd48f38a1cd817513b96950f4c6f2f035b3d33ddee2a27938b2f04 When you run the Interactive Disk Repair (IDR) Shell option, it presents you with a few questions (like, I've found a saved network interface in rc.conf(5) -- would you like me to activate it for you?), and ultimately mounts your system to present a working shell to fix your problems. Important: when it asks you if you want to chroot into the mounted filesystem, say NO (you're libc isn't working, so that would be a bad idea) -- rather, run from the LiveFS environment where /mnt is your mounted system. There's even a copy of libc in the LiveFS environment that you can copy over your old one... cp /cdrom/freebsd/rescue/lib/libc.so.7 /mnt/lib/libc.so.7 (if I recall correctly) _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I made a mess. libc
As per Devin's suggestion, I just set up a RCP server from which you'll be able to grab libc.so.7 using /rescue/rcp I'm gonna need, in private, your IP address so I can add you both to .rhosts and firewall rules. I'm leaving work now so I may not answer again before 2-3 hours. On Feb 21, 2013, at 6:46 PM, Teske, Devin devin.te...@fisglobal.com wrote: Can you specify perhaps /rescue/sh as the single-user shell? That should get you in. Then you have to stick to static executables like /rescue/rcp to remotely transfer files. Perhaps someone can host a file on a machine that can be reached via /rescue/rcp for you. -- Devin From: Bernt Hansson [b...@bananmonarki.se] Sent: Thursday, February 21, 2013 9:22 AM To: Teske, Devin Cc: Fleuriot Damien; questions FreeBSD Subject: Re: I made a mess. libc 2013-02-21 18:01, Teske, Devin skrev: Is it the base machine that won't boot? I got this ... That is correct. So no cd burning no nothing...Well it want to drop in to a single shell bla bla bla press enter for /bin/sh enter libexec* libc.so.7: invalid file format I do not want to reinstall, have 4 encrypted disks. My latest version of Druid has a very sophisticated Interactive Disk Repair script that will assemble your system humpty-dumpty style while booted from a CD or Thumb drive (you said you couldn't burn a CD, but it wasn't clear whether you could master a thumb drive). https://urldefense.proofpoint.com/v1/url?u=http://sourceforge.net/projects/druidbsd/files/FreeBSD-8.3_Druid-1.0b60.iso/downloadk=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0Ar=LTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0Am=07piZUd2tTTVmRt2abbbhXwBr9OUC7olyXwRy6BdjoM%3D%0As=a0b244b57abd48f38a1cd817513b96950f4c6f2f035b3d33ddee2a27938b2f04 When you run the Interactive Disk Repair (IDR) Shell option, it presents you with a few questions (like, I've found a saved network interface in rc.conf(5) -- would you like me to activate it for you?), and ultimately mounts your system to present a working shell to fix your problems. Important: when it asks you if you want to chroot into the mounted filesystem, say NO (you're libc isn't working, so that would be a bad idea) -- rather, run from the LiveFS environment where /mnt is your mounted system. There's even a copy of libc in the LiveFS environment that you can copy over your old one... cp /cdrom/freebsd/rescue/lib/libc.so.7 /mnt/lib/libc.so.7 (if I recall correctly) _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I made a mess. libc
On 2/21/2013 11:22 AM, Bernt Hansson wrote: 2013-02-21 18:01, Teske, Devin skrev: Is it the base machine that won't boot? I got this ... That is correct. So no cd burning no nothing...Well it want to drop in to a single shell bla bla bla press enter for /bin/sh enter libexec* libc.so.7: invalid file format I do not want to reinstall, have 4 encrypted disks. If you get the PC-BSD memstick, it boots FreeBSD with a GUI. You'll want the USB Live probably. The PC-BSD versions match the FreeBSD versions. If you're running 8.3, get the 8.3 memstick for instance. You could be safe just copying the libc from PC-BSD to your host, and then just reinstall for sanity's sake. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: I made a mess. libc
On 22/02/2013 10:07, Bernt Hansson wrote: Yes that is an idea. Since Damien was kind to host the file I downloaded it and will try later today (friday) The problem is I can't burn or otherwise get in to the machine. libc.so.7: invalid file format You missed the earlier suggestion - at the single user prompt for a shell don't just hit enter - type in /rescue/sh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Clang with libc++ doesn't find quuick_exit()
On Fri, 10 Aug 2012 02:21:28 +0400 Артем Зуйков cher...@gmail.com wrote: Hi, I can't build anything with clang libc++ What am I doing wrong? clang++ -stdlib=libc++ test1.cpp -o x In file included from test1.cpp:1: /usr/include/c++/v1/cstdlib:134:9: error: no member named 'at_quick_exit' in the global namespace using ::at_quick_exit; ~~^ /usr/include/c++/v1/cstdlib:135:9: error: no member named 'quick_exit' in the global namespace using ::quick_exit; ~~^ 2 errors generated. A part of /usr/include/stdlib.h #if __ISO_C_VISIBLE = 2011 || __cplusplus = 201103L _Noreturn void quick_exit(int); int at_quick_exit(void (*)(void)); #endif /* __ISO_C_VISIBLE = 2011 */ Hi, quick_exit() has only become available in C++ as part of the C++11 standard. Thus you will have to invoke clang++ as follows: clang++ -std=c++11 -stdlib=libc++ test1.cpp -o x or '-std=c++0x' if you're using an older version of clang++ Best regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Clang with libc++ doesn't find quuick_exit()
Hi, I can't build anything with clang libc++ What am I doing wrong? clang++ -stdlib=libc++ test1.cpp -o x In file included from test1.cpp:1: /usr/include/c++/v1/cstdlib:134:9: error: no member named 'at_quick_exit' in the global namespace using ::at_quick_exit; ~~^ /usr/include/c++/v1/cstdlib:135:9: error: no member named 'quick_exit' in the global namespace using ::quick_exit; ~~^ 2 errors generated. A part of /usr/include/stdlib.h #if __ISO_C_VISIBLE = 2011 || __cplusplus = 201103L _Noreturn void quick_exit(int); int at_quick_exit(void (*)(void)); #endif /* __ISO_C_VISIBLE = 2011 */ clang++ -v -stdlib=libc++ -D__ISO_C_VISIBLE=2011 test1.cpp -o x FreeBSD clang version 3.1 (branches/release_31 156863) 20120523 Target: x86_64-unknown-freebsd9.0 Thread model: posix /usr/bin/clang++ -cc1 -triple x86_64-unknown-freebsd9.0 -emit-obj -mrelax-all -disable-free -main-file-name test1.cpp -mrelocation-model static -mdisable-fp-elim -masm-verbose -mconstructor-aliases -munwind-tables -target-cpu x86-64 -momit-leaf-frame-pointer -v -resource-dir /usr/bin/../lib/clang/3.1 -D __ISO_C_VISIBLE=2011 -fmodule-cache-path /var/tmp/clang-module-cache -stdlib=libc++ -fdeprecated-macro -fdebug-compilation-dir /home/42/gw/new-iface -ferror-limit 19 -fmessage-length 90 -mstackrealign -fgnu-runtime -fobjc-runtime-has-arc -fobjc-runtime-has-weak -fobjc-dispatch-method=non-legacy -fcxx-exceptions -fexceptions -fdiagnostics-show-option -fcolor-diagnostics -o /tmp/test1-jPurFk.o -x c++ test1.cpp clang -cc1 version 3.1 based upon LLVM 3.1 default target x86_64-unknown-freebsd9.0 ignoring nonexistent directory /usr/bin/../lib/clang/3.1/include #include ... search starts here: #include ... search starts here: /usr/include/c++/v1 /usr/include/clang/3.1 /usr/include End of search list. In file included from test1.cpp:1: /usr/include/c++/v1/cstdlib:134:9: error: no member named 'at_quick_exit' in the global namespace using ::at_quick_exit; ~~^ /usr/include/c++/v1/cstdlib:135:9: error: no member named 'quick_exit' in the global namespace using ::quick_exit; ~~^ 2 errors generated. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
libc version
Hello... I upgrade the server from version 8.2 to 8.3, and rebuild all packages.. it all works... Then I installed a binary package (8.3) in an old 8.2 ... every package works... gnome, nautilus, wget about 800 of them the only one that does not work is postgesql84-server when I try to run it it I got the message: /libexec/ld-elf.so.1: /lib/libc.so.7: version FBSD_1.3 required by /usr/local/bin/postgres not found seems that only postgres is check for the libc version??? is there a compile switch to check for that??? Of course, if I compile postgres in the 8.2 or upgrade to 8.3 it works... Thanks for any help, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: libc version
From owner-freebsd-questi...@freebsd.org Mon Jun 18 08:21:38 2012 From: Sergio de Almeida Lenzi lenzi.ser...@gmail.com To: freebsd-questions@freebsd.org Date: Mon, 18 Jun 2012 10:20:09 -0300 Subject: libc version Hello... I upgrade the server from version 8.2 to 8.3, and rebuild all packages.. it all works... Then I installed a binary package (8.3) in an old 8.2 ... every package works... gnome, nautilus, wget about 800 of them the only one that does not work is postgesql84-server when I try to run it it I got the message: /libexec/ld-elf.so.1: /lib/libc.so.7: version FBSD_1.3 required by /usr/local/bin/postgres not found seems that only postgres is check for the libc version??? INCORRECT. Postgres is jjust the only one of those programs that _requires_ a 'minimum' version level that is newer than the one installed. is there a compile switch to check for that??? No. Of course, if I compile postgres in the 8.2 or upgrade to 8.3 it works... Naturally. do it right and it will work'. grin The required _minimum_ version of a runtime library is specified in the program source code -- because it uses features that did not exist in any version prior to that one. There is *NO* way to tell _at_compile_time_ what version of a runtome library will be present when the program is executed. The 'compiled on 8.3' Postgres binary requires a newer version of libc than exists in 8.2. Compile on 8.2 and it builds using diferent code that does not require the newer libc feature. hence the 8.2-compiled code works on 8.2. The solution to your problem, as you found, is to _not_ use 'more current' binaries in 'down-rev' environments. upward compatibility is almost always present in a package. backward compatibility is *always* a crap-shoot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: libc version
Ok thank you for your answer... the problem is in the postgres code and not in a compile switch or something like that... I will upgrade all my 8.2 to 8.3... systems to do this, I build an 8.3 from ground zero, and than do a rsync from this one to the others, directories: /usr/obj /usr/src than... on each target, a make installworld installkernel should do the upgrade... Any comments?? Sergio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
libc regex word-boundary support fallen-off?
I've noticed for some time that claws-mail and less (which I think use libc's regex(3)) don't support word boundaries in searches. I might be delusional, but I think I've used \b in the past in both of those applications in FreeBSD. According to regex(3) it's an implementation POSIX.2, so the feature needn't be supported, but at the bottom of the page it says word-boundary matching is a bit of a kludge, so presumably it has been. Does anyone know what's going on? I switched from i386 to amd64 last year so it might be something to do with that. I'm currently using 8.2p6. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: libc regex word-boundary support fallen-off?
RW rwmailli...@googlemail.com writes: I've noticed for some time that claws-mail and less (which I think use libc's regex(3)) don't support word boundaries in searches. I might be delusional, but I think I've used \b in the past in both of those applications in FreeBSD. According to regex(3) it's an implementation POSIX.2, so the feature needn't be supported, but at the bottom of the page it says word-boundary matching is a bit of a kludge, so presumably it has been. Does anyone know what's going on? I switched from i386 to amd64 last year so it might be something to do with that. I'm currently using 8.2p6. The only way I have found to do it is [[::]] and [[::]]. That is very awkward, so I't love to hear of a shorter way. I found them in the re_format(7) manpage. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
any effort to use bsd libc on Linux?
Or expand bionic to full set bsd libc? Thanks for help. joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Missing Library libc-client4.so.9
Hello all, I have FreeBSD 6.3-RELEASE. Suddenly I can not start my apache webserver which load php5. The error said, missing libc-client4.so.9. I checked that libc-client4.so.9 should be in /usr/local/lib but I can not find it. How do I get this one? Best Regards, Kalpin E. Silaen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Missing Library libc-client4.so.9
On 28/01/2010 10:37, kal...@muliahost.com wrote: I checked that libc-client4.so.9 should be in /usr/local/lib but I can not find it. It's installed by the mail/cclient port, which is a dependency of the php5-imap module. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
libc or OpenSSL patches break ssh?
Am running 6.4-PRERELEASE. Received FreeBSD-SA-09:07.libc / FreeBSD-SA-09:08.openssl notifications today, applied applicable patches correctly. However, now when anyone attempts to connect to my server via SSH, the connection is closed after they enter their login password. /var/log/messages says the following when they try to login: Apr 22 12:53:12 x sshd[75505]: fatal: openpty returns device for which ttyname fails. Apr 22 12:53:12 x sshd[75505]: error: chown 0 0 failed: No such file or directory Apr 22 12:53:12 x sshd[75505]: error: chmod 0666 failed: No such file or directory ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
libc or OpenSSL patches break ssh?
Am running 6.4-PRERELEASE. Received FreeBSD-SA-09:07.libc / FreeBSD-SA-09:08.openssl notifications today, applied applicable patches correctly. However, now when anyone attempts to connect to my server via SSH, the connection is closed after they enter their login password. /var/log/messages says the following when they try to login: Apr 22 12:53:12 x sshd[75505]: fatal: openpty returns device for which ttyname fails. Apr 22 12:53:12 x sshd[75505]: error: chown 0 0 failed: No such file or directory Apr 22 12:53:12 x sshd[75505]: error: chmod 0666 failed: No such file or directory ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: libc or OpenSSL patches break ssh?
Figured it out. The libc patch instructions don't tell you to rebuild libutil. You need to do that. On Wed, 22 Apr 2009, Jake Evans wrote: Am running 6.4-PRERELEASE. Received FreeBSD-SA-09:07.libc / FreeBSD-SA-09:08.openssl notifications today, applied applicable patches correctly. However, now when anyone attempts to connect to my server via SSH, the connection is closed after they enter their login password. /var/log/messages says the following when they try to login: Apr 22 12:53:12 x sshd[75505]: fatal: openpty returns device for which ttyname fails. Apr 22 12:53:12 x sshd[75505]: error: chown 0 0 failed: No such file or directory Apr 22 12:53:12 x sshd[75505]: error: chmod 0666 failed: No such file or directory ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: libc or OpenSSL patches break ssh?
On Wednesday 22 April 2009 20:11:09 Jake Evans wrote: Am running 6.4-PRERELEASE. Received FreeBSD-SA-09:07.libc / FreeBSD-SA-09:08.openssl notifications today, applied applicable patches correctly. However, now when anyone attempts to connect to my server via SSH, the connection is closed after they enter their login password. /var/log/messages says the following when they try to login: Apr 22 12:53:12 x sshd[75505]: fatal: openpty returns device for which ttyname fails. Apr 22 12:53:12 x sshd[75505]: error: chown 0 0 failed: No such file or directory Apr 22 12:53:12 x sshd[75505]: error: chmod 0666 failed: No such file or directory You did a full buildworld and restarted sshd, or just updated openssl? -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to do regression on libc?
Unga [EMAIL PROTECTED] writes: How to do regression on libc to verify the correctness? There are conformance test suites out there. The decent ones all seem to cost money, but you might want to look at the Open POSIX project. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to do regression on libc?
Hi all How to do regression on libc to verify the correctness? Kind regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
What consists FreeBSD Libc?
Hi all What consists FreeBSD Libc (/lib/libc.so.7)? Is it only /usr/src/lib/libc/* ? I have compiled /usr/src/lib/libc/*, the resulting libc.so.7 is about 65,000 bytes smaller. Kind regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What consists FreeBSD Libc?
Unga wrote: Hi all What consists FreeBSD Libc (/lib/libc.so.7)? Is it only /usr/src/lib/libc/* ? Yes. I have compiled /usr/src/lib/libc/*, the resulting libc.so.7 is about 65,000 bytes smaller. Than what? It will change depending on your CFLAGS. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What consists FreeBSD Libc?
with the same compiler options and same compiler as used with binary distribution? On Sun, 8 Jun 2008, Unga wrote: Hi all What consists FreeBSD Libc (/lib/libc.so.7)? Is it only /usr/src/lib/libc/* ? I have compiled /usr/src/lib/libc/*, the resulting libc.so.7 is about 65,000 bytes smaller. Kind regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What consists FreeBSD Libc?
--- On Sun, 6/8/08, Kris Kennaway [EMAIL PROTECTED] wrote: From: Kris Kennaway [EMAIL PROTECTED] Subject: Re: What consists FreeBSD Libc? To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Sunday, June 8, 2008, 6:37 PM Unga wrote: Hi all What consists FreeBSD Libc (/lib/libc.so.7)? Is it only /usr/src/lib/libc/* ? Yes. I have compiled /usr/src/lib/libc/*, the resulting libc.so.7 is about 65,000 bytes smaller. Than what? It will change depending on your CFLAGS. Thanks Kris Wojciech for replies. Its great to get it confirmed that FreeBSD Libc is only /usr/src/lib/libc/* as I presumed. I have compiled and installed the FreeBSD Libc into a temp directory. The size of /tmp/libc.so.7 is about 65,000 bytes smaller than /lib/libc.so.7. The /lib/libc.so.7 is dated May 25, 2008. I did not touch CFLAGS or anything other than DESTDIR. But I really forgot, the gcc version is different. The /lib/libc.so.7 is by gcc 4.2.1, but the /tmp/libc.so.7 is by gcc 4.3.0. May be the code generation of the latest gcc may be better. I think the size difference may not be an issue as the libc is get it compiled and installed without any error. The GNU glibc has a make check, but there is no make check target for FreeBSD libc. How do you guys test it? Is the /usr/src/tools/regression/ any help for that? Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What consists FreeBSD Libc?
Its great to get it confirmed that FreeBSD Libc is only /usr/src/lib/libc/* as I presumed. I have compiled and installed the FreeBSD Libc into a temp directory. The size of /tmp/libc.so.7 is about 65,000 bytes smaller than /lib/libc.so.7. The /lib/libc.so.7 is dated May 25, 2008. I did not touch CFLAGS or anything other than DESTDIR. But I really forgot, the gcc version is different. The /lib/libc.so.7 is by gcc 4.2.1, but the /tmp/libc.so.7 is by gcc 4.3.0. May be the code generation of the latest gcc may be better. indeed it is better. while difference between gcc 3.* and 4.* is HUGE in respect of code size. after i upgraded to FreeBSD 7 from 6.3 (so gcc got upgraded to 4.*) i recompiled bash. same version, 20% smaller! finally gcc turned to rule small code=fast code, always true on processors with at least 1 level of cache, not mentioning 2 or 3 cache levels :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
libc documentation
Hi, I need to know where I can find the full documentation of the last libc library. Thanks, -- Robe. En el verdadero amor, el alma oculta al cuerpo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libc documentation
In the last episode (Dec 20), Robe said: I need to know where I can find the full documentation of the last libc library. Most of the libc documentation should be in /usr/src/lib/libc/ . Any file ending in .2 or .3 is a manpage. They are also installed in /usr/share/man and are available using the man command. Run man 3 printf, for example. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
avr-libc port problem
Dear list. I found a problem with the port named avr-libc. The reason is ... there is one line of code in the Makefile with the following content: BROKEN= Does not build what can be the reason to checkin an intentionally broken makefile, and how can I use this port again? thanks in advance I. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: avr-libc port problem
On Sat, Oct 06, 2007 at 07:43:23PM +0300, Ivan Dimitrov wrote: Dear list. I found a problem with the port named avr-libc. The reason is ... there is one line of code in the Makefile with the following content: BROKEN= Does not build what can be the reason to checkin an intentionally broken makefile, It is a warning that building this port doesn't currently work. The build cluster probably detected this, so it was marked broken. It's up to the port maintainer or any other interested person to fix it. and how can I use this port again? - read the FreeBSD Porter's Handbook - remove the BROKEN line from the port's makefile - try to build it and see where it breaks - make it work again. - submit a PR with the changes Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpRrOltTfzwY.pgp Description: PGP signature
Re: avr-libc port problem
On Saturday 06 October 2007 18:43:23 Ivan Dimitrov wrote: I found a problem with the port named avr-libc. The reason is ... there is one line of code in the Makefile with the following content: BROKEN= Does not build what can be the reason to checkin an intentionally broken makefile, and how can I use this port again? thanks in advance This means the port does not build, but the MAINTAINER cannot figure out why / how to fix it / has no time to look into it / is waiting for patches from authors / ... So, at present you cannot use this version. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade avr-libc error
Greetings, I am running FreeBSD 6.0-RELEASE #0 I am attempting to upgrade my avr-libc port. (/usr/ports/devel/avr-libc) pkg_version -v shows: avr-libc-1.2.5,1 needs updating (port has 1.4.3,1) Note: all other ports show current except kde related items. So, I updated my port collection: /usr/local/bin/cvsup -L 2 ~/ports-supfile pkgdb -vF Next, I try to upgrade the port: portupgrade avr-libc I get: ** Port marked as IGNORE: devel/avr-libc: is marked as broken: Incomplete pkg-plist Opening the /usr/ports/devel/avr-libc/Makefile, I see this line: BROKEN= Incomplete pkg-plist What should I do to fix this error? Thanks. ps On a related note, I see http://www.freebsd.org/cgi/query-pr.cgi?pr=91145 mentions a problem, but it appears to relate to 7.0-CURRENT so I do not know if it applies. -- ___ Play 100s of games for FREE! http://games.mail.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade avr-libc error
On Feb 19, 2006, at 9:13 PM, Steve Pauly wrote: pkg_version -v shows: avr-libc-1.2.5,1 needs updating (port has 1.4.3,1) Note: all other ports show current except kde related items. So, I updated my port collection: /usr/local/bin/cvsup -L 2 ~/ports-supfile pkgdb -vF Next, I try to upgrade the port: portupgrade avr-libc I get: ** Port marked as IGNORE: devel/avr-libc: is marked as broken: Incomplete pkg-plist Opening the /usr/ports/devel/avr-libc/Makefile, I see this line: BROKEN= Incomplete pkg-plist What should I do to fix this error? does pkg_version -v still say the same thing as it did before your cvsup? There is not a BROKEN line in the 1.4.3,1 version I have. It built just now with a simple (so as not to disturb my installed version): % cd /usr/ports/devel/avr-libc % make -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade avr-libc error
On Sun, Feb 19, 2006 at 10:38:15PM -0600, David Kelly wrote: On Feb 19, 2006, at 9:13 PM, Steve Pauly wrote: pkg_version -v shows: avr-libc-1.2.5,1 needs updating (port has 1.4.3,1) Note: all other ports show current except kde related items. So, I updated my port collection: /usr/local/bin/cvsup -L 2 ~/ports-supfile pkgdb -vF Next, I try to upgrade the port: portupgrade avr-libc I get: ** Port marked as IGNORE: devel/avr-libc: is marked as broken: Incomplete pkg-plist Opening the /usr/ports/devel/avr-libc/Makefile, I see this line: BROKEN= Incomplete pkg-plist What should I do to fix this error? does pkg_version -v still say the same thing as it did before your cvsup? There is not a BROKEN line in the 1.4.3,1 version I have. It built just now with a simple (so as not to disturb my installed version): I added it a little while ago. If the OP doesn't care about stale files being left behind by the port, he can build with TRYBROKEN set. Kris pgppOjjGHB2Iq.pgp Description: PGP signature
Re: portupgrade avr-libc error
Kris, I added TRYBROKEN= yes in the Makefile and ran portupgrade avr-libc (getting further than before) with the following results: install -o root -g wheel -m 444 /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/LICENSE /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/AUTHORS /usr/local/share/doc/avr-libc install: wrong number or types of arguments usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /usr/ports/devel/avr-libc. *** Error code 1 Stop in /usr/ports/devel/avr-libc. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade4660.0 make reinstall egrep: /var/db/pkg/avr-libc-1.2.5,1/+CONTENTS: No such file or directory --- Restoring the old version ** Fix the installation problem and try again. [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 172 packages found (-0 +1) . done] ** Listing the failed packages (*:skipped / !:failed) ! devel/avr-libc (avr-libc-1.2.5,1) (install error) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed As expected pkg_version shows the old libc still there. Looking at this line: install -o root -g wheel -m 444 /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/LICENSE /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/AUTHORS /usr/local/share/doc/avr-libc I notice that that the first two file parameters specify files, while the last one specifies a directory. Is that the issue? Just guessing, newbie here. The other parameters seem okay I guess. What am I doing wrong? Thanks. Steve. - Original Message - From: Kris Kennaway [EMAIL PROTECTED] To: David Kelly [EMAIL PROTECTED] Subject: Re: portupgrade avr-libc error Date: Sun, 19 Feb 2006 23:44:12 -0500 On Sun, Feb 19, 2006 at 10:38:15PM -0600, David Kelly wrote: On Feb 19, 2006, at 9:13 PM, Steve Pauly wrote: pkg_version -v shows: avr-libc-1.2.5,1 needs updating (port has 1.4.3,1) Note: all other ports show current except kde related items. So, I updated my port collection: /usr/local/bin/cvsup -L 2 ~/ports-supfile pkgdb -vF Next, I try to upgrade the port: portupgrade avr-libc I get: ** Port marked as IGNORE: devel/avr-libc: is marked as broken: Incomplete pkg-plist Opening the /usr/ports/devel/avr-libc/Makefile, I see this line: BROKEN= Incomplete pkg-plist What should I do to fix this error? does pkg_version -v still say the same thing as it did before your cvsup? There is not a BROKEN line in the 1.4.3,1 version I have. It built just now with a simple (so as not to disturb my installed version): I added it a little while ago. If the OP doesn't care about stale files being left behind by the port, he can build with TRYBROKEN set. Kris 2.dat -- ___ Play 100s of games for FREE! http://games.mail.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade avr-libc error
On Mon, Feb 20, 2006 at 12:27:49AM -0500, Steve Pauly wrote: Kris, I added TRYBROKEN= yes in the Makefile and ran portupgrade avr-libc (getting further than before) with the following results: install -o root -g wheel -m 444 /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/LICENSE /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/AUTHORS /usr/local/share/doc/avr-libc install: wrong number or types of arguments usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /usr/ports/devel/avr-libc. *** Error code 1 Stop in /usr/ports/devel/avr-libc. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade4660.0 make reinstall egrep: /var/db/pkg/avr-libc-1.2.5,1/+CONTENTS: No such file or directory --- Restoring the old version ** Fix the installation problem and try again. [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 172 packages found (-0 +1) . done] ** Listing the failed packages (*:skipped / !:failed) ! devel/avr-libc (avr-libc-1.2.5,1) (install error) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed As expected pkg_version shows the old libc still there. Looking at this line: install -o root -g wheel -m 444 /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/LICENSE /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/AUTHORS /usr/local/share/doc/avr-libc I notice that that the first two file parameters specify files, while the last one specifies a directory. Is that the issue? Just guessing, newbie here. The other parameters seem okay I guess. What am I doing wrong? Dunno, the port builds fine on a clean system. Is /usr/local/share/doc/avr-libc not a directory on your system? Kris pgpvol6KGiXWU.pgp Description: PGP signature
Re: portupgrade avr-libc error
Kris, /usr/local/share/doc/avr-libc is a good directory. Should the parameter to install be files or directories? Do you think I should pkg_delete avr-libc ? Also, avr-libc was built from ports as part of avr-gcc, not that long ago. The whole install is but a few weeks old. Thanks. - Original Message - From: Kris Kennaway [EMAIL PROTECTED] To: Steve Pauly [EMAIL PROTECTED] Subject: Re: portupgrade avr-libc error Date: Mon, 20 Feb 2006 00:31:57 -0500 On Mon, Feb 20, 2006 at 12:27:49AM -0500, Steve Pauly wrote: Kris, I added TRYBROKEN= yes in the Makefile and ran portupgrade avr-libc (getting further than before) with the following results: install -o root -g wheel -m 444 /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/LICENSE /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/AUTHORS /usr/local/share/doc/avr-libc install: wrong number or types of arguments usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /usr/ports/devel/avr-libc. *** Error code 1 Stop in /usr/ports/devel/avr-libc. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade4660.0 make reinstall egrep: /var/db/pkg/avr-libc-1.2.5,1/+CONTENTS: No such file or directory --- Restoring the old version ** Fix the installation problem and try again. [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 172 packages found (-0 +1) . done] ** Listing the failed packages (*:skipped / !:failed) ! devel/avr-libc (avr-libc-1.2.5,1) (install error) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed As expected pkg_version shows the old libc still there. Looking at this line: install -o root -g wheel -m 444 /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/LICENSE /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/AUTHORS /usr/local/share/doc/avr-libc I notice that that the first two file parameters specify files, while the last one specifies a directory. Is that the issue? Just guessing, newbie here. The other parameters seem okay I guess. What am I doing wrong? Dunno, the port builds fine on a clean system. Is /usr/local/share/doc/avr-libc not a directory on your system? Kris 2.dat -- ___ Play 100s of games for FREE! http://games.mail.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade avr-libc error
Issue was resolved. in /etc/make.conf I had added a line NOPORTDOCS=yes to keep from building the docs, which would require Latex, etc. Once I commented out that line, the port upgraded without issue. At least one 87MB file had to be downloaded though! Thanks for your help. Steve. - Original Message - From: Kris Kennaway [EMAIL PROTECTED] To: Steve Pauly [EMAIL PROTECTED] Subject: Re: portupgrade avr-libc error Date: Mon, 20 Feb 2006 00:31:57 -0500 On Mon, Feb 20, 2006 at 12:27:49AM -0500, Steve Pauly wrote: Kris, I added TRYBROKEN= yes in the Makefile and ran portupgrade avr-libc (getting further than before) with the following results: install -o root -g wheel -m 444 /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/LICENSE /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/AUTHORS /usr/local/share/doc/avr-libc install: wrong number or types of arguments usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /usr/ports/devel/avr-libc. *** Error code 1 Stop in /usr/ports/devel/avr-libc. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade4660.0 make reinstall egrep: /var/db/pkg/avr-libc-1.2.5,1/+CONTENTS: No such file or directory --- Restoring the old version ** Fix the installation problem and try again. [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 172 packages found (-0 +1) . done] ** Listing the failed packages (*:skipped / !:failed) ! devel/avr-libc (avr-libc-1.2.5,1) (install error) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed As expected pkg_version shows the old libc still there. Looking at this line: install -o root -g wheel -m 444 /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/LICENSE /usr/ports/devel/avr-libc/work/avr-libc-1.4.3/AUTHORS /usr/local/share/doc/avr-libc I notice that that the first two file parameters specify files, while the last one specifies a directory. Is that the issue? Just guessing, newbie here. The other parameters seem okay I guess. What am I doing wrong? Dunno, the port builds fine on a clean system. Is /usr/local/share/doc/avr-libc not a directory on your system? Kris 2.dat -- ___ Play 100s of games for FREE! http://games.mail.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Where should I address fixes for /usr/src/lib/libc/rpc code to?
Hi, Ive been fixing code in /usr/src/lib/libc/rpc and would like to know where I should address my attention (and code fixes) to. Thanks, Damien Miller = Sub UNIX lumen [EMAIL PROTECTED] = -- Aluminium Oxide [EMAIL PROTECTED] -- http://www.fastmail.fm - Access your email from home and the web ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Where should I address fixes for /usr/src/lib/libc/rpc code to?
On Mon, Jan 02, 2006 at 02:14:40PM +1030, Aluminium Oxide wrote: Hi, Ive been fixing code in /usr/src/lib/libc/rpc and would like to know where I should address my attention (and code fixes) to. There's the freebsd-hackers@freebsd.org list, and you can always send-pr(1) your patches at any time. -- Jonathan Chen [EMAIL PROTECTED]Once is dumb luck. Twice is coincidence. Three times and Somebody Is Trying To Tell You Something. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Where should I address fixes for /usr/src/lib/libc/rpc code to?
In the last episode (Jan 02), Aluminium Oxide said: Ive been fixing code in /usr/src/lib/libc/rpc and would like to know where I should address my attention (and code fixes) to. According to src/MAINTAINERS, alfred@ is the go-to guy for rpc code. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Error code 71 on rebuilding libc. FreeBSD 5.4-p6.
Performing a make install in /usr/src/lib/libc, here's the output : # make install install -C -o root -g wheel -m 444 libc.a /usr/lib install: libc.a: No such file or directory *** Error code 71 Stop in /usr/src/lib/libc. Howerer, when I ll for the file /usr/lib/libc.a in the /usr/lib directory, I get : # ll libc.a -r--r--r-- 1 root wheel 1918768 Aug 20 11:53 libc.a So the file is obviously there. There is a possibilty that I'm just being a twit. Any assistance would be greatly appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error code 71 on rebuilding libc. FreeBSD 5.4-p6.
In the last episode (Sep 16), Jordan Freeman said: Performing a make install in /usr/src/lib/libc, here's the output : # make install install -C -o root -g wheel -m 444 libc.a /usr/lib install: libc.a: No such file or directory *** Error code 71 Stop in /usr/src/lib/libc. Howerer, when I ll for the file /usr/lib/libc.a in the /usr/lib directory, I get : # ll libc.a -r--r--r-- 1 root wheel 1918768 Aug 20 11:53 libc.a So the file is obviously there. There is a possibilty that I'm just being a twit. Any assistance would be greatly appreciated. Did you run make first? -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error code 71 on rebuilding libc. FreeBSD 5.4-p6.
Dan Nelson wrote: In the last episode (Sep 16), Jordan Freeman said: Performing a make install in /usr/src/lib/libc, here's the output : # make install install -C -o root -g wheel -m 444 libc.a /usr/lib install: libc.a: No such file or directory *** Error code 71 Stop in /usr/src/lib/libc. Howerer, when I ll for the file /usr/lib/libc.a in the /usr/lib directory, I get : # ll libc.a -r--r--r-- 1 root wheel 1918768 Aug 20 11:53 libc.a So the file is obviously there. There is a possibilty that I'm just being a twit. Any assistance would be greatly appreciated. Did you run make first? Negative libc is compiling as I type this. May I fall on my sword now??? Jordan Freeman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Linking standalone NASM binary with libc
On Tue, Aug 30, 2005 at 02:11:09PM +0300, Giorgos Keramidas wrote: : I'm sure others can think of more points in support or linking to libc : and against linking to it :-) Most of what I want to do is low-level encryption... like copy protection routines. I love those. So who needs libc for that? ;-) Jonathon McKitrick -- Hoppiness is a good beer. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Linking standalone NASM binary with libc
On 2005-08-30 04:29, Jonathon McKitrick [EMAIL PROTECTED] wrote: I'm doing some experimentation with assembly code based on the int80h.org tutorials. But since I am going to use malloc and some other functions, I need to make my code link with libc rather than stand totally on its own. ld -s -o foo foo.o -lc leaves 'environ' and '__progname' undefined. What is the correct way to link standalone asm code with needed libraries? That depends on what the ``standalone'' code contains. If your foo.o object file defines a 'main' function, then you can just use cc(1): % tesla:/tmp/foo$ cat -n foo.asm % 1 global main % 2 main: % 3 mov eax,1 ; exit() syscall % 4 mov ebx,1 ; exit code % 5 int 0x80; trap into kernel % tesla:/tmp/foo$ nasm -f elf -o foo.o foo.asm == % tesla:/tmp/foo$ cc -o foo foo.o % tesla:/tmp/foo$ ./foo % tesla:/tmp/foo$ echo $? % 1 % tesla:/tmp/foo$ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Linking standalone NASM binary with libc
On Tue, Aug 30, 2005 at 01:37:02PM +0300, Giorgos Keramidas wrote: : On 2005-08-30 04:29, Jonathon McKitrick [EMAIL PROTECTED] wrote: : : I'm doing some experimentation with assembly code based on the int80h.org : tutorials. But since I am going to use malloc and some other functions, : I need to make my code link with libc rather than stand totally on its own. : : ld -s -o foo foo.o -lc : : leaves 'environ' and '__progname' undefined. What is the correct way to link : standalone asm code with needed libraries? : : That depends on what the ``standalone'' code contains. If your foo.o : object file defines a 'main' function, then you can just use cc(1): This is the method I've been using until now. And maybe it's the best one. I was just wondering, though, if I want to write an app that is linked to libc, but doesn't have 'main', and has '_start' instead, and where I want to use ld directly rather than indirectly through cc to link. Jonathon McKitrick -- Hoppiness is a good beer. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Linking standalone NASM binary with libc
On 2005-08-30 11:43, Jonathon McKitrick [EMAIL PROTECTED] wrote: On Tue, Aug 30, 2005 at 01:37:02PM +0300, Giorgos Keramidas wrote: On 2005-08-30 04:29, Jonathon McKitrick [EMAIL PROTECTED] wrote: I'm doing some experimentation with assembly code based on the int80h.org tutorials. But since I am going to use malloc and some other functions, I need to make my code link with libc rather than stand totally on its own. ld -s -o foo foo.o -lc leaves 'environ' and '__progname' undefined. What is the correct way to link standalone asm code with needed libraries? That depends on what the ``standalone'' code contains. If your foo.o object file defines a 'main' function, then you can just use cc(1): This is the method I've been using until now. And maybe it's the best one. I was just wondering, though, if I want to write an app that is linked to libc, but doesn't have 'main', and has '_start' instead, and where I want to use ld directly rather than indirectly through cc to link. That's up to you, really. Linking to the libc library has both good and bad points. 1) Good - You don't need to reinvent the wheel as far as program startup, cleanup and other useful bits are concerned. - Since the C library has setup up things for you, you can call all the known functions that libc or other libraries that use the same calling conventions support (i.e. any library available on your FreeBSD system). 2) Bad - The extra bloat of the C startup/cleanup code. - When you call into C functions you should follow the C calling conventions, otherwise the called library functions may break in bad ways. I'm sure others can think of more points in support or linking to libc and against linking to it :-) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Linking standalone NASM binary with libc
Hi all, I'm doing some experimentation with assembly code based on the int80h.org tutorials. But since I am going to use malloc and some other functions, I need to make my code link with libc rather than stand totally on its own. ld -s -o foo foo.o -lc leaves 'environ' and '__progname' undefined. What is the correct way to link standalone asm code with needed libraries? jm -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
libc
Lo all, Is there anywhere that I can see what has changed from FreeBSD 4.11 to FreeBSD 5.x, in regards to libc ? We are getting major errors and core dumps from one of our applications which runs flawlessly on 4.x, but just dumps on 5.x, complaining about __cxa_finalize () from /lib/libc.so.5 (FreeBSD 5.4-STABLE)... Would be good if someone can give some hints or pointers to debug this... Thanks allot, Chris. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libc
On Thu, Jun 23, 2005 at 12:39:11PM +0200, Chris Knipe wrote: Lo all, Is there anywhere that I can see what has changed from FreeBSD 4.11 to FreeBSD 5.x, in regards to libc ? The CVS logs are public, e.g. http://cvsweb.freebsd.org/, but there are literally thousands of changes. Kris pgprIGyEfnh9P.pgp Description: PGP signature
avr-libc 5.2.1
Hi! Has anybody an idea where I can fetch: avr-libc-2003.09.09.tar.bz2 or a package for 5.2.1? I have installed avrdude, avr-gcc via pkg_add but I'm not successfull with the libc. make install says: Attempting to fetch from http://people.freebsd.org/~joerg/. fetch: http://people.freebsd.org/~joerg/avr-libc-2003.09.09.tar.bz2: Not Found Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/avr-libc-2003.09.09.tar.bz2: File unavailable (e.g., file not found, no access) Where can I download it? Thanks Florian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: avr-libc 5.2.1
On 01/09/05 17:15:40, Florian Hengstberger wrote: Hi! Has anybody an idea where I can fetch: avr-libc-2003.09.09.tar.bz2 or a package for 5.2.1? I have installed avrdude, avr-gcc via pkg_add but I'm not successfull with the libc. make install says: Attempting to fetch from http://people.freebsd.org/~joerg/. fetch: http://people.freebsd.org/~joerg/avr-libc-2003.09.09.tar.bz2: Not Found Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/avr-libc-2003.09.09.tar.bz2: File unavailable (e.g., file not found, no access) Where can I download it? Thanks Florian If there are no pkgs then you have to build(cd /usr/ports/devel/avr- libc make install clean). That can be good because you can optimize, but bad if you had to build gnome or kde on a [EMAIL PROTECTED] Most libs I've built are very quick. Someone could build them for you, but it should not be a problem on a modern machine. By the way email the port maintainer, hot off the press: http://savannah.nongnu.org/download/avr-libc/ avr-libc-1.2.0.tar.bz2 01-Jan-2005 16:25 306k ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
linking to libc and libc_r (was Re: Certain 4.10 apps failing to run as root)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here's an update...
On Thu, 10 Jun 2004 09:12:33 -0600 Anthony Chavez [EMAIL PROTECTED] wrote:
I think that Kris has been swallowed up by other efforts at the moment,
so I'm moving this to the freebsd-stable list, where it's probably more
relevant anyhow.
Actually, this particular machine is actually running RELENG_4_10. My
bad. So I'm posting this back to -questions. :-)
On Thu, 03 Jun 2004 01:35:33 -0600 Anthony Chavez [EMAIL PROTECTED] wrote:
I just upgraded one of my machines to 4.10-STABLE from 4.9-STABLE and
s/0-STABLE/0-RELEASE/
certain binaries (such as vim or vipw) when run as root (either with
sudo or su -) freeze up with rcmdsh: unknown user: followed by a bunch
of garbage.
Any thoughts on what could be causing this?
On Thu, 03 Jun 2004 07:22:09 -0600 Anthony Chavez [EMAIL PROTECTED] wrote:
On Thu, 3 Jun 2004 01:27:57 -0700 Kris Kennaway [EMAIL PROTECTED] wrote:
I've only seen this when something incorrectly links to both libc and
libc_r. Neither of those four binaries should be linked to libc_r at
all though. Can you confirm with ldd(1)?
I have successfully worked around the problem by passing -DLITE to make
when building editors/vim. When I remove -DLITE, the error resurfaces.
The following binaries remain affected (there are others, but they are
irrelevant to vim):
/usr/X11R6/bin/glxinfo:
libc_r.so.4 = /usr/lib/libc_r.so.4 (0x28221000)
libc.so.4 = /usr/lib/libc.so.4 (0x2831e000)
/usr/X11R6/bin/glxgears:
libc_r.so.4 = /usr/lib/libc_r.so.4 (0x281ac000)
libc.so.4 = /usr/lib/libc.so.4 (0x28264000)
What is causing this? My first suspicion is ccache. Could it be that I
have set the following variables in /etc/make.conf?
CC=/usr/local/bin/cc
CPP=/usr/local/bin/cpp
CXX=/usr/local/bin/c++
( /usr/local/bin/c{c,pp,++} are symlinked to /usr/local/bin/ccache. )
Apart from that, the only difference between the system in question and
a stock FreeBSD installation is the following MARK_ARGS pair in
/usr/local/etc/pkgtools.conf:
'editors/vim' = '-DLITE -DWITH_CSCOPE -DWITH_PERL -DWITH_PYTHON -DWITH_RUBY
-DWITH_TCL'
- --
Anthony Chavez http://www.anthonychavez.org/
mailto:[EMAIL PROTECTED]jabber:[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFA9KG1bZTbIaRBRXERAvYRAJ9Q+3AcEYJLB1iYSoSqWZM/ZMfxkACfXKeT
WTypK5pincbgv/4DyQ0abDU=
=FEw9
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
nasm, ld, libc, and **environ
Hi all. I am trying to learn asm with NASM on a FreeBSD system. I really need to debug my programs while I learn, so I want to use printf. This is what I am using to assemble and link: nasm -f elf use_printf.asm ld -o use_printf use_printf.asm -lc but then when I run the program: $./use_printf /usr/libexec/ld-elf.so.1: /lib/libc.so.5: Undefined symbol environ If I try to use static linking, I get this: $ld -static -o use_printf use_printf.asm -lc /usr/lib/libc.a(getenv.o): In function `getenv': getenv.o(.text+0x19): undefined reference to `environ' getenv.o(.text+0x29): undefined reference to `environ' getenv.o(.text+0x63): undefined reference to `environ' /usr/lib/libc.a(getenv.o): In function `__findenv': getenv.o(.text+0xd5): undefined reference to `environ' getenv.o(.text+0xe2): undefined reference to `environ' /usr/lib/libc.a(getenv.o)(.text+0x113): more undefined references to `environ' follow /usr/lib/libc.a(getprogname.o): In function `_getprogname': getprogname.o(.text+0x4): undefined reference to `__progname' Can somebody see where I am going wrong? This is kindof holding me back. I added the 'extern environ' and 'extern __progname' beause I get this otherwise: (when NOT using -static) /usr/lib/libc.so: undefined reference to `environ' /usr/lib/libc.so: undefined reference to `__progname' Here's what I have: ;; BEGIN CODE extern printf extern environ extern __progname section .data mesgdb 'the number is %d\n',0 mesglen equ $-mesg errormesg db 'libc error',0ah,0 errormesglenequ $-errormesg newline db 10 number dw 0x10 kernel: int 80h ret align 4 section .text global _start _start: ; call printf from libc push dword number push dword mesg call printf ; error if eax 1 ( we should have wrote some chars ) cmp eax , 0x1 jl .error ; use write() system call to print message pushdword mesglen pushdword mesg pushdword 0x1 ; stdout mov eax , 0x4 ; 4 == write system call callkernel ; output a newline pushdword 1 pushdword newline pushdword 0x1 mov eax , 0x4 callkernel mov eax , 0x1 ; exit syscall number push dword 0x0 ; exit status call kernel .error: push dword errormesglen push dword errormesg push dword 0x1 mov eax , 0x4 callkernel mov eax , 0x1 pushdword 0xff callkernel END CODE ;;; Any suggestions will be greatly appreciated. Thanks -Adam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld: ENCODING GB18030 is not supported by libc
# [EMAIL PROTECTED] / 2004-01-03 13:18:58 -0500: Roman Neuhauser [EMAIL PROTECTED] writes: I just got this failure on a FreeBSD freepuppy.bellavista.cz 4.8-STABLE FreeBSD 4.8-STABLE #3: Tue Aug 26 12:34:53 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FREEPUPPY2_5 i386 in a buildworld of freshly updated /usr/src. UPDATING, marc.theaimsgroup.com, and google are quiet about the message. what's up? You don't mention what you cvsup'd *to*, but it may not matter... [EMAIL PROTECTED] /usr/src 1029:1 sudo make update -- Running /usr/local/bin/cvsup -- Parsing supfile /usr/local/etc/cvsup/supfiles/standard-supfile Connecting to cvsup.cz.FreeBSD.org Connected to cvsup.cz.FreeBSD.org Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running Updating collection src-all/cvs ^CCleaning up ... Interrupted [EMAIL PROTECTED] /usr/src 1030:130 grep tag= /usr/local/etc/cvsup/supfiles/standard-supfile *default release=cvs tag=RELENG_4 Did you run mergemaster -p? Preferably one built from the new sources? not before now. cvsupped again, ran mergemaster -p (nothing special, just some variables in /etc/make.conf), got the same failure. -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld: ENCODING GB18030 is not supported by libc
Roman Neuhauser [EMAIL PROTECTED] writes: I just got this failure on a FreeBSD freepuppy.bellavista.cz 4.8-STABLE FreeBSD 4.8-STABLE #3: Tue Aug 26 12:34:53 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FREEPUPPY2_5 i386 in a buildworld of freshly updated /usr/src. UPDATING, marc.theaimsgroup.com, and google are quiet about the message. what's up? You don't mention what you cvsup'd *to*, but it may not matter... Did you run mergemaster -p? Preferably one built from the new sources? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
buildworld: ENCODING GB18030 is not supported by libc
I just got this failure on a FreeBSD freepuppy.bellavista.cz 4.8-STABLE FreeBSD 4.8-STABLE #3: Tue Aug 26 12:34:53 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FREEPUPPY2_5 i386 in a buildworld of freshly updated /usr/src. UPDATING, marc.theaimsgroup.com, and google are quiet about the message. what's up? mklocale -o zh_CN.GB18030.out /usr/src/share/mklocale/zh_CN.GB18030.src ENCODING GB18030 is not supported by libc *** Error code 1 Stop in /usr/src/share/mklocale. *** Error code 1 Stop in /usr/src/share. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kde + libc
Hi! Unfortunatelly I am really new with FBSD... so, I installed a 4.7 and upgradet with cvsup to 4.9 after this compiled the base system.. the X server and the KDE 3.1.4. There were some problem during the compile of KDE, and cause of time I installed from binary... Now, If I wanna use any Save/As / Open Dialog box, and type to the filename the application segfaults, and here is the output. (no debugging symbols found)...0x28f24900 in __sys_poll () from /usr/lib/libc_r.so.4 #0 0x28f24900 in __sys_poll () from /usr/lib/libc_r.so.4 #1 0x28f23e4c in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.4 #2 0x28f23811 in _thread_kern_scheduler () from /usr/lib/libc_r.so.4 #3 0x0 in ?? () What should I do ? I am not on the list, so please to private. thanks, woodi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
libc (?)
G'day I've just installed gimp, via the 5.1 distfiles, and get the following error message; [EMAIL PROTECTED]:~] /usr/libexec/ld-elf.so.1: Shared object libc.so.5 not found How would I fix this? - what do I compile etc that will remove this error message? I did a buildworld a while ago to 4.8 stable, and ever since then I've received this error message (ie, amavis doesn't work anymore :-( Any suggestions, or pointers in the right direction would be greatly appreciated :-) regards james ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libc (?)
On Wed, 2 Jul 2003 23:46:16 +0930 james [EMAIL PROTECTED] wrote: Hi, [EMAIL PROTECTED]:~] /usr/libexec/ld-elf.so.1: Shared object libc.so.5 not found How would I fix this? - what do I compile etc that will remove this error message? Sounds like you've installed a 5.x package on a 4.x system. You cannot do that. I did a buildworld a while ago to 4.8 stable, and ever since then I've received this error message (ie, amavis doesn't work anymore :-( Are you installing packages for -CURRENT? Using ports? If a program is asking for libc.so.5 it means it was compiled for 5.x. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] EnergyHQ :: http://www.energyhq.tk Tired of Spam? - http://www.trustic.com pgp0.pgp Description: PGP signature
Re: libc (?)
G'day Probably a really stupid question - but is there a compatability port of some sort for 4.x systems so we can run things compiled for 5.x ? :-) regards james On Wed, 2 Jul 2003 16:40:30 +0200, Miguel Mendez wrote On Wed, 2 Jul 2003 23:46:16 +0930 james [EMAIL PROTECTED] wrote: Hi, [EMAIL PROTECTED]:~] /usr/libexec/ld-elf.so.1: Shared object libc.so.5 not found How would I fix this? - what do I compile etc that will remove this error message? Sounds like you've installed a 5.x package on a 4.x system. You cannot do that. I did a buildworld a while ago to 4.8 stable, and ever since then I've received this error message (ie, amavis doesn't work anymore :-( Are you installing packages for -CURRENT? Using ports? If a program is asking for libc.so.5 it means it was compiled for 5.x. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] EnergyHQ :: http://www.energyhq.tk Tired of Spam? - http://www.trustic.com -- Open WebMail Project (http://openwebmail.org) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libc (?)
Probably a really stupid question - but is there a compatability port of some sort for 4.x systems so we can run things compiled for 5.x ? :-) No, but you can go the other way around. You MIGHT be able to use the 5.x libc directly on 4.x, but I wouldn't recommend it. Ken ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libc (?)
On Thu, 3 Jul 2003 00:16:59 +0930 james [EMAIL PROTECTED] wrote: Hi, Probably a really stupid question - but is there a compatability port of some sort for 4.x systems so we can run things compiled for 5.x ? :-) I fail to see how that could be useful, even if it worked. You can build ports on your 4.x system, and you can use packages on it too. I recommend you installing portupgrade if you haven't already. The you can use cvsup and portupgrade with the -Pp options to use packages if you don't feel compiling stuff yourself. Note that there's not a specific 4.x or 5.x ports tree, ports are ports are ports. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] EnergyHQ :: http://www.energyhq.tk Tired of Spam? - http://www.trustic.com pgp0.pgp Description: PGP signature
Re: libc (?)
On Thu, Jul 03, 2003 at 12:16:59AM +0930, james wrote: G'day Probably a really stupid question - but is there a compatability port of some sort for 4.x systems so we can run things compiled for 5.x ? :-) Why do you think you need this? The same packages are provided for 4.x systems. Kris pgp0.pgp Description: PGP signature
Re: libc (?)
No you can't - it relies on the 5.1 kernel. OK, well I wasn't sure how much things had changed as far as the ABI goes, so I didn't want to rule it out. Ken ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Is this a libc bug ? (gethostbyaddr)
Why does the program below produce radically different results when
linked either (a) with just the libc on FreeBSD 4.7 or else (b) with
the BIND library (libbind.a) from the ISC 8.x.x BIND release, and then
with libc?
Is FreeBSD's gethostbyaddr(3) mishandling the classless in-addr.arpa
delegation in the case of 62.23.166.218 ?
==
#include stdio.h
#include sys/types.h
#include sys/socket.h
#include netinet/in.h
#include arpa/inet.h
#include netdb.h
int
main (void)
{
auto struct in_addr addr;
register struct hostent const *hp;
inet_aton (62.23.166.218, addr);
hp = gethostbyaddr ((char const *)addr, sizeof addr, AF_INET);
if (hp)
printf (%s\n, hp-h_name);
else
printf (No rDNS for %s\n, inet_ntoa (addr));
return 0;
}
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libc tests
On Thu, Mar 06, 2003 at 02:12:06PM -0700, Quinlan, Gerald F wrote: We are looking to acquire or develop the capability to test for proper or expected results for each LIBC function. Your help is appreciated. FreeBSD doesn't include anything comprehensive, except for a few regression tests for miscellaneous parts of the system in /usr/src/tools/regression/. The nearest thing to what you're asking for would be a compliance testing suite for one of the UNIX standards (except FreeBSD may not pass every test). Good luck, Kris pgp0.pgp Description: PGP signature
libc tests
We have acquired a copy of Version 4.7 of freeBSD on CD-ROM and are searching for a way to test the libc functions. The LSB-VSX test suite from The Open Group does not appear to meet our needs. Do you have any other suggestions? Thanks for your help. Gerry Quinlan SNL Department 9224 Scalable Systems Integration Phone 505-844-6568 Fax 505-845-7442 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: libc tests
On Thu, Mar 06, 2003 at 10:50:32AM -0700, Quinlan, Gerald F wrote: We have acquired a copy of Version 4.7 of freeBSD on CD-ROM and are searching for a way to test the libc functions. The LSB-VSX test suite from The Open Group does not appear to meet our needs. Do you have any other suggestions? Thanks for your help. What kind of tests are you hoping to perform? Kris pgp0.pgp Description: PGP signature
RE: libc tests
We are looking to acquire or develop the capability to test for proper or expected results for each LIBC function. Your help is appreciated. Gerry Quinlan SNL Department 9224 Scalable Systems Integration Phone 505-844-6568 Fax 505-845-7442 -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2003 12:01 PM To: Quinlan, Gerald F Cc: '[EMAIL PROTECTED]'; Kelly, Suzanne M Subject: Re: libc tests On Thu, Mar 06, 2003 at 10:50:32AM -0700, Quinlan, Gerald F wrote: We have acquired a copy of Version 4.7 of freeBSD on CD-ROM and are searching for a way to test the libc functions. The LSB-VSX test suite from The Open Group does not appear to meet our needs. Do you have any other suggestions? Thanks for your help. What kind of tests are you hoping to perform? Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: glibc vs BSD libc
when making such assertions it helps to be actually correct. while it is true that *any* old binary may require COMPAT_XX options in the kernel, netbsd supports binaries back to 386bsd for i386, with shorter periods of backwards compat for the newer plaforms. i have personally run 386bsd binaries on netbsd 1.5/i386. i just downloaded the netbsd/sparc 1.0 /bin/sh and: i think you will find that netbsd cares _a whole lot_ about binary compatibility. to claim otherwise is simply fallacy. Are you sure that running such old binaries doesn't require to have any COMPAT_ option? I remember a recommendation on current-users that if you upgrade your kernel before your userland, you should always compile the COMPAT_xxx option for your previous version. I also vaguely remember failure reports from people who forgot to do this. My statement of not caring about binary compatibility was wrong, sorry. What I wanted to say was that the binary interfaces become incompatible and compatibility is provided via COMPAT_ options in the kernel or by packages containing old versions of librairies. So I really don't think that it's possible to run an old binary against a new libc (at least, the sonames wold probably mismatch). Why would otherwise the compat packages in pkgsrc exist? Please correct me if I am wrong. BTW, I believe there are some programs that search the kernel memory directly for some data. Are ps and netstat examples of this? Can old versions of such programs be successfully used on a new kernel, even if the required COMPAT_ option is present? What about special ioctls, like SCSI commands sent directly from userland? Bye Pavel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
re: glibc vs BSD libc
when making such assertions it helps to be actually correct. while it is true that *any* old binary may require COMPAT_XX options in the kernel, netbsd supports binaries back to 386bsd for i386, with shorter periods of backwards compat for the newer plaforms. i have personally run 386bsd binaries on netbsd 1.5/i386. i just downloaded the netbsd/sparc 1.0 /bin/sh and: i think you will find that netbsd cares _a whole lot_ about binary compatibility. to claim otherwise is simply fallacy. Are you sure that running such old binaries doesn't require to have any COMPAT_ option? I remember a recommendation on current-users that if you upgrade your kernel before your userland, you should always compile the COMPAT_xxx option for your previous version. I also vaguely remember failure reports from people who forgot to do this. i never said that you don't need COMPAT_XXX options. infact, i said is true that *any* old binary may require COMPAT_XX options in the kernel. however, these options are enabled by default so unless you actually take them out this isn't an issue. the advice you have gotten from current-users is good and valid. My statement of not caring about binary compatibility was wrong, sorry. What I wanted to say was that the binary interfaces become incompatible and compatibility is provided via COMPAT_ options in the kernel or by packages containing old versions of librairies. So I really don't think that it's possible to run an old binary against a new libc (at least, the sonames wold probably mismatch). Why would otherwise the compat packages in pkgsrc exist? Please correct me if I am wrong. the compat packages exist to provide missing libraries. the netbsd libc soname has never changed -- it was libc.so.12 when the first ELF port arrived, and it is libc.so.12 today. of course you can not use an ELF libc.so to run an a.out program. that's is what the compat packages provide - a.out libraries so that old programs work. however the a.out dynamic linker *is* provided by the system so given that all relevant libraries are available, dynamic netbsd programs will run back to when shared libraries were first introduced. BTW, I believe there are some programs that search the kernel memory directly for some data. Are ps and netstat examples of this? Can old versions of such programs be successfully used on a new kernel, even if the required COMPAT_ option is present? What about special ioctls, like SCSI commands sent directly from userland? ps(1) from netbsd 1.5 and above will work. programs like netstat and other kmem/libkvm grovellers may or may not work. it all depends on the relevant kernel structures not changing (too much?) kmem grovellers do not count as portable programs -- they do not use published API's to gather info, but assume a particular format about how the kernel stores things. netbsd has been moving away from kmem grovellers in a big way for two main reasons: the binary compat issue, and, most kmem grovellers are set-id to group kmem. removing both of these issues *is* a goal, but as i meantioned above, these sorts of programs don't count for backwards compatibility. for instance, the VM system was completely replaced in netbsd 1.4. no program that tries to grovel the old VM system could possibly work today -- those data structures don't exist and more and in many cases, they don't even have something comparable. SCSI commands sent directly from userland i would expect to work. the interface for doing this doesn't change, and the SCSI spec doesn't change one hopes does this clear it all up? [sorry for being so verbose] .mrg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: glibc vs BSD libc
Hello, some notes about NetBSD libc: it supports nsswitch for a long time, see here: http://netbsd.gw.com/cgi-bin/man-cgi?nsswitch.conf++NetBSD-current Dynamically loaded NSS modules are not supported. To David Brownlee: I doubt NetBSD 1.0 binary could run against a NetBSD 1.6 libc. They don't care much about binary compatibility. You could not even run a statically linked 1.0 app without some COMPAT_ option in the kernel, I think. And, if there are things like funopen(), why do Gnome hackers invent their own APIs like gnome-vfs? Does somebody actually use funopen()? Does it really work? Bye Pavel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: glibc vs BSD libc
On Thu, Jan 23, 2003 at 06:41:27PM +0100, Pavel Cahyna wrote: And, if there are things like funopen(), why do Gnome hackers invent their own APIs like gnome-vfs? Does somebody actually use funopen()? Does it really work? They presumably did it because they thought it would be a good idea. Perhaps they wanted to hide implementation differences between different OSes. Either way, the low-level functions in FreeBSD work just fine. Kris msg16499/pgp0.pgp Description: PGP signature
Re: glibc vs BSD libc
Pavel Cahyna [EMAIL PROTECTED] schrieb am 23.01.03 19:14:41: To David Brownlee: I doubt NetBSD 1.0 binary could run against a NetBSD 1.6 libc. They don't care much about binary compatibility. You could not even run a statically linked 1.0 app without some COMPAT_ option in the kernel, I think. Like in many other OSes, NetBSD switched from a.out to ELF. This has the consequence that You need to add some kind of compatibility mode to support both formats - be it switchable (like in NetBSD or Linux) or not. Michael __ Bequemer und billiger - SMS mit FreeMail verschicken! Mehr Information unter: http://freemail.web.de/features/?mc=021147 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
re: glibc vs BSD libc
To David Brownlee: I doubt NetBSD 1.0 binary could run against a NetBSD 1.6 libc. They don't care much about binary compatibility. You could not even run a statically linked 1.0 app without some COMPAT_ option in the kernel, I think. when making such assertions it helps to be actually correct. while it is true that *any* old binary may require COMPAT_XX options in the kernel, netbsd supports binaries back to 386bsd for i386, with shorter periods of backwards compat for the newer plaforms. i have personally run 386bsd binaries on netbsd 1.5/i386. i just downloaded the netbsd/sparc 1.0 /bin/sh and: russsian-intervention ~ uname -a NetBSD russian-intervention.eterna.com.au 1.6M NetBSD 1.6M (_russian_) #719: Sun Jan 19 00:15:13 EST 2003 [EMAIL PROTECTED]:/var/_russian_ sparc russian-intervention ~ file ./sh-sparc-1.0 ./sh-sparc-1.0: NetBSD/sparc demand paged executable russian-intervention ~ ./sh-sparc-1.0 $ ps PID TT STAT TIME COMMAND 229 p0 Ss+0:04.48 -tcsh 284 p1 Ss 0:02.16 -tcsh 327 p1 TN 178:29.44 systat -w1 vm 14305 p1 S 0:00.07 ./sh-sparc-1.0 14308 p1 R+ 0:00.06 ps 17424 p2 IWs0:02.76 -tcsh 22292 p2 SN+ 12:38.86 top ie, that is a netbsd/sparc machine running a kernel that is only a few days old, and it happily runs the 1.0 /bin/sh. (this is a SMP kernel with the new netbsd kernel-based userthreads implementation as well.) i can not test a dynamic program from 1.0 because i don't have the a.out libraries installed currently and i'm not bandwidth-connected right now to download them... (took long enough for /bin/sh to download!) however, i have in the fairly recent past (in the last year or so) run very old a.out dynamic sparc binaries on each of: - 32 bit sparc - 32 bit sparc64 - 64 bit sparc64 with 32 bit binary support when i was testing that the emulations work as LKM's. i think you will find that netbsd cares _a whole lot_ about binary compatibility. to claim otherwise is simply fallacy. .mrg. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
re: glibc vs BSD libc
They presumably did it because they thought it would be a good idea. Perhaps they wanted to hide implementation differences between different OSes. Either way, the low-level functions in FreeBSD work just fine. FWIW, i just ran man funopen on my netbsd box and it says: HISTORY The funopen() functions first appeared in 4.4BSD. BUGS The funopen() function may not be portable to systems other than BSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: glibc vs BSD libc
On Mon, 20 Jan 2003, Andreas Schuldei wrote: i understood him this way: glibcs *portability* is large, since it is not only portabel over several archs but also over several kernels. bsds libc is less portable (only accross different archs) so its portability is smaller. At a source or a binary level? A NetBSD 1.6 box can run NetBSD 1.0 binaries, complete with their shared libraries. A NetBSD 1.0 binary should even run against a NetBSD 1.6 libc (modulus a.out or ECOFF changes to ELF). -- David Brownlee - CTO Purple Interactive - (0)20 8742 8880 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
glibc vs BSD libc
Hello, I am trying to study the various functionalities supported by glibc Vs presence or absence of those features in BSD libc. This information here is w.r.t BSD libc which is supplied with FreeBSD4.6(on intel) i would like to know if i am missing something or some information is not accurate. Any comments?? thanx Atifa __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com 1. License glibc :LGPL License BSD libc:BSD 2. glibc support for standards: ANSI C(ISO C) POSIX (Pthreads support) SYSTEM V (Eg: Malloc tunable parameter(mallopt) Extensions : Statistics for storage allocation with malloc(mallinfo) _tolower() and _toupper() supported. ) Berkely UNIX (Eg: BSD Signal handling BSD wait Symbolic links Sockets ) BSD libc supports: ANSI C pthreads as per POSIX.1 std Berkely UNIX 3. Portability glibc:Portable to more than one Kernel and hence large BSD libc:Dont attempt to be portable across kernels and hence smaller. 4. Error Reporting facility(Eg:perror,strerror) glibc:Supported BSD libc:Supported 5. Memory Allocation Basic Dynamic memory allocation (malloc () and free()) Changing the size of previously allocated memory(realloc() Allocating and Clearing the memory (calloc()) Allocating aligned memory blocks (memalign() and valloc()) Storage allocation hooks (_malloc_hook, _realloc_ hook) Obstacks(stack like allocation,generally not so much used to malloc) Alloca Reallocating allocator(GNU Extensions (r_alloc,r_alloc_free)) Heap Consistency Checking(GNU Extensions(mcheck,mprobe)) glibc: Supports All of the above BSD libc: Supports all except Storage allocation hooks ,obstacks,reallocating allocator, heap consistancy checking valloc() is now obsolete with current malloc implementation which takes care for alignment on page size or larger allocations. 6. Character Handling (tolower,toascii,etc) glibc: Supported BSD libc: Supported. 7. a)String and array utilities glibc: Supported BSD libc:Supported except a few like strndup() and a few which are glibc specific like stpncpy,stpcpy are not Supported. b)Collation functions (strcoll,strxfrm) glibc: Supported BSD libc: Supported. c)Search Functions (memchr,strchr) glibc: Supported BSD libc: Supports except GNU extensions like memmem() 8. a)Input/Output streams and Buffering: glibc: Supported BSD libc: Supported. b)Line Oriented Input glibc: Supported BSD libc:Supported except GNU extensions like getline() and getdelim() c)Formatted Output (printf,sprintf,asprintf,etc) glibc: Supported BSD libc: Supported except obstack_printf() and obstack_vprintf() d)Extend Syntax of printf template string (GNU extension) glibc: Supported BSD libc: Not Supported. e)Other Streams(like string streams,Obstack streams,etc) glibc: Supported BSD libc: Not Supported. 9. System call support glibc: Supported BSD libc: Supported. 10. Support for Pipes and FIFOs. glibc: Supported BSD libc: Supported. 11. File System Interfaces glibc: Supported BSD libc: Supported Except GNU extensions like getumask() 12. Sockets Support glibc: Supported BSD libc: Supported. 13. Terminal Interfaces (isatty,ttyname,etc). glibc: Supported BSD libc: Supported. 14. Math Library Support for Mathematical computation and trignometric functions. glibc: Supported BSD libc: Supported. 15. Searching and sorting(eg:bsearch,qsort) glibc: Supported BSD libc: Supported. 16. Pattern matching(eg:fnmatch) glibc: Supported BSD libc: Supported. 17. Shell Style word expansion (Eg:wordexp,wordfree) glibc: Supported BSD libc: Not Supported. 18. Date and Time glibc: Supported BSD libc: Supported. 19. Extended Characters glibc: Supported BSD libc: No multi-byte character set functions.Breaks building UTF(Unicode) support in libncurses. 20. Locale and Internationalization glibc: Supported BSD libc:libintl and libiconv provides i18n support.By default libc does not contain lintl. 21. Signal handling glibc: Supported BSD libc: Supported. 22. Process startup and termination Program Arguments (Eg:getopt) Environment variables Program Termination glibc: All Supported BSD libc:Supported.(getopt_long updated from NetBSD) 23. System database and name service switch(NSS) glibc: Supported BSD libc: NSS not supported.Incompatible shadow and password support and ancient utmp. (Problem Solved by writing a library libshadow) 24. User and Group Data base glibc: Supported BSD libc:Supported.Except a few functions like fgetpwent(),fgetpwent_r(),putpwent(), Fgetgrent(),fgetgrent_r(). 25. System Information glibc: Supported BSD libc: utsname() not Supported. 26. System Configuration parameters glibc: Supported BSD libc: Supported. 27. Large file support (fseeko64,ftello64) glibc: Supported BSD libc: Not Supported. 28. Debugging features (mtrace(memory leaks),backtrace,etc) glibc: Supported BSD libc: Not Supported. 29. glibc: Add-on packages Crypt BSD libc:Contains additional libraries
Re: glibc vs BSD libc
In the last episode (Jan 20), Atifa Kheel said: e)Other Streams(like string streams,Obstack streams,etc) glibc: Supported BSD libc: Not Supported. BSD supports funopen() which allows the user to create handles for arbitrary stream types. http://www.freebsd.org/cgi/man.cgi?query=funopen Shell Style word expansion (Eg:wordexp,wordfree) glibc: Supported BSD libc: Not Supported. wordexp/wordfree are in 5.0, so they will probably be backported to 4.* at some point. 23. System database and name service switch(NSS) glibc: Supported BSD libc: NSS not supported.Incompatible shadow and password support and ancient utmp. (Problem Solved by writing a library libshadow) User applications should not need to know about FreeBSD's shadow password style, so that shouldn't really matter. 25. System Information glibc: Supported BSD libc: utsname() not Supported. uname() is the correct function name (the data is returned in a struct utsname), and BSD supports it. 27. Large file support (fseeko64,ftello64) glibc: Supported BSD libc: Not Supported. BSD has supported large files far longer than Linux has. fseeko and ftello are the functions you should use. fseeko64 is sort of redundant :) -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: glibc vs BSD libc
* Neal H. Walfield ([EMAIL PROTECTED]) [030120 19:10]: 3. Portability glibc:Portable to more than one Kernel and hence large BSD libc:Dont attempt to be portable across kernels and hence smaller. I do not see the logic. If you are speaking about lines of code in the distribution, I may agree, however, this does not speak to the size of the generated binary, which seems to me to be what you are referring to. i understood him this way: glibcs *portability* is large, since it is not only portabel over several archs but also over several kernels. bsds libc is less portable (only accross different archs) so its portability is smaller. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: glibc vs BSD libc
On Mon, Jan 20, 2003 at 10:31:31AM -0600, Dan Nelson wrote: System database and name service switch(NSS) glibc: Supported BSD libc: NSS not supported.Incompatible shadow and password support and ancient utmp. (Problem Solved by writing a library libshadow) User applications should not need to know about FreeBSD's shadow password style, so that shouldn't really matter. 5.0 has NSS. Also, while it's obvious you're coming from a Linux background, please note that it's equally valid to consider glibc as the one with the incompatible password file format ;-). What does ancient mean, in technical terms? Kris msg16119/pgp0.pgp Description: PGP signature
Re: glibc vs BSD libc
On Mon, Jan 20, 2003 at 05:05:38AM -0800, Atifa Kheel wrote: Some other comments: glibc support for standards: ANSI C(ISO C) POSIX (Pthreads support) SYSTEM V (Eg: Malloc tunable parameter(mallopt) Extensions : Statistics for storage allocation with malloc(mallinfo) _tolower() and _toupper() supported. If it's an 'extension', then it's not 'standard' and not worth using as a point of comparison. Basically, most of the things you list as not supported by BSD are better stated as being GNU-specific extensions that are non-standard and therefore incompatible with the rest of the world. 19. Extended Characters glibc: Supported BSD libc: No multi-byte character set functions.Breaks building UTF(Unicode) support in libncurses. wide character support is present in 5.0. Kris msg16121/pgp0.pgp Description: PGP signature
BSD libc
Hello, i want use BSD libc on my linux system. i want to know from where i can download the source and if any documentation on this is available,like the features it supports etc?? thanx in advance Atifa __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: BSD libc
In [EMAIL PROTECTED], Atifa Kheel [EMAIL PROTECTED] typed: Hello, i want use BSD libc on my linux system. i want to know from where i can download the source and if any documentation on this is available,like the features it supports etc?? FreeBSD is a complete system, not a collection of projects that are put together by people building distributions. I don't believe you can easily download *just* libc. The documentation is included as man pages in the source tree. It's not clear what the best way to get the soruces is. You can go somewhere like: URL: ftp://ftp2.freebsd.org/pub/FreeBSD/releases/i386/4.7-RELEASE/src/ and get slib.*. Those files can be cat'ed togeter, ungzip'ed and the untarred. You can also try fetching the sources from the CVS server. Be aware that you WILL NOT be able to use standard Linux utilities with the FreeBSD libc. There was a project to tweak the FreeBSD user code - libraries and commands - to run on a Linux kernel. I'm not sure what happened to it. If you google through the FreeBSD mail archives, you can probably find a URL for more information. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
recompile libc with BIND IRS ?
Hi In order to have nss_ldap to work on FreeBSD I've read it would be necessary to recompile the libc with the BIND IRS. Does some guru could explain how to do such thing and does anybody has done this with success ? The goal is to have LDAP auth to work on FreeBSD which is not the case with std configuration. Thanks a lot for any infos. -- Frank Bonnet To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Help! Broken libc!
I believe that one of my machines has a hardware problem that occasionally corrupts disk writes. As luck would have it, I also suspect that my /usr/lib/libc.so.4 became corrupt during my last buildworld a few days ago. I now get 'internal compiler errors' whenever I try to compile any program with g++. I compared the md5 hashes of various system files to those of another 4.7-RC machine I updated at about the same time. The libc.so.4 hash is different, so I suspect it may be the source of my problem. It also appears that replacing this file is somewhat non-trivial. When I attempt to remove the file, I get an Operation not permitted, probably because it's linked to a ton of running programs. Is there even a way to replace this file? -- Christopher Farley www.northernbrewer.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
