Autotools, libraries and man pages: oh my!
Hey everyone, So, I have a question. I have Makefile.am, configure.in and a file called dstring.pc.in (for a library of mine called dstring) for a project. It always built fine on Linux. My home is now FreeBSD. This is the first time I've tried to compile/install this library since moving away from Linux. I'm able to use autotools on FreeBSD to generate configure and Makefile.in, and can use gmake to compile and install it. Unfortunately, the man pages are installed to /usr/local/share/man instead of to /usr/local/man, which I thought the tools would've taken care of. Also, even though I see my library was successfully compiled and installed to /usr/local/lib, when I try to compile a program with gcc source.c -ldstring, I get: /usr/bin/ld: cannot find -ldstring Other open source projects I've seen have installed fine on FreeBSD just with the simple configure --prefix=/usr/local make make install. I'm not sure what's wrong with my own setup. Disclaimer: I have no idea what I'm doing :) Does anyone have a stab in the dark that might help me fix these things? I can send any of the three files above if you need to see them. Thanks so much everyone! James ___ 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: Autotools, libraries and man pages: oh my!
On 11/01/12 21:44, James Colannino wrote: [...]I'm able to use autotools on FreeBSD to generate configure and Makefile.in, and can use gmake to compile and install it. Unfortunately, the man pages are installed to /usr/local/share/man instead of to /usr/local/man, which I thought the tools would've taken care of. Also, even though I see my library was successfully compiled and installed to /usr/local/lib, when I try to compile a program with gcc source.c -ldstring, I get: /usr/bin/ld: cannot find -ldstring Update: I can compile against my dstring library by using the following line: gcc source.c -L/usr/local/lib -ldstring. I guess it didn't know to search /usr/local/lib. Still having trouble figuring out how to install the man pages properly, though :( James ___ 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
No color on CUPS
Hey everyone, I hope this is FreeBSD-specific enough for this list... Ever since moving to FreeBSD, I haven't been able to use color on my color laserjet. I've tried selecting just about every color laserjet model from the web interface to CUPS that I can think of, and the only color models available are grayscale and inverted grayscale. I was always able to get color no problem on my Linux box. I know there's something stupid that I'm missing, but I'm not really knowledgeable about CUPS, much less CUPS on FreeBSD. Has anyone else had this problem, and if so, how did you fix it? Thanks so much! James ___ 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
Checking for broken packages (as in linking)
No, I don't mean checking for broken ports :-P In fact, when I Google around for the answer to my question, that's all I can find, which is why I bring my question to the mailing list instead :) Maybe broken ports or broken packages isn't the right term (what should I be searching for instead?) What I want to know is, are there tools that will check the ports I've installed and tell me if any of my packages are linked against libraries that are no longer there? I'm paranoid that at some point, while I'm building and installing updates, I'm going to break something. I've been using FreeBSD for a little while now, but I'm still learning... :) Thanks in advance! James ___ 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: Checking for broken packages (as in linking)
On 11/04/11 23:53, Conrad J. Sabatier wrote: On Fri, 04 Nov 2011 23:27:54 -0700 James Colanninoja...@colannino.org wrote: What I want to know is, are there tools that will check the ports I've installed and tell me if any of my packages are linked against libraries that are no longer there? I'm paranoid that at some point, while I'm building and installing updates, I'm going to break something. The port sysutils/bsdadminscripts includes a tool called pkg_libchk, which does exactly what you're looking for. Perfect. Thanks! I've been using FreeBSD for a little while now, but I'm still learning... :) Thanks in advance! Hey, we're all (even us so-called old-timers) still learning. :-) :) James ___ 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: Checking for broken packages (as in linking)
On 11/05/11 12:43, C. P. Ghost wrote: I'm using the following script (attached). Thanks for the script. By any chance, are you a Gentoo user (or were you at one point)? revdep-rebuild, a part of the gentoolkit, is the first thing I think of when I think about fixing broken packages :) James ___ 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 won't install after Fixit
Hey everyone, I have the FreeBSD DVD (amd64) and, during an install, used the Fixit option (while choosing to mount the DVD as the live filesystem) to load a kernel module. After exiting the fixit shell and attempting a standard install, when it came time to install packages, I got the following error: Error mounting /dev/acd0 on /dist: Input/output error (5) I also noticed that once I've chosen the CDROM/DVD option under Fixit once, I can't do it again, and get the same error when I try. It appears that /dev/acd0 can only be mounted once by the installer. Is this a known issue, and if so, is there a way to work around this so that I can load kernel modules before continuing on with the installation? I could remain within the fixit environment and do the entire install manually, but I'd really rather not do that... Thanks! James ___ 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: FreeBSD won't install after Fixit [solved]
On 08/09/11 13:08, James Colannino wrote: Hey everyone, I have the FreeBSD DVD (amd64) and, during an install, used the Fixit option (while choosing to mount the DVD as the live filesystem) to load a kernel module. After exiting the fixit shell and attempting a standard install, when it came time to install packages, I got the following error: Error mounting /dev/acd0 on /dist: Input/output error (5) [...] Ok, so it turns out that the reason for this was that I was using a VM. I tested this on an ordinary system, and when you exit the Fixit prompt, it ejects the disk. This was happening in the VM, only I didn't realize it because the CD-ROM was being emulated. When it came time to mount the disk a second time, the disk wasn't there, and so that's why it was complaining. James ___ 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
FBSD 8.2 and USB Floppies
Hey everyone, I have a FBSD 8.2 install. I've been trying to mount DOS formatted floppy disks via a USB floppy drive, and have been getting the following error every time: cannot mount /dev/da0: invalid argument I was curious to see what would happen if I created a UFS filesystem on the floppy and tried to mount it. So, I issued the following command: newfs /dev/da0 It was successful. I then tried to mount the new filesystem (mount /dev/da0 /mnt), and got the same error: invalid argument. Does FBSD have a problem mounting USB floppy disks? It's not a big deal, as my other USB storage devices seem to work, and as I have an ordinary floppy drive I can try, but that curious part of me wants to know why this isn't working. I can provide dmesg output, if necessary. Thanks! James ___ 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: FBSD 8.2 and USB Floppies
On 07/18/11 11:57, Pegasus Mc Cleaft wrote: On Monday 18 July 2011 19:45:27 James Colannino wrote: newfs /dev/da0 It was successful. I then tried to mount the new filesystem (mount /dev/da0 /mnt), and got the same error: invalid argument. Does FBSD have a problem mounting USB floppy disks? It's not a big deal, as my other USB storage devices seem to work, and as I have an ordinary floppy drive I can try, but that curious part of me wants to know why this isn't working. Have you tried: mount_msdosfs /dev/da0 /mnt Not sure if this would work with a UFS filesystem :) I did try this when the disk was formatted with a DOS filesystem, however, and I still got the same error. James ___ 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
CUPS and Windows Printers
Hey everyone, I've been Googling around, trying to figure out how to see Windows printers via CUPS on FreeBSD, but so far, all I've found are links describing how to share FreeBSD printers with Windows boxes. Can anyone tell me how I can connect to Windows printers via CUPS + Samba so that I can start getting some work done at the office? :) Thanks so much! James ___ 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: CUPS and Windows Printers
On 07/13/11 20:59, Polytropon wrote: Obtained by a google search. :-) I can't give better advice as I'm not a Windows person, and I avoid using CUPS whenever possible (usually by using a network printer that doesn't need all this stuff), and due to lack of experience with MICROS~1 stuff I can't be fully sure that this is what you're searching for. That looks like it might help. Thanks for the link. The only thing that comes to my mind is that this seems to be a command line approach - so in relation of CUPS configuration mainly done through a web interface today, maybe you could also ask this question in a CUPS web forum? That would probably be a good idea as well... :) James ___ 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 Atheros 9285 patch on 8.0-stable
Hey everyone, I have an Asus EEE PC 1005HA, which has an Atheros 9285 wireless chipset. I discovered that Rui Paulo wrote a driver, and put up a patch for the 8.0 stable kernel here: http://people.freebsd.org/~rpaulo/ar9285_stable_8.diff It seems to have worked for some people. After patching and re-compiling my kernel, it did manage to detect the device on my machine, but unfortunately, I'm unable to scan for networks or associate with my network. Here's what happens: The machine boots, and I see the ath0 interface when I run ifconfig. I then run the command 'ifconfig wlan0 create wlandev ath0' and successfully create wlan0. However, when I run the command 'ifconfig wlan0 scan', the command doesn't seem to do anything, and I eventually have to CTRL-C it. Has anybody else had this problem? Is it a known issue? Maybe I'm doing something wrong? It was mentioned that testers were needed for this driver, and I'd love to help out if possible. If anybody wants me to send any additional information, just let me know. Thanks so much everyone! James ___ 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: Modules and Custom Kernels
David Naylor wrote: If you are building custom kernels then you are not that new to FreeBSD ;-) Well, ok, maybe new is a relative term :-P I've had experience installing FreeBSD in the past (I need to be able to do this for work), but haven't done too much else with it. I normally just copy GENERIC and tweak it but there are better ways than this. That's what I'm doing as well. Not at all. Enjoy :-) Thanks for the help! James ___ 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
Modules and Custom Kernels
Hey everyone. Please bear with me as I'm very new to FreeBSD. I've recently started building a custom kernel after having had to apply a patch to enable support for my wireless device (Atheros 9285) in 8.0-RELEASE, and had a quick question about the process in general. According to the documentation, a line with device driver name will cause that driver to be compiled into the kernel. If one of those lines is commented out, does that mean that the driver will still be built, but that it will be installed as a module? I didn't see anything that told me that explicitly in the documentation, but that's the feeling I got from what I read. I just want to make sure that my assumption is correct, and if not, how to make sure that something gets built as a module rather than built directly into the kernel. In all, the process looks relatively painless as long as I'm careful not to make too many changes to the GENERIC config. Hopefully this isn't a dumb question :) I really like FreeBSD so far, and think I'm going to enjoy my new experience quite a bit. Thanks in advance! James ___ 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
