See attached build log.
(Please do not complain about the need for looking at the build log until you can provide an easy way to open bugs with the correct data picked out of a tinderbox log. Thanks.)
Created attachment 247626 [details]
Created attachment 256515 [details, diff]
Diego, I have tried to modify native/native.build as attached without success, how should the "gcc" invocation look then?
Thanks a lot for your help
Upstream also doesn't know how to solve this :-(
(In reply to comment #3)
> Upstream also doesn't know how to solve this :-(
I would suspect that the environment variables are not passed correctly.
Therefore nant/mono would resolve $(LDFLAGS) as ""
trying to get nant to build for me (using mono-9999) and if successful to attempt to fix this.
Created attachment 259032 [details, diff]
This seems to work much better. Currently the only issue with this is if a user does not have LDFLAGS defined at all (it will error). This should be easily worked around.
by adding -v to the nant call this patch results in this...
[exec] Starting '/bin/bash (-c 'gcc -Wl,--hash-style=gnu,--as-needed -o libikvm-native.so --shared -fPIC `pkg-config --cflags --libs --libs gmodule-2.0` jni.c os.c')' in '/var/tmp/portage/dev-dotnet/ikvm-0.44.0.6-r1/work/ikvm-0.44.0.6/native'
[copy] Copying 1 file to '/var/tmp/portage/dev-dotnet/ikvm-0.44.0.6-r1/work/ikvm-0.44.0.6/bin'.
[copy] Copying '/var/tmp/portage/dev-dotnet/ikvm-0.44.0.6-r1/work/ikvm-0.44.0.6/native/libikvm-native.so' to '/var/tmp/portage/dev-dotnet/ikvm-0.44.0.6-r1/work/ikvm-0.44.0.6/bin/libikvm-native.so'.
Function platform::is-win32 is deprecated. Use the is-windows function instead.
BUILD SUCCEEDED - 0 non-fatal error(s), 1 warning(s)
+*ikvm-0.46.0.1 (10 Sep 2011)
+ 10 Sep 2011; Pacho Ramos <firstname.lastname@example.org> -ikvm-0.44.0.5.ebuild,
+ +ikvm-0.46.0.1.ebuild, +files/ikvm-0.46.0.1-key.patch:
+ Version bump, remove old.
Looks fixed in this version