I suppose it's obvious by now that I'm learning makefiles as I go, so I apologize for my obtuseness. The below is both my first attempt at correcting the file, and demonstrably wrong.
HDRS =...
Type: Posts; User: lost09; Keyword(s):
I suppose it's obvious by now that I'm learning makefiles as I go, so I apologize for my obtuseness. The below is both my first attempt at correcting the file, and demonstrably wrong.
HDRS =...
Making progress, but the resulting library doesn't seem to be linking correctly. Here's the entire makefile, with your most recent suggestion:
HDRS = $(wildcard *.h)
SRCS = $(filter-out...
But removing "-I $(CFITSIO)" from the CXXFLAGS definition causes the compiler to not recognize any of the fitsfile instructions contained in the cfits library.
No, I don't have libcfitsio.so. To the extent of my knowledge, the library doesn't need to be dynamically linked. I tried this:
CFITSIO=/path/to/cfitsio/libcfitsio.a
LDFLAGS=$(CXXFLAGS)...
Thanks for the response, karlson. Making the first change only:
CFITSIO=/path/to/cfitsio
results in the following:
So, here's to dredging up long-dead threads...
I've experienced the same problem, namely that the compiler isn't able to locate libcfitsio.a. I've been operating under dwhitney67's advice of...
Sometimes running with sudo brings up results, and other times not. So far I can't determine any pattern, but it seems to stop turning up results after an arbitrary period of time. I suspect this is...
Minor update: I reinstalled ndiswrapper-utils-1.9 and ndiswrapper-common. iwlist wlan0 scan once again returns the list of available networks. However, dmesg still claims that ath0 is "not ready",...
Well, this is interesting; for some reason, iwlist wlan0 scan no longer returns any results. I've tried rebooting, restarting the network, and bringing wlan0 down and back up, and nothing seems to...
Whoops, momentary stupidity on my part... I'm using karmic, so I retried the previous with karmic instead of intrepid. It installed successfully. Once again I'm able to see available wireless...
First off, thanks for the response, draperdt. Unfortunately, I'm having trouble installing the necessary modules:
$ sudo aptitude install linux-backports-modules-intrepid-generic
Reading package...
The ath5k driver seems to be functioning again after installing ndiswrapper:
$ lshw -C network
*-network:0
description: Wireless interface
product: AR2413 802.11bg...
Found one step towards a fix, which should have been obvious. For some reason, ndiswrapper wasn't installed. After installing it, I retried a scan:
$ iwlist wlan0 scan
wlan0 No scan results
...
Here's some more info; I seem to be farther away from a solution than before. The system no longer recognizes wlan0 at all:
$ ifconfig wlan0 up
wlan0: ERROR while getting interface flags: No...
Alright, I tried blacklisting ath5k and switching to madwifi. But installation of the madwifi-source fails, claiming that I need to add contrib and non-free archives. I was trying to follow steps...
Ok, I've made some progress. I found the correct driver with lshw:
$ lshw
*-network:0
description: Wireless interface
product: AR2413 802.11bg NIC
...
Here's the output of lsmod:
$ lsmod
Module Size Used by
binfmt_misc 8356 1
ppdev 6688 0
joydev 10240 0
pcmcia ...
Here's to adding to the wealth of wireless troubleshooting threads; hopefully this will at least be of use to others. My ethernet connection works perfectly, but I can't connect to wireless to save...
As the problem seems to lie with the disk and not with Ubuntu or, as I had previously suspected, with my computer, I have marked this thread as "solved". Thanks to all for your assistance.
I tried that, to no avail. Actually, it seems to have made things worse, as now I can no longer get into the terminal.
I had a Suse disc on-hand, and out of desperation installed that. It seems to...
I've yet to try. What do I type-in if I'm able to reach it?
Do I have any options shy of physical replacement?
I suspect it is indeed a hard-drive problem, as the reason I reinstalled in the first place was because my computer committed suicide.
I tried plugging in my external monitor. It illuminates, but...
I reinstalled Gutsy for the second time in the hopes that the error would be remedied. No such happiness.
Anyone? Anyone? Stokes Theorem? Anyone...?
My monitor does not display anything after the BIOS screen. It functions perfectly during live CD. I am using a Toshiba Satellite M40 series laptop with an ATI Radeon graphics card. Does anyone know...