mkbundle fails on Snow Leopard or Mono 2.4.2.3

[duanew]

Hopefully someone can help.  I had not run this step in awhile.  Since I last ran this I've upgraded to Snow Leopard and Mono version 2.4.2.3. 

I am trying to use mkbundle like this:

> mkbundle -o test.c -oo libtest.a --nomain -c -L System.dll test.dll

OS is: Darwin

Sources: 1 Auto-dependencies: False

   embedding: /Users/dwandless/PixSrc/sandbox/testmkbundle/test.dll

Compiling:

as -o libtest.a temp.s 

temp.s:2:unknown section type: symbol_stubs

temp.s:2:Rest of line ignored. 1st junk character valued 112 (p).

[Fail]

To workaround this I let it fail, then run:

> as -o libtest.a temp.s -arch i386

Which then produces the .a file.  The contents of test.dll are extraordinarily simple.  namespace test { public class test1 { public void func() { } } }, something like that.

Am I missing something?  Is there a better way than having it fail?  Which of course messes up the make system.

Thanks,

Duane

_______________________________________________
Mono-osx mailing list
Mono-osx@...
http://lists.ximian.com/mailman/listinfo/mono-osx

[Laurent Etiemble]

Hello,

I did not noticed problems with mkbundle on Snow Leopard. But, I
already have this kind of error with an assembly containing a space in
its name. I suggest you to take a look at the symbol file to check if
symbol name is not screwed by a forbidden character.

Regards, Laurent Etiemble.

2009/10/21 Duane Wandless <duane@...>:

> Hopefully someone can help.  I had not run this step in awhile.  Since I
> last ran this I've upgraded to Snow Leopard and Mono version 2.4.2.3.
> I am trying to use mkbundle like this:
>> mkbundle -o test.c -oo libtest.a --nomain -c -L System.dll test.dll
> OS is: Darwin
> Sources: 1 Auto-dependencies: False
>    embedding: /Users/dwandless/PixSrc/sandbox/testmkbundle/test.dll
> Compiling:
> as -o libtest.a temp.s
> temp.s:2:unknown section type: symbol_stubs
> temp.s:2:Rest of line ignored. 1st junk character valued 112 (p).
> [Fail]
> To workaround this I let it fail, then run:
>> as -o libtest.a temp.s -arch i386
> Which then produces the .a file.  The contents of test.dll are
> extraordinarily simple.  namespace test { public class test1 { public void
> func() { } } }, something like that.
> Am I missing something?  Is there a better way than having it fail?  Which
> of course messes up the make system.
> Thanks,
> Duane
> _______________________________________________
> Mono-osx mailing list
> Mono-osx@...
> http://lists.ximian.com/mailman/listinfo/mono-osx
>
>

_______________________________________________
Mono-osx mailing list
Mono-osx@...
http://lists.ximian.com/mailman/listinfo/mono-osx

[duanew]

Well I have a workaround.  Luckily mkbundle reads the environment variable AS.  So I added to my login shell:
export AS="as -arch i386"

And now mkbundle works again.  I do not know why `as` is failing.  The `arch` for my system is i386.

Thanks.

On Wed, Oct 21, 2009 at 2:55 AM, Laurent Etiemble <laurent.etiemble@...> wrote:

Hello,

I did not noticed problems with mkbundle on Snow Leopard. But, I
already have this kind of error with an assembly containing a space in
its name. I suggest you to take a look at the symbol file to check if
symbol name is not screwed by a forbidden character.

Regards, Laurent Etiemble.

2009/10/21 Duane Wandless <duane@...>:

> Hopefully someone can help.  I had not run this step in awhile.  Since I
> last ran this I've upgraded to Snow Leopard and Mono version 2.4.2.3.
> I am trying to use mkbundle like this:
>> mkbundle -o test.c -oo libtest.a --nomain -c -L System.dll test.dll
> OS is: Darwin
> Sources: 1 Auto-dependencies: False
>    embedding: /Users/dwandless/PixSrc/sandbox/testmkbundle/test.dll
> Compiling:
> as -o libtest.a temp.s
> temp.s:2:unknown section type: symbol_stubs
> temp.s:2:Rest of line ignored. 1st junk character valued 112 (p).
> [Fail]
> To workaround this I let it fail, then run:
>> as -o libtest.a temp.s -arch i386
> Which then produces the .a file.  The contents of test.dll are
> extraordinarily simple.  namespace test { public class test1 { public void
> func() { } } }, something like that.
> Am I missing something?  Is there a better way than having it fail?  Which
> of course messes up the make system.
> Thanks,
> Duane

> _______________________________________________
> Mono-osx mailing list
> Mono-osx@...
> http://lists.ximian.com/mailman/listinfo/mono-osx
>
>

_______________________________________________
Mono-osx mailing list
Mono-osx@...
http://lists.ximian.com/mailman/listinfo/mono-osx