Wierd compile error with libpthread.a
Hi, Please note to CC replies to [EMAIL PROTECTED] and [EMAIL PROTECTED] I don't follow this list all that regularly - thanks I am having problems compiling a c program under Debian-Potato. I have traced it this far: If I compile any C program, and link in the library /usr/lib/libpthread.a then an executable will be produced, but when executed will simply lock up. I have tried doing this with just the helloworld type Cprogram and it still locks up. If I don't link that archive, then it works fine. CTRL-C will interrupt it. I have tried looking at it with GDB, but I couldn't figure out what it is doing. That is not surprising as I am not very good with gdb. I have upgraded my libc6, and libc6-dev, and gconv-modules to the latest versions. Thanks a million in advance Rupert Brooks More details: The prog that I am trying to compile is a ppp over ethernet prog. It acts as a little pipe to connect the usual pppd to the eth0. I need it because my ADSL provider (Bell Sympatico) is switching to this method in a few days. The source code is a few hundred lines of C. I will provide it to anyone who would like to compile it themselves. Or you can get it from http://ftp.davin.ottawa.on.ca/linux/sympatico/. Unfortunately its totally undocumented and uncommented. But, if you stick a little printf early in the program, and then see if it prints when you run it, that will determine if it is getting past this problem. If someone can produce a working binary out of it, that would solve my problem, at least for now. In the longer term, I'm toying with the idea of adding PPPOE to the PPP daemon. This little prog is supposed to be really inefficient. If anyone is interested let me know. I'm a lazy, lazy man and would rather not have to do it myself.
Re: 2.2.x kernel and PCI eth0 problem - the answer
Thanks Jor-el, I upgraded dhcpcd and netbase and it works like a charm. The fact that 2.2 kernels require an upgrade is documented in the release notes section on www.debian.org. (Yes I am embarrassed - I should have caught that myself) Thanks also to Paul Wade, who also dropped me a helpful note, with other diagnostic techniques. Namaste Rupert B. At 08:02 AM 03/08/99 -0500, Jor-el wrote: -BEGIN PGP SIGNED MESSAGE- Rupert, I assume that you are running Slink. Have to installed the upgrade versions of the packages that are required for your to be running the 2.2.x kernels? I belive the net-tools package is one of the packages that need to be ugraded, so I am not at all surprised to hear that networking is failing for you. There is a URL available somewhere on the Debian website which tells you about the packages that need to be upgraded. Unfortunately, I do not have a URL handy - so you'll have to search. Regards, Jor-el Everywhere I go I'm asked if I think the university stifles writers. My opinion is that they don't stifle enough of them. There's many a bestseller that could have been prevented by a good teacher. -- Flannery O'Connor On Mon, 2 Aug 1999, Rupert Brooks wrote: Hi, I have configed and compiled both the 2.2.10 and 2.2.5 kernels, and my ne2000 clone PCI ethernet card does not work with either. With my 2.0.34 kernel, the card worked fine. The module ne2k-pci loaded without a hitch and dhcpcd configured the ip information flawlessly. ( I use an ADSL connection which requires DHCP to be used to set up the IP address.) I have tried both kernels with NE2000 support compiled in. In this case, the card appears to be recognized on startup, but DHCPCD does not create new files when it runs. DHCPCD does not report any errors either. ifconfig without arguments shows the loopback device. Ifconfig listing all devices lists the eth0 device and it looks ok, but none of the IP information is configured. Note that I have also used dhcpcd eth0 to try and force dhcp to use the ethernet card. If I configure the kernel to use loadable module support for the ethernet card, then the module ne2k-pci won't load. When using insmod to try to load it, it will complain aboutn several symbols not being resolved. From their names they look like the ethernet card hooks in the kernel. After that lengthy description - I have a couple questions Does anyone out there have a ne2000 PCI ethernet card working under a 2.2.x kernel? If so, did you have to do anything wierd to get it to work? I am not sure what is not working, because there have been so few error messages. Can anyone recommend some diagnostic tests? TIA Rupert Brooks -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv iQCVAwUBN6boavrE9j2ZpWNBAQHr7wQAhRVXTfZcyb+oRJegJ/K7BOOT+mS06H8+ Ptmz35+BkgSJddrYScmO/8bxzZHNoinhVDd2KwPfYEnJQFvIf2thP40rqXj4wJA8 w5/AIQJvDaOtxg98g09qquHRH57rbBcyVE0bJCLC+l9qJiYzPjSxmD3RHvOKtZlL P7WQVXUVi0M= =WzBR -END PGP SIGNATURE-
2.2.x kernel and PCI eth0 problem
Hi, I have configed and compiled both the 2.2.10 and 2.2.5 kernels, and my ne2000 clone PCI ethernet card does not work with either. With my 2.0.34 kernel, the card worked fine. The module ne2k-pci loaded without a hitch and dhcpcd configured the ip information flawlessly. ( I use an ADSL connection which requires DHCP to be used to set up the IP address.) I have tried both kernels with NE2000 support compiled in. In this case, the card appears to be recognized on startup, but DHCPCD does not create new files when it runs. DHCPCD does not report any errors either. ifconfig without arguments shows the loopback device. Ifconfig listing all devices lists the eth0 device and it looks ok, but none of the IP information is configured. Note that I have also used dhcpcd eth0 to try and force dhcp to use the ethernet card. If I configure the kernel to use loadable module support for the ethernet card, then the module ne2k-pci won't load. When using insmod to try to load it, it will complain aboutn several symbols not being resolved. From their names they look like the ethernet card hooks in the kernel. After that lengthy description - I have a couple questions Does anyone out there have a ne2000 PCI ethernet card working under a 2.2.x kernel? If so, did you have to do anything wierd to get it to work? I am not sure what is not working, because there have been so few error messages. Can anyone recommend some diagnostic tests? TIA Rupert Brooks
