I know this has probably often been debated but...
I can't seem to understand the logic for which [import] fails with an error e.g.:
[import]: ERROR: can't load library in monlib
and doesn't for others.
This is on debian with libraries installed from respective packages, and are all in /usr/lib/pd/extra
I may be missing something about the behaviour of [import] but the apparently herratic behaviour makes understanding this hard.
Of course all the libs could be imported by prefixing them such as [osc/packOSC] but then opening the help patch won't find [udpsend] which should then be [iemnet/udpsend] etc. having a single [import iemnet osc] would make much more sense. If it worked.
Lorenzo.
On 14/02/12 16:32, IOhannes m zmölnig wrote:
On 02/14/12 16:17, Lorenzo Sutton wrote:
I know this has probably often been debated but...
I can't seem to understand the logic for which [import] fails with an error e.g.:
[import]: ERROR: can't load library in monlib
isn't this called "moonlib"?
Yes, bad example with a typo. But the error(s) are still there.
Lorenzo.
On Feb 14, 2012, at 10:17 AM, Lorenzo Sutton wrote:
I know this has probably often been debated but...
I can't seem to understand the logic for which [import] fails with an error e.g.:
[import]: ERROR: can't load library in monlib
and doesn't for others.
This is on debian with libraries installed from respective packages, and are all in /usr/lib/pd/extra
I may be missing something about the behaviour of [import] but the apparently herratic behaviour makes understanding this hard.
Of course all the libs could be imported by prefixing them such as [osc/packOSC] but then opening the help patch won't find [udpsend] which should then be [iemnet/udpsend] etc. having a single [import iemnet osc] would make much more sense. If it worked.
You can include all the libraries you want in a single import statement, that's the preferred way to do it, i.e. [import moonlib motex Gem osc]
Now that you've fixed the typo, what's the error?
.hc
"We have nothing to fear from love and commitment." - New York Senator Diane Savino, trying to convince the NY Senate to pass a gay marriage bill
On 14/02/12 18:49, Hans-Christoph Steiner wrote:
On Feb 14, 2012, at 10:17 AM, Lorenzo Sutton wrote:
I know this has probably often been debated but...
I can't seem to understand the logic for which [import] fails with an error e.g.:
[import]: ERROR: can't load library in monlib
and doesn't for others.
This is on debian with libraries installed from respective packages, and are all in /usr/lib/pd/extra
I may be missing something about the behaviour of [import] but the apparently herratic behaviour makes understanding this hard.
Of course all the libs could be imported by prefixing them such as [osc/packOSC] but then opening the help patch won't find [udpsend] which should then be [iemnet/udpsend] etc. having a single [import iemnet osc] would make much more sense. If it worked.
You can include all the libraries you want in a single import statement, that's the preferred way to do it, i.e. [import moonlib motex Gem osc]
Now that you've fixed the typo, what's the error?
As I said this seems to be erratic - at least to me for the moment - so for moonlib specifically e.g.
[import]: ERROR: can't load library in moonlib
Same goes e.g. for osc.
On the other hand if I try to import Gem [import Gem] it works.
One interesting thing i "discovered" for the errors mentioned above is that if I also import (before) libdir they work. Maybe this is the requirement I wasn't understanding about the import process?
[import libdir moonlib osc]
gives: libdir loader 1.9 compiled on Jul 21 2011 at 03:17:08 compiled against Pd version 0.43.0. [import] loaded library: libdir [import] loaded library: moonlib [import] loaded library: osc
Ciao Lorenzo. PS: BTW I wouldn't have started a thread based on a single error with a typo although I can see it might have been misleading ;)
On Feb 15, 2012, at 3:14 AM, Lorenzo Sutton wrote:
On 14/02/12 18:49, Hans-Christoph Steiner wrote:
On Feb 14, 2012, at 10:17 AM, Lorenzo Sutton wrote:
I know this has probably often been debated but...
I can't seem to understand the logic for which [import] fails with an error e.g.:
[import]: ERROR: can't load library in monlib
and doesn't for others.
This is on debian with libraries installed from respective packages, and are all in /usr/lib/pd/extra
I may be missing something about the behaviour of [import] but the apparently herratic behaviour makes understanding this hard.
Of course all the libs could be imported by prefixing them such as [osc/packOSC] but then opening the help patch won't find [udpsend] which should then be [iemnet/udpsend] etc. having a single [import iemnet osc] would make much more sense. If it worked.
You can include all the libraries you want in a single import statement, that's the preferred way to do it, i.e. [import moonlib motex Gem osc]
Now that you've fixed the typo, what's the error?
As I said this seems to be erratic - at least to me for the moment - so for moonlib specifically e.g.
[import]: ERROR: can't load library in moonlib
Same goes e.g. for osc.
On the other hand if I try to import Gem [import Gem] it works.
One interesting thing i "discovered" for the errors mentioned above is that if I also import (before) libdir they work. Maybe this is the requirement I wasn't understanding about the import process?
[import libdir moonlib osc]
gives: libdir loader 1.9 compiled on Jul 21 2011 at 03:17:08 compiled against Pd version 0.43.0. [import] loaded library: libdir [import] loaded library: moonlib [import] loaded library: osc
Ciao Lorenzo. PS: BTW I wouldn't have started a thread based on a single error with a typo although I can see it might have been misleading ;)
Sounds like you are using 0.42 preferences with 0.43. Delete or move your ~/.pdextended file and [import moonlib] should work fine.
.hc
“We must become the change we want to see. - Mahatma Gandhi
On 16/02/12 16:03, Hans-Christoph Steiner wrote:
On Feb 15, 2012, at 3:14 AM, Lorenzo Sutton wrote:
On 14/02/12 18:49, Hans-Christoph Steiner wrote:
On Feb 14, 2012, at 10:17 AM, Lorenzo Sutton wrote:
I know this has probably often been debated but...
I can't seem to understand the logic for which [import] fails with an error e.g.:
[import]: ERROR: can't load library in monlib
and doesn't for others.
This is on debian with libraries installed from respective packages, and are all in /usr/lib/pd/extra
I may be missing something about the behaviour of [import] but the apparently herratic behaviour makes understanding this hard.
Of course all the libs could be imported by prefixing them such as [osc/packOSC] but then opening the help patch won't find [udpsend] which should then be [iemnet/udpsend] etc. having a single [import iemnet osc] would make much more sense. If it worked.
You can include all the libraries you want in a single import statement, that's the preferred way to do it, i.e. [import moonlib motex Gem osc]
Now that you've fixed the typo, what's the error?
As I said this seems to be erratic - at least to me for the moment - so for moonlib specifically e.g.
[import]: ERROR: can't load library in moonlib
Same goes e.g. for osc.
On the other hand if I try to import Gem [import Gem] it works.
One interesting thing i "discovered" for the errors mentioned above is that if I also import (before) libdir they work. Maybe this is the requirement I wasn't understanding about the import process?
[import libdir moonlib osc]
gives: libdir loader 1.9 compiled on Jul 21 2011 at 03:17:08 compiled against Pd version 0.43.0. [import] loaded library: libdir [import] loaded library: moonlib [import] loaded library: osc
Ciao Lorenzo. PS: BTW I wouldn't have started a thread based on a single error with a typo although I can see it might have been misleading ;)
Sounds like you are using 0.42 preferences with 0.43. Delete or move your ~/.pdextended file and [import moonlib] should work fine.
Indeed there was a ~/.pdextended file which I removed, but I still get the error, while it works with [import libdir moonlib]
Lorenzo.
.hc
“We must become the change we want to see. - Mahatma Gandhi
On Feb 17, 2012, at 6:49 AM, Lorenzo Sutton wrote:
On 16/02/12 16:03, Hans-Christoph Steiner wrote:
On Feb 15, 2012, at 3:14 AM, Lorenzo Sutton wrote:
On 14/02/12 18:49, Hans-Christoph Steiner wrote:
On Feb 14, 2012, at 10:17 AM, Lorenzo Sutton wrote:
I know this has probably often been debated but...
I can't seem to understand the logic for which [import] fails with an error e.g.:
[import]: ERROR: can't load library in monlib
and doesn't for others.
This is on debian with libraries installed from respective packages, and are all in /usr/lib/pd/extra
I may be missing something about the behaviour of [import] but the apparently herratic behaviour makes understanding this hard.
Of course all the libs could be imported by prefixing them such as [osc/packOSC] but then opening the help patch won't find [udpsend] which should then be [iemnet/udpsend] etc. having a single [import iemnet osc] would make much more sense. If it worked.
You can include all the libraries you want in a single import statement, that's the preferred way to do it, i.e. [import moonlib motex Gem osc]
Now that you've fixed the typo, what's the error?
As I said this seems to be erratic - at least to me for the moment - so for moonlib specifically e.g.
[import]: ERROR: can't load library in moonlib
Same goes e.g. for osc.
On the other hand if I try to import Gem [import Gem] it works.
One interesting thing i "discovered" for the errors mentioned above is that if I also import (before) libdir they work. Maybe this is the requirement I wasn't understanding about the import process?
[import libdir moonlib osc]
gives: libdir loader 1.9 compiled on Jul 21 2011 at 03:17:08 compiled against Pd version 0.43.0. [import] loaded library: libdir [import] loaded library: moonlib [import] loaded library: osc
Ciao Lorenzo. PS: BTW I wouldn't have started a thread based on a single error with a typo although I can see it might have been misleading ;)
Sounds like you are using 0.42 preferences with 0.43. Delete or move your ~/.pdextended file and [import moonlib] should work fine.
Indeed there was a ~/.pdextended file which I removed, but I still get the error, while it works with [import libdir moonlib]
What about just [import moonlib]?
What does this should you on your machine: ls -l /usr/lib/pd-extended/startup/
.hc
If you are not part of the solution, you are part of the problem.
On 17/02/2012 20:05, Hans-Christoph Steiner wrote:
On Feb 17, 2012, at 6:49 AM, Lorenzo Sutton wrote:
On 16/02/12 16:03, Hans-Christoph Steiner wrote:
On Feb 15, 2012, at 3:14 AM, Lorenzo Sutton wrote:
On 14/02/12 18:49, Hans-Christoph Steiner wrote:
On Feb 14, 2012, at 10:17 AM, Lorenzo Sutton wrote:
I know this has probably often been debated but...
I can't seem to understand the logic for which [import] fails with an error e.g.:
[import]: ERROR: can't load library in monlib
and doesn't for others.
This is on debian with libraries installed from respective packages, and are all in /usr/lib/pd/extra
I may be missing something about the behaviour of [import] but the apparently herratic behaviour makes understanding this hard.
Of course all the libs could be imported by prefixing them such as [osc/packOSC] but then opening the help patch won't find [udpsend] which should then be [iemnet/udpsend] etc. having a single [import iemnet osc] would make much more sense. If it worked.
You can include all the libraries you want in a single import statement, that's the preferred way to do it, i.e. [import moonlib motex Gem osc]
Now that you've fixed the typo, what's the error?
As I said this seems to be erratic - at least to me for the moment - so for moonlib specifically e.g.
[import]: ERROR: can't load library in moonlib
Same goes e.g. for osc.
On the other hand if I try to import Gem [import Gem] it works.
One interesting thing i "discovered" for the errors mentioned above is that if I also import (before) libdir they work. Maybe this is the requirement I wasn't understanding about the import process?
[import libdir moonlib osc]
gives: libdir loader 1.9 compiled on Jul 21 2011 at 03:17:08 compiled against Pd version 0.43.0. [import] loaded library: libdir [import] loaded library: moonlib [import] loaded library: osc
Ciao Lorenzo. PS: BTW I wouldn't have started a thread based on a single error with a typo although I can see it might have been misleading ;)
Sounds like you are using 0.42 preferences with 0.43. Delete or move your ~/.pdextended file and [import moonlib] should work fine.
Indeed there was a ~/.pdextended file which I removed, but I still get the error, while it works with [import libdir moonlib]
What about just [import moonlib]?
It fails with the same error.
What does this should you on your machine: ls -l /usr/lib/pd-extended/startup/
ls: cannot access /usr/lib/pd-extended/startup/: No such file or directory
Lorenzo.
On Feb 17, 2012, at 3:56 PM, Lorenzo Sutton wrote:
On 17/02/2012 20:05, Hans-Christoph Steiner wrote:
On Feb 17, 2012, at 6:49 AM, Lorenzo Sutton wrote:
On 16/02/12 16:03, Hans-Christoph Steiner wrote:
On Feb 15, 2012, at 3:14 AM, Lorenzo Sutton wrote:
On 14/02/12 18:49, Hans-Christoph Steiner wrote:
On Feb 14, 2012, at 10:17 AM, Lorenzo Sutton wrote:
> I know this has probably often been debated but... > > I can't seem to understand the logic for which [import] fails with an error e.g.: > > [import]: ERROR: can't load library in monlib > > and doesn't for others. > > This is on debian with libraries installed from respective packages, and are all in /usr/lib/pd/extra > > I may be missing something about the behaviour of [import] but the apparently herratic behaviour makes understanding this hard. > > Of course all the libs could be imported by prefixing them such as [osc/packOSC] but then opening the help patch won't find [udpsend] which should then be [iemnet/udpsend] etc. having a single [import iemnet osc] would make much more sense. If it worked. You can include all the libraries you want in a single import statement, that's the preferred way to do it, i.e. [import moonlib motex Gem osc]
Now that you've fixed the typo, what's the error?
As I said this seems to be erratic - at least to me for the moment - so for moonlib specifically e.g.
[import]: ERROR: can't load library in moonlib
Same goes e.g. for osc.
On the other hand if I try to import Gem [import Gem] it works.
One interesting thing i "discovered" for the errors mentioned above is that if I also import (before) libdir they work. Maybe this is the requirement I wasn't understanding about the import process?
[import libdir moonlib osc]
gives: libdir loader 1.9 compiled on Jul 21 2011 at 03:17:08 compiled against Pd version 0.43.0. [import] loaded library: libdir [import] loaded library: moonlib [import] loaded library: osc
Ciao Lorenzo. PS: BTW I wouldn't have started a thread based on a single error with a typo although I can see it might have been misleading ;)
Sounds like you are using 0.42 preferences with 0.43. Delete or move your ~/.pdextended file and [import moonlib] should work fine.
Indeed there was a ~/.pdextended file which I removed, but I still get the error, while it works with [import libdir moonlib]
What about just [import moonlib]?
It fails with the same error.
What does this should you on your machine: ls -l /usr/lib/pd-extended/startup/
ls: cannot access /usr/lib/pd-extended/startup/: No such file or directory
That's the problem, in Pd-extended 0.43, the loaders (libdir, pdlua, tclpd) are loaded using the new startup/ folder. Yours doesn't exist, so its not loading anything.
Which version of the Pd-extended package are you using? Where did the build come from?
.hc
Programs should be written for people to read, and only incidentally for machines to execute.
- from Structure and Interpretation of Computer Programs
-
Hans-Christoph Steiner -
IOhannes m zmölnig -
Lorenzo Sutton