Re: [Pharo-users] Using FFI: MessagetNotUnderstood:InterfaceDev class>>fficall:module

2016-04-25 Thread Arnaud
Hi , Thanks Esteban, I have install pharo 5 and another issue appear when working with it. when i create a class and i try to inspect the class am having the following issue: Here is my class: Object subclass: #InterfaceDev instanceVariableNames: 'errbuf' classVariableNames: ''

Re: [Pharo-users] Using FFI: MessagetNotUnderstood:InterfaceDev class>>fficall:module

2016-04-20 Thread Esteban Lorenzano
> On 20 Apr 2016, at 12:34, Esteban Lorenzano wrote: > > >> On 20 Apr 2016, at 10:37, mathias arnaud nkeumo tsombeng >> wrote: >> >> Dear All, >> >> Am try to call a libpcap library using FFI in pharo and am getting the >> following error: >> MessagetNotUnderstood:InterfaceDev class>>ffical

Re: [Pharo-users] Using FFI: MessagetNotUnderstood:InterfaceDev class>>fficall:module

2016-04-20 Thread Esteban Lorenzano
> On 20 Apr 2016, at 10:37, mathias arnaud nkeumo tsombeng > wrote: > > Dear All, > > Am try to call a libpcap library using FFI in pharo and am getting the > following error: > MessagetNotUnderstood:InterfaceDev class>>fficall:module > > Am working with pharo 4 ffiCall:module: is UFFI, then

[Pharo-users] Using FFI: MessagetNotUnderstood:InterfaceDev class>>fficall:module

2016-04-20 Thread mathias arnaud nkeumo tsombeng
Dear All, Am try to call a libpcap library using FFI in pharo and am getting the following error: MessagetNotUnderstood:InterfaceDev class>>fficall:module Am working with pharo 4 also I have issue with pharo 5 on unbuntu after runing the pharo launher i create an image of pharo 5 but when i tr

Re: [Pharo-users] Using FFI

2014-07-11 Thread Annick Fron
Actually the problem was I had forgotten to put the right number of arguments in the Smalltalk method … Too bad … Le 10 juil. 2014 à 11:54, Esteban Lorenzano a écrit : > > On 10 Jul 2014, at 02:32, Andres Valloud > wrote: > >> On 64 bit Windows a long is 32 bits and pointers are 64 bits, so

Re: [Pharo-users] Using FFI

2014-07-10 Thread Esteban Lorenzano
On 10 Jul 2014, at 02:32, Andres Valloud wrote: > On 64 bit Windows a long is 32 bits and pointers are 64 bits, so that type of > replacement is not going to work in the long run… Of course, but let’s take care about that problem when actually become a problem :) Hopefully, for when we final

Re: [Pharo-users] Using FFI

2014-07-09 Thread Andres Valloud
On 64 bit Windows a long is 32 bits and pointers are 64 bits, so that type of replacement is not going to work in the long run... On 7/9/14 8:20 , Esteban Lorenzano wrote: yes, FFI does not handle ** arguments. I always replace it by ulong instead (it is the same, after all) Esteban On 09 Jul

Re: [Pharo-users] Using FFI

2014-07-09 Thread Esteban Lorenzano
yes, FFI does not handle ** arguments. I always replace it by ulong instead (it is the same, after all) Esteban On 09 Jul 2014, at 17:17, Clément Bera wrote: > Hello, > > This bug happen both with the old and new compiler. > > The error tells you that the number of arguments of your smallta

Re: [Pharo-users] Using FFI

2014-07-09 Thread Clément Bera
Hello, This bug happen both with the old and new compiler. The error tells you that the number of arguments of your smalltalk method does not match the number of argument of the C method you want to call (but it seemsthe number of arguments is correct). This works fine: ^self externalCallFai

[Pharo-users] Using FFI

2014-07-09 Thread Annick Fron
Hi, I am trying to use FFI on linux with pharo 3 using version 31 of FFI. I have written the following method : ^self externalCallFailed but when accepting it I get a syntax error « matching number of arguments » Annick Fron

Re: [Pharo-users] Using FFI

2013-12-10 Thread Esteban Lorenzano
Hi Annik, long time without a response to this, I'm sorry. I'm just catching up with this stuff (I'm really full of work this days). The problem here is that FFI does not have the type "int". You need to choose between short, ushort, long and ulong (depending of the real size you need). And you

Re: [Pharo-users] Using FFI

2013-11-09 Thread btc
Hi Annick, I hope you are able to achieve what you are aiming for (I don't have the technical knowledge to help) but as a bystander I must make an observation that I hope will be useful to you. While your response "I have answered I think" could be technically correct if someone wade through

Re: [Pharo-users] Using FFI

2013-11-08 Thread Annick Fron
I have answered I think Envoyé de mon iPod > Le 9 nov. 2013 à 02:01, Stéphane Ducasse a écrit : > > Annick > > You cannot expect people to respond to you if you do not provide > full context + information. > On the long term people will stop to reply to you. > Repeat after me: > which

Re: [Pharo-users] Using FFI

2013-11-08 Thread Stéphane Ducasse
Annick You cannot expect people to respond to you if you do not provide full context + information. On the long term people will stop to reply to you. Repeat after me: which image? which OS version? which vm version? I think that we are pretty nice people but do not forc

Re: [Pharo-users] Using FFI

2013-11-06 Thread Annick Fron
I am using the latest download from version 2 Annick Le 31 oct. 2013 à 18:47, Esteban Lorenzano a écrit : > ok... then we have a problem. > but we need more data... > > which image version are you using? > and which vm version? > > cheers, > Esteban > > On Oct 31, 2013, at 11:24 AM, Annic

Re: [Pharo-users] Using FFI

2013-10-31 Thread Esteban Lorenzano
ok... then we have a problem. but we need more data... which image version are you using? and which vm version? cheers, Esteban On Oct 31, 2013, at 11:24 AM, Annick Fron wrote: > I hâve thé error on Windows > > Envoyé de mon iPod > > Le 31 oct. 2013 à 14:51, Igor Stasenko a écrit : > >

Re: [Pharo-users] Using FFI

2013-10-31 Thread Annick Fron
I hâve thé error on Windows Envoyé de mon iPod > Le 31 oct. 2013 à 14:51, Igor Stasenko a écrit : > > > > >> On 31 October 2013 11:23, Annick Fron wrote: >> Hi Igor >> >> I have done that, but still gets an error, do I need to remove NativeBoost ? >> Annick > > FFI not supported on ARM >

Re: [Pharo-users] Using FFI

2013-10-31 Thread Luc Fabresse
2013/10/31 Clément Bera > Does Alien support ARM ? > no > > How to do FFI on ARM then if NativeBoost and FFI does not support it ? > IMHO you should do a VM plugin easiest and fastest path currently Luc > > > 2013/10/31 Igor Stasenko > >> >> >> >> On 31 October 2013 11:23, Annick Fron wr

Re: [Pharo-users] Using FFI

2013-10-31 Thread Clément Bera
Does Alien support ARM ? How to do FFI on ARM then if NativeBoost and FFI does not support it ? 2013/10/31 Igor Stasenko > > > > On 31 October 2013 11:23, Annick Fron wrote: > >> Hi Igor >> >> I have done that, but still gets an error, do I need to remove >> NativeBoost ? >> Annick >> >> > FF

Re: [Pharo-users] Using FFI

2013-10-31 Thread Igor Stasenko
On 31 October 2013 11:23, Annick Fron wrote: > Hi Igor > > I have done that, but still gets an error, do I need to remove NativeBoost > ? > Annick > > FFI not supported on ARM > Le 30 oct. 2013 à 14:12, Igor Stasenko a écrit : > > AFAIK, it should be in Configurations browser. > Else try this:

Re: [Pharo-users] Using FFI

2013-10-31 Thread Annick Fron
Hi Igor I have done that, but still gets an error, do I need to remove NativeBoost ? Annick Le 30 oct. 2013 à 14:12, Igor Stasenko a écrit : > AFAIK, it should be in Configurations browser. > Else try this: > > Gofer new > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOf

Re: [Pharo-users] Using FFI

2013-10-30 Thread Igor Stasenko
On 30 October 2013 16:11, Esteban Lorenzano wrote: > mmm... but again, AFAIK... Old FFI will not work in ARM. > > yes. but i replied before knowing that its about ARM :) > On Oct 30, 2013, at 10:12 AM, Igor Stasenko wrote: > > AFAIK, it should be in Configurations browser. > Else try this: > >

Re: [Pharo-users] Using FFI

2013-10-30 Thread Esteban Lorenzano
mmm... but again, AFAIK... Old FFI will not work in ARM. On Oct 30, 2013, at 10:12 AM, Igor Stasenko wrote: > AFAIK, it should be in Configurations browser. > Else try this: > > Gofer new > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfFFI'; > load. > (Smalltalk at:

Re: [Pharo-users] Using FFI

2013-10-30 Thread Igor Stasenko
AFAIK, it should be in Configurations browser. Else try this: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfFFI'; load. (Smalltalk at: #ConfigurationOfFFI) project lastVersion load On 30 October 2013 09:41, Annick Fron wrote: > My problem is that the Raspberr

Re: [Pharo-users] Using FFI

2013-10-30 Thread Luc Fabresse
Hi Annick, Probably (others will correct me if I am wrong ;-)) that the easiest is to write a VM plugin, add it in your ARM-based VM and recompile it. Cheers, Luc #Luc 2013/10/30 Esteban Lorenzano > Hi Annick, > > Rapsberry (ARM) does not supports FFI either (current implementation is > x

Re: [Pharo-users] Using FFI

2013-10-30 Thread Esteban Lorenzano
Hi Annick, Rapsberry (ARM) does not supports FFI either (current implementation is x86 architecture). Esteban On Oct 30, 2013, at 5:41 AM, Annick Fron wrote: > My problem is that the Raspberry does not support native boost (as yet !). > Where can I load the old FFI ? > > Le 29 oct. 2013 à

Re: [Pharo-users] Using FFI

2013-10-30 Thread Annick Fron
My problem is that the Raspberry does not support native boost (as yet !). Where can I load the old FFI ? Le 29 oct. 2013 à 16:57, Igor Stasenko a écrit : > > > > On 29 October 2013 16:27, Annick Fron wrote: > Hi > > I want to launch a simple init with the following C signature : > > void

Re: [Pharo-users] Using FFI

2013-10-29 Thread Igor Stasenko
On 29 October 2013 16:27, Annick Fron wrote: > Hi > > I want to launch a simple init with the following C signature : > > void gst_init (int *argc, char **argv[]) > > If I write > > > > I get a Smalltalk syntax error > > Annick Fron > > To use this syntax, you must load old FFI implementation. O

[Pharo-users] Using FFI

2013-10-29 Thread Annick Fron
Hi I want to launch a simple init with the following C signature : void gst_init (int *argc, char **argv[]) If I write I get a Smalltalk syntax error Annick Fron