[ardour-users] PKG_CONFIG_PATH?

[jim stockford]

my mistake.
now i see something that looks like a typo--
don't use the  :  character

# the following is wrong
$ export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$ANYTHING
ANYTHING: Undefined variable  # BASH shell error return
# its the colon character that's throwing BASH off, seems to me


$ export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig

should do it. if not,

$ export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig/
$ # note the final  /  character

hope that helps sorry for previous noise




On Oct 25, 2005, at 1:33 PM, dragon fly wrote:

> typing 'set'in the comand line gives out sth about bash
> i am using bash, the confusion was the first suggestion about export
> the second suggestion, using the "=" sign, does not gives out an error
> just nothing really changes running scons after that
> thanx,
> doc
>
>
>> From: jim stockford <jim at well.com>
>> To: Wolfgang Woehl <tito at rumford.de>
>> CC: ardour-users at lists.ardour.org
>> Subject: Re: [ardour-users] PKG_CONFIG_PATH?
>> Date: Tue, 25 Oct 2005 13:25:02 -0700
>>
>>
>> if
>> export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
>> is the command you issued,
>>
>> and if the shell response to that command is
>> $PKG_CONFIG_PATH: undefined variable
>>
>> then you are using the C shell. verify this by typing
>> set
>> on the command line; you should see the variable
>> shell=/bin/tcsh
>> or similar.
>>
>> the command form you've entered is for the BASH shell,
>> not for the C shell. so use the BASH shell.
>>
>>     Beware of loading the BASH shell to run the command,
>> in that if you subsequently terminate the BASH shell,
>> you'll lose the variable; things will be as if you'd never
>> run the command at all.
>>
>>     it is probably a good idea to set the BASH shell as your
>> default shell for the reason that most documentation
>> assumes the BASH shell and presents commands using
>> BASH shell notation.
>>     if you do so, you can use the C shell whenever you
>> like for special purposes (beware the same problem
>> with respect to environment variables: you'll lose them
>> entirely when you terminate the C shell and resume
>> using the BASH shell.
>>
>> -------------
>> assuming your csh prompt is % here's how to load BASH
>> % /bin/bash
>> $  # the dollar sign shows the BASH shell is now running
>>     # as long as you keep using the BASH shell, your commands
>>     # will "take"; just don't terminate the BASH shell until you're
>>     # done with all your work.
>>
>>
>>
>> On Oct 25, 2005, at 1:01 PM, Wolfgang Woehl wrote:
>>
>> > "dragon fly" <perodog at hotmail.com>:
>> >> well i found some .pc files in /usr/lib/pkgconfig/, but trying to
>> >> export that, i get the message: ... not a valid indentifier
>> >
>> > export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
>> >                      ^^^
>> >
>> >
>> > _______________________________________________
>> > ardour-users mailing list
>> > ardour-users at lists.ardour.org
>> > http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
>> >
>>
>> _______________________________________________
>> ardour-users mailing list
>> ardour-users at lists.ardour.org
>> http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
>
>