Re: linker paths /usr/local/lib
On Mon, Feb 24, 2003 at 09:40:27AM +0100, Miguel Mendez wrote: Being a curious person myself I cvs co'd the OpenPTC thing to try it here. I've tried it on a NetBSD box, but the procedure to build it on FreeBSD should be similar. Hey great, thanks for that! You didn't have to do that :-) I tried your changes and did indeed get further. I also had to hack the Makefile.config (in the x11 dir) to include /usr/local/lib and /usr/local/include. Also, a few of the Makefiles had carriage returns at the end of every line, and that also caused gmake to bork. Oh, I had to change configure in one other spot too to include /usr/local/include. After that it compiled everything! Did all that happen because they were using an older version of autoconf to create the configure script? other things. Hope this helps a bit. Perhaps it would be worth e-mailing the developers and making an offer to help them make a more sane configure script. Yeah I think I'll email them, though I'm a newbie when it comes to autoconf/ automake. I'm about to teach myself though because (a) it's about time I learnt and (2) I need to learn to package up some software I'm working on. :-) Thanks muchly for your help! sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
linker paths /usr/local/lib
Hi,
I'm trying to compile ptc. Actually I'm trying to link against the Hermes
pixel conversion library. With the following (ptc's configure creates this):
char Hermes_ConverterInstance();
int main() {
Hermes_ConverterInstance()
; return 0; }
and the command-line:
gcc test.c -o test -lHermes
I get:
/usr/libexec/elf/ld: cannot find -lHermes
Hermes is installed in /usr/local/lib (from ports). The gcc/ld man pages and
various sources on the web seem to indicate that /usr/local/lib isn't searched
by default. `ldconfig -r' shows hermes in its list, however. Anyway man ld
says that for a native linker on an ELF system, if the file /etc/ld.so.conf
exists, the list of directories found in that file will be searched, so I
added /usr/local/lib to that file (and /usr/X11R6/lib for good measure) however
I still get the error.
Any pointers as to what I'm doing wrong? Should this have gone to -newbies? :D
cheers
sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: linker paths /usr/local/lib
Hi On Sun, Feb 23, 2003 at 04:51:33PM +0100, Miguel Mendez wrote: and the command-line: gcc test.c -o test -lHermes You probably want something like this: cc -o test test.c -L/usr/local/lib -lHermes Yeah that's all well and good for me compiling my own programs, but the OpenPTC `configure' checks for Hermes by writing the test program that I posted and linking with the above line :-) It doesn't put -L/usr/local/lib in. I suppose I can just hack the `configure' script but surely there's a better solution? IIRC, ld.so.conf only affects the runtime dynamic linker, in a similar way LD_LIBRARY_PATH does. Ahh, darn, that's not what the ld man page says :) But it didn't work when I put the paths in ld.so.conf so I guess it's wrong.. Thanks for your suggestions. sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: linker paths /usr/local/lib
The configure scripts usually accept a parameter like `--with-extra-libs=/usr/local/lib' that you could use. You can always invoke configure with the --help option and check for it. Works most of the time. Yeah, OpenPTC doesn't accept that parameter :/ Most of the GNU tools are better documented in the info pages, as they consider man pages legacy. info ld might turn up more detailed info. You know, I've read/heard that many times over the years, but whenever I look at the info page for whatever tool I'm after, it's exactly the same as the man page (in the ld case too). I can't stand info, mostly because I always forget the keys, and the default keys seem completely foreign and wrong to me that it just puts me off using it. man works well enough for me.. :-) Thanks anyway. sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: sound card blocking problem
Hi, On Fri, Feb 21, 2003 at 09:00:29AM -0600, Brian Henning wrote: I noticed that is FBSD4.7 that when i am using the sound device in one process that the system blocks that device so no other processes can use the sound device until that process is killed. I know that in windows 2000 that is not the case, it lets multilple processes have control of the sound device at the same time. Is there a way to make FBSD4.7 have this functionality? Does this question make any sense? Do you mean you get the device busy or whatever the message is? Unfortunately I don't think you can do much about that. If a piece of software opens /dev/dsp when it starts and doesn't close it until it finishes then nothing else will be able to write to /dev/dsp. Have a look at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html for some info on how to set up virtual channels. This is a way of having several dsp devices (/dev/dsp0.x where x is between 0 and some maximum that you specify) that are multiplixed through the one physical dsp device. Then you should set your various pieces of software to use different dsp devices (e.g. xmms might use /dev/dsp0.0, your window manager's sound server might use /dev/dsp0.1, etc). If you've got an SBLive (or probably any modern sound card) they you actually have around 48 hardware channels (i.e. 48 channels similar to the vchans mentioned above, except that they're mixed on the hardware device, freeing up the CPU). Unfortunately I don't think the current SBLive driver for FreeBSD supports utilising more than one hardware channel (current meaning even the one in 5.0). I think the way the OSS and ALSA drivers do it (I can't remember which - one of them does it this way at the very least) is to allow /dev/dsp to be opened multiple times. I'm going to have a look at putting this support in soon (or at least try to understand what's going on in the current driver - maybe it's in there already; I've never done any kernel hacking before). cheers sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
can't mount msdos partition
Hi, Everything was working fine. Then I created a 30gb FAT32 partition (out of 30gb that was sitting there unused) in Windows 2000 on ad0. Previously there were three partitions on ad0, now there are four. Now when I boot back in to FreeBSD (4.7-RELEASE) I can't mount a _different_ partition on ad1 (my second drive): Next free cluster in FSInfo (4294967295) exceeds maxcluster (1230581) msdos: /dev/ad1s3: Invalid argument The 30gb partition is the only thing I've changed. This didn't happen before adding that partition. Any ideas? cheers sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CVSup Tags and release status
Hi, On Thu, Feb 20, 2003 at 09:55:01PM -0500, Travis Troyer wrote: This says that RELENG_4 is for FreeBSD-STABLE and that RELENG_5_0 is used only for security advisories and other seriously critical fixes. Is this still the case now that 5.0 is the current release version? I installed FreeBSD using the 5.0-Release ISO and want the most current, but stable packages, so I'm not sure which tag to use. FreeBSD 5.0-STABLE may not be as stable as you hope :-) Have a read of: http://www.freebsd.org/releases/5.0R/early-adopter.html for details on the FreeBSD release process. Also, I'm trying to install NVidia's geforce driver, which says it is for FreeBSD -STABLE version 4.7 or later. When I try to compile it, it says that This driver does not support FreeBSD 5.0/-CURRENT! If I installed FreeBSD from the 5.0-Release ISO, wouldn't I be running 5.0-Stable and not 5.0-Current? From the above url: FreeBSD 5.0 will be based on the CURRENT branch. This will be the first release from this branch in over two years (the last was FreeBSD 4.0, in March 2000). At some point after the release of FreeBSD 5.0, a ``5-STABLE'' branch will be created in the FreeBSD CVS repository with the branch tag RELENG_5. The past two stable branches (3-STABLE and 4-STABLE) were created immediately after their respective ``dot-oh'' releases (3.0 and 4.0, respectively). In hindsight, this practice did not give sufficient time for either CURRENT or the new STABLE branches to stabilize after the new branches were created. Therefore, the release engineering team will only create the 5-STABLE branch in the CVS repository after they have found a relatively stable state to use as its basis. It is likely that there will be multiple releases in the 5.X series before this happens; we estimate that the 5-STABLE branch will be created sometime after 5.1-RELEASE or 5.2-RELEASE. cheers sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Root Kits?
Hi, On Thu, Feb 20, 2003 at 07:05:48PM -0800, Silent Secrets wrote: If you could let me know if this is an error on the root kit checker or something else is causing it to look infected, that'd be great. According to posts on this list in previous weeks it's a false positive. cheers sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: CD Recording
Hi, On Wed, Feb 19, 2003 at 12:05:53AM -0500, Justin P. Michel wrote: Is there an easy process for CD duplication using FreeBSD V4.7-R, and a standard IDE/ATAPI burner? I used to use Nero under Windows, but now am lost with dd and burncd, as it seems I have to know beforehand how many tracks are on the CD's, and what types they are. I've recently heard of a program called `arson' for kde. It's supposedly pretty good, but I haven't tried it yet. If you use `cdrecord' you can just give it a list of files to burn. Or you can use `mkisofs' to create an iso image of a directory tree and then just write the image with `cdrecord'. Oh, I just realised that you wanted to duplicate CDs. Well I suppose there's a tool to rip a CD to an iso image; then you can just write it with `cdrecord' as per normal. cheers sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Fw: Creative Audigy soundblaster support
Hi, On Mon, Feb 17, 2003 at 11:58:52AM +0200, Alec wrote: I sent my code to FreeBSD developers and I believe they're considering it and going to include changes in next release. Well done! Do your changes affect the SBLive in any way? I don't have rear speakers working on my 4.7-RELEASE machine and as far as I can tell it's not supported by the current driver. Also the SBLive has (I think) 48 hardware channels; it would be nice if they could be utilised! It's ridiculous to have to use that vchan software mixing thing! cheers sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: syntax problems in /etc/csh.login
Hi, Try this instead: if ( $user == user1 ) then echo hello user1 else if ( $user == user2 ) then echo hello user2 endif You could also do it with a switch: switch ( $user ) case user1: echo hello user1 breaksw case user2: echo hello user2 breaksw endsw $user is a shell built-in variable that holds the user's login name. If you have a lot of users you might want to do it via some username-message mapping mechanism instead of coding a whole bunch of if or case statements. A simple method might be to have a directory under /etc called, say, usermsg and then a file for each user. Then in your csh.login you'd do something like: if ( -r /etc/usermsg/$user ) then cat /etc/usermsg/$user endif cheers sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: emu10k1 patch
Hi, On Thu, Feb 13, 2003 at 11:31:23AM +0100, Antoine Jacoutot wrote: While looking for a way to improve my SBlive sound, I found a patch here: http://groups.google.com/groups?selm=a0ahlh%24itf%241%40FreeBSD.csie.NCTU.edu.tw It is supposed to improve rear speaker output and to add bass+treble mixer. Anyone tried it ? Do you know if it made it into FreeBSD ? I just subscribed to freebsd-multimedia to ask about the emu10k1 driver/SBLive cards. Funny coincidence.. :) I haven't tried that patch. I'm currently running 4.7-RELEASE, and I can't get any sound out of my rear speakers. What are you running/what have you done? I found some old posts by Cameron Grant, the fellow responsible for the emu10k1 driver. In particular there was this one: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=8561+0+archive/2000/freebsd-multimedia/20001112.freebsd-multimedia in which he says that rear speaker support is not yet supported (in 2000). I haven't seen (m)any recent posts from him. Is he still working on the driver? Also, in the pr database there's a report about treble/bass: http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/33013 the gist of it is that most sblive cards use a codec that doesn't support tone controls, and under Windows, tone controls are implemented using filters via the dsp (ack! sounds like a roundabout way to do it..) and that this will not be supported under freebsd for some time (that was written on 30 dec. 2001). Also I remember reading another old email from Cameron Grant that the OSS/ Voxware API (which the pcm interface provides, I think) doesn't have a way to control the rear speaker volume. I wouldn't have thought that that would stop anyone from adding some sort of an extension. Of course, then you'd need mixers to support it, but I don't see that as being a huge problem; a couple of extra #ifdefs wouldn't hurt. Plus maybe the current OSS interface has support for rear speakers already. I might be interested in spearheading improvements in the sblive/other sound card drivers if Cameron Grant isn't around anymore. However I only just installed FreeBSD about a week ago so it'd take me a while to get up to scratch with how everything is implemented. Previously I was using Slackware Linux, so I'm not a total newbie but I have no kernel hacking experience whatsoever. Maybe we should move this discussion over to -multimedia? cheers sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
asdf
subscribe freebsd-questions To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
memory leak problem
Hi,
Woops, sorry about my other asdf spam email.. :-)
This might be a stupid/obvious question but dmalloc is reporting that I have
a memory leak in the following (test) program and I don't know why:
#include stdio.h
#include stdlib.h
#include dmalloc.h
int main(int argc, char **argv)
{
char *c = malloc(10);
strcpy(c, hello);
printf(c=%s\n, c);
free(c);
return 1;
}
dmalloc is installed in my account and I compiled it with:
gcc -g test.c -o test /home/izzo/usr/lib/libdmalloc.a -I/home/izzo/usr/include
I set dmalloc up with:
dmalloc -i 200 -l dmlog high
and at the end of my log file (snipped for brevity) is:
1045066226: 3: total-size count in-use-size count source
1045066226: 3:4096 14096 1 ra=0x280e57ec
1045066226: 3: 10 1 0 0 test.c:7
1045066226: 3:4106 24096 1 Total of 2
1045066226: 3: dumping not-freed pointers changed since 0:
1045066226: 3: not freed: '0x808f008|s1' (4096 bytes) from 'ra=0x280e57ec'
1045066226: 3: total-size count source
1045066226: 3:4096 1 ra=0x280e57ec
1045066226: 3:4096 1 Total of 1
1045066226: 3: unknown memory: 1 pointer, 4096 bytes
Supposedly there is a 4096 byte memory leak. The same program on my Slackware
Linux box reports no leaks. I'm using 4.7-RELEASE. Does anyone have any ideas?
The same program on a friend's 4.5-RELEASE box reports a 1024 byte leak. Is
dmalloc just not FreeBSD-friendly?
Thanks
sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: ftp_proxy syntax
I have never used squid, so this may not work, but the standard for variables is captial letters. try: export FTP_PROXY=squid.sento.com:8080 Ah but the ftp man page says that the *_proxy variables are lowercase. :-) Unless it's a typo.. sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
