Smalltalk › Cincom › VisualWorks

DLLCC on Mac?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

Stephen Pope

DLLCC on Mac?

Hello all,

I'm trying to update some ancient DLLCC interfaces on an Intel-based Mac running OS X 10.6.

I thought I had read that 64-bit was not supported, so I compiled everything for 32-bit (-arch i386).

When I load the plug-in, I always get the error,

a SystemError(#'generic error','dlopen(/usr/local/lib/portmidi_lite.dylib, 9):
no suitable image found. Did find: /usr/local/lib/portmidi_lite.dylib: can''t map')

Does anyone use DLLCC on Macs that can give me a hint?

...any reply appreciated...

stp

--

Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

pastedGraphic.tiff (3K) Download Attachment

andre

Re: DLLCC on Mac?

Am 14.01.2012 um 06:00 schrieb Stephen Travis Pope:

> When I load the plug-in, I always get the error,
>
> a SystemError(#'generic error','dlopen(/usr/local/lib/portmidi_lite.dylib, 9):
> no suitable image found. Did find: /usr/local/lib/portmidi_lite.dylib: can''t map')

Hi Stephen,

this error may indicate that your are trying to link to a framework/dylib with a different bitness (32/64) than the VM. Or there may be missing dependencies so the dylib does not load.

You should perhaps try and compile the portmidi lib as Universal Binary for 32 and 64 bit to ensure all possible images are available.

Andre

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Stephen Pope

Re: DLLCC on Mac?

Thanks for the advice, Andre (Tausend Dank!),

I tried your suggestion, and compiled the following dynamic libraries,

file /usr/local/lib/*portmidi*

/usr/local/lib/libportmidi.dylib: Mach-O universal binary with 2 architectures
/usr/local/lib/libportmidi.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64
/usr/local/lib/libportmidi.dylib (for architecture i386): Mach-O dynamically linked shared library i386

/usr/local/lib/portmidi_lite.dylib: Mach-O universal binary with 2 architectures
/usr/local/lib/portmidi_lite.dylib (for architecture i386): Mach-O executable i386
/usr/local/lib/portmidi_lite.dylib (for architecture x86_64): Mach-O 64-bit executable x86_64

But I get the same error when loading the library.

The C glue code worked a few versions ago.

Has anything in DLLCC changed?

stp

--

Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com

On Jan 14, 2012, at 1:59 AM, andre wrote:

Am 14.01.2012 um 06:00 schrieb Stephen Travis Pope:

When I load the plug-in, I always get the error,

a SystemError(#'generic error','dlopen(/usr/local/lib/portmidi_lite.dylib, 9):
no suitable image found. Did find: /usr/local/lib/portmidi_lite.dylib: can''t map')

Hi Stephen,

this error may indicate that your are trying to link to a framework/dylib with a different bitness (32/64) than the VM. Or there may be missing dependencies so the dylib does not load.

You should perhaps try and compile the portmidi lib as Universal Binary for 32 and 64 bit to ensure all possible images are available.

Andre

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Stephen Pope

Re: DLLCC on Mac?

Just to be complete, I compiled 64-bit-only versions of the MIDI library and the glue code, and the loader error changed to,

#'generic error','dlopen(/usr/local/lib/portmidi_lite.dylib, 9): no suitable image found.

Did find: /usr/local/lib/portmidi_lite.dylib: mach-o, but wrong architecture')

So it looks like it's expecting a 32-bit library.

stp

Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com

On Jan 14, 2012, at 11:02 AM, Stephen Travis Pope wrote:

Thanks for the advice, Andre (Tausend Dank!),

I tried your suggestion, and compiled the following dynamic libraries,

file /usr/local/lib/*portmidi*

/usr/local/lib/libportmidi.dylib: Mach-O universal binary with 2 architectures
/usr/local/lib/libportmidi.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64
/usr/local/lib/libportmidi.dylib (for architecture i386): Mach-O dynamically linked shared library i386

/usr/local/lib/portmidi_lite.dylib: Mach-O universal binary with 2 architectures
/usr/local/lib/portmidi_lite.dylib (for architecture i386): Mach-O executable i386
/usr/local/lib/portmidi_lite.dylib (for architecture x86_64): Mach-O 64-bit executable x86_64

But I get the same error when loading the library.

The C glue code worked a few versions ago.
Has anything in DLLCC changed?

stp

--

Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com
<pastedGraphic.tiff>

On Jan 14, 2012, at 1:59 AM, andre wrote:

Am 14.01.2012 um 06:00 schrieb Stephen Travis Pope:

When I load the plug-in, I always get the error,

a SystemError(#'generic error','dlopen(/usr/local/lib/portmidi_lite.dylib, 9):
no suitable image found. Did find: /usr/local/lib/portmidi_lite.dylib: can''t map')

Hi Stephen,

this error may indicate that your are trying to link to a framework/dylib with a different bitness (32/64) than the VM. Or there may be missing dependencies so the dylib does not load.

You should perhaps try and compile the portmidi lib as Universal Binary for 32 and 64 bit to ensure all possible images are available.

Andre

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Stephen Pope

Re: DLLCC on Mac?

FYI, here's the Makefile I use for the portmidi glue code - this was known to work with VWNC 7.5.

GCC = gcc

CFLAGS = -I$(DLLCC_SRC) -I/usr/local/include -O2 -g -fno-common -dynamic -DDEBUG_SIREN -arch i386

LINKOPTS = -dynamic --bundle -undefined suppress -flat_namespace -L/usr/local/lib -lgcc -arch i386

# portmidi plug-in

midi: portmidi_lite.c

$(GCC) -c portmidi_lite.c $(CFLAGS)

$(GCC) -o portmidi_lite.dylib portmidi_lite.o $(LINKOPTS) -lportmidi \

/System/Library/Frameworks/CoreMIDI.framework/Versions/Current/CoreMIDI

Does anybody use DLLCC on an Intel-based Mac?

stp

Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com

On Jan 14, 2012, at 11:42 AM, Stephen Travis Pope wrote:

Just to be complete, I compiled 64-bit-only versions of the MIDI library and the glue code, and the loader error changed to,

#'generic error','dlopen(/usr/local/lib/portmidi_lite.dylib, 9): no suitable image found.
Did find: /usr/local/lib/portmidi_lite.dylib: mach-o, but wrong architecture')

So it looks like it's expecting a 32-bit library.

stp

--

Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com
<pastedGraphic.tiff>

On Jan 14, 2012, at 11:02 AM, Stephen Travis Pope wrote:

Thanks for the advice, Andre (Tausend Dank!),

I tried your suggestion, and compiled the following dynamic libraries,

file /usr/local/lib/*portmidi*

/usr/local/lib/libportmidi.dylib: Mach-O universal binary with 2 architectures
/usr/local/lib/libportmidi.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64
/usr/local/lib/libportmidi.dylib (for architecture i386): Mach-O dynamically linked shared library i386

/usr/local/lib/portmidi_lite.dylib: Mach-O universal binary with 2 architectures
/usr/local/lib/portmidi_lite.dylib (for architecture i386): Mach-O executable i386
/usr/local/lib/portmidi_lite.dylib (for architecture x86_64): Mach-O 64-bit executable x86_64

But I get the same error when loading the library.

The C glue code worked a few versions ago.
Has anything in DLLCC changed?

stp

--

Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com
<pastedGraphic.tiff>

On Jan 14, 2012, at 1:59 AM, andre wrote:

Am 14.01.2012 um 06:00 schrieb Stephen Travis Pope:

When I load the plug-in, I always get the error,

a SystemError(#'generic error','dlopen(/usr/local/lib/portmidi_lite.dylib, 9):
no suitable image found. Did find: /usr/local/lib/portmidi_lite.dylib: can''t map')

Hi Stephen,

this error may indicate that your are trying to link to a framework/dylib with a different bitness (32/64) than the VM. Or there may be missing dependencies so the dylib does not load.

You should perhaps try and compile the portmidi lib as Universal Binary for 32 and 64 bit to ensure all possible images are available.

Andre

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Christiaan Nooteboom

Support for the SHA256 with RSA encryption algorithm

We have to deal with certificates which make us of the
SHA256WithRSAEncryption algorithm.
At the moment it seems this is not supported in VW, is there an easy
way of resolving this and will this be supported soon?

Regards,

Christiaan
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

mkobetic

Re: Support for the SHA256 with RSA encryption algorithm

"Christiaan Nooteboom"<[hidden email]> wrote:
> We have to deal with certificates which make us of the
> SHA256WithRSAEncryption algorithm.
> At the moment it seems this is not supported in VW, is there an easy
> way of resolving this and will this be supported soon?

We have support for RSA/SHA-2 based signatures lined up for the upcoming release, unfortunately currently we can't share those updates publicly. However it isn't difficult to retrofit RSA/SHA256 support into older releases either as the necessary algorithms are included already. It's mostly just extending the X509.AlgorithmIdentifier to recognize the corresponding algorithm identifiers and small extension to the RSA implementation (it also has to embed the proper algorithm OID into the signature). It would be feasible to provide it as a patch through official support channels as well.

HTH,

Martin

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Peter Hatch

Re: DLLCC on Mac?

In reply to this post by Stephen Pope

Take a look at the rules for compiling the cptst.so library in src/makefiles/makefile.generic.

I don't know if you have to compile using the same SDK as the VM...

Try something like (using the 10.4 SDK):

GCC = gcc-4.0

CFLAGS = -D_APPLE_C_SOURCE -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -mmacosx-version-min=10.4 -O2 -fsigned-char -g -fno-common -I$(DLLCC_SRC) -fPIC

LINKOPTS = -dynamiclib -flat_namespace -undefined suppress -arch i386 -L/usr/local/lib

Obviously, if you can use a newer SDK than what is used for the VM then

GCC = gcc

CFLAGS = -D_DARWIN_C_SOURCE -D_XOPEN_SOURCE=500 -arch i386 O2 -fsigned-char -g -fno-common -I$(DLLCC_SRC) -fPIC

hth,

pete

On Jan 14, 2012, at 2:29 PM, Stephen Travis Pope wrote:

FYI, here's the Makefile I use for the portmidi glue code - this was known to work with VWNC 7.5.

GCC = gcc

CFLAGS = -I$(DLLCC_SRC) -I/usr/local/include -O2 -g -fno-common -dynamic -DDEBUG_SIREN -arch i386

LINKOPTS = -dynamic --bundle -undefined suppress -flat_namespace -L/usr/local/lib -lgcc -arch i386

# portmidi plug-in

midi: portmidi_lite.c
$(GCC) -c portmidi_lite.c $(CFLAGS)
$(GCC) -o portmidi_lite.dylib portmidi_lite.o $(LINKOPTS) -lportmidi \
/System/Library/Frameworks/CoreMIDI.framework/Versions/Current/CoreMIDI

Does anybody use DLLCC on an Intel-based Mac?

stp

--

Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com
<pastedGraphic.tiff>

On Jan 14, 2012, at 11:42 AM, Stephen Travis Pope wrote:

Just to be complete, I compiled 64-bit-only versions of the MIDI library and the glue code, and the loader error changed to,

#'generic error','dlopen(/usr/local/lib/portmidi_lite.dylib, 9): no suitable image found.
Did find: /usr/local/lib/portmidi_lite.dylib: mach-o, but wrong architecture')

So it looks like it's expecting a 32-bit library.

stp

--

Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com
<pastedGraphic.tiff>

On Jan 14, 2012, at 11:02 AM, Stephen Travis Pope wrote:

Thanks for the advice, Andre (Tausend Dank!),

I tried your suggestion, and compiled the following dynamic libraries,

file /usr/local/lib/*portmidi*

/usr/local/lib/libportmidi.dylib: Mach-O universal binary with 2 architectures
/usr/local/lib/libportmidi.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64
/usr/local/lib/libportmidi.dylib (for architecture i386): Mach-O dynamically linked shared library i386

/usr/local/lib/portmidi_lite.dylib: Mach-O universal binary with 2 architectures
/usr/local/lib/portmidi_lite.dylib (for architecture i386): Mach-O executable i386
/usr/local/lib/portmidi_lite.dylib (for architecture x86_64): Mach-O 64-bit executable x86_64

But I get the same error when loading the library.

The C glue code worked a few versions ago.
Has anything in DLLCC changed?

stp

--

Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com
<pastedGraphic.tiff>

On Jan 14, 2012, at 1:59 AM, andre wrote:

Am 14.01.2012 um 06:00 schrieb Stephen Travis Pope:

When I load the plug-in, I always get the error,

a SystemError(#'generic error','dlopen(/usr/local/lib/portmidi_lite.dylib, 9):
no suitable image found. Did find: /usr/local/lib/portmidi_lite.dylib: can''t map')

Hi Stephen,

this error may indicate that your are trying to link to a framework/dylib with a different bitness (32/64) than the VM. Or there may be missing dependencies so the dylib does not load.

You should perhaps try and compile the portmidi lib as Universal Binary for 32 and 64 bit to ensure all possible images are available.

Andre

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc