Re: [Vala] any latest vala binary for windows?

[oyster via vala-list]

I am using win7 64 bits
Mario Daniel Ruiz Saavedra  于2018年9月20日周四 上午8:58写道：
>
> If you're on Windows 10 you can try to use Vala vía WSL
>
> El mié., 19 de sep. de 2018 7:54 PM, oyster via vala-list 
>  escribió:
>>
>> By the way, I also tried to build directly from C code
>> (https://download.gnome.org/sources/vala/0.42/vala-0.42.1.tar.xz)
>> but
>> ```
>> ...
>>
>> c:(.text+0xd2f): undefined reference to `g_type_check_instance_cast'
>> ../codegen/.libs/libvalaccodegen.a(valaccodecontrolflowmodule.o):valaccodecontrolflowmodule.c:(.text+0x15a5):
>> undefined reference to `g_type_check_instance_cast'
>> ../codegen/.libs/libvalaccodegen.a(valaccodecontrolflowmodule.o):valaccodecontrolflowmodule.c:(.text+0x231d):
>> undefined reference to `g_type_register_static'
>>
>> collect2.exe: error: ld returned 1 exit status
>> make[3]: *** [Makefile:453: valac.exe] Error 1
>> make[3]: Leaving directory '/r/vala-0.42.1/compiler'
>> make[2]: *** [Makefile:367: all] Error 2
>> make[2]: Leaving directory '/r/vala-0.42.1/compiler'
>> make[1]: *** [Makefile:541: all-recursive] Error 1
>> make[1]: Leaving directory '/r/vala-0.42.1'
>> make: *** [Makefile:429: all] Error 2
>>
>> ```
>> oyster  于2018年9月20日周四 上午8:40写道：
>> >
>> > thanks, but this github's build uses installed vala to compile latest
>> > source, in other words, there is no pre-built binary. It installs
>> > mingw-w64-x86_64-vala-0.38.4-1 first, which happens do not work on my
>> > MSYS2(no matter I input `valac`, `valac --help`, `valac test.vala`,
>> > there is no message displays;  `valac test.vala` does not produce any
>> > C file)
>> >
>> > Years ago, vala did not work on my MSYS2. Years later, it fails too.
>> > Maybe vala loves Linux better. Perhaps this is my last time to try
>> > vala before I totally switch to nim for which I can build the latest
>> > version without any problem.
>> >
>> > bye. good luck to vala and me
>> > Al Thomas  于2018年9月20日周四 上午8:01写道：
>> > >
>> > > > On Thursday, 20 September 2018, 00:45:51 BST, oyster via vala-list 
>> > > >  wrote:
>> > > > I give up building from source. So is there any binary vala for
>> > > > windows? On MSYS2, there is an old mingw-w64-x86_64-vala-0.38.4-1
>> > >
>> > > It looks like 0.42.0 is there: 
>> > > https://github.com/Alexpux/MINGW-packages/pull/4350
>> > >
>> > > I'm not a Windows user so can't really help further.
>> > >
>> > > Al
>> > >
>> > >
>> > >
>> ___
>> vala-list mailing list
>> vala-list@gnome.org
>> https://mail.gnome.org/mailman/listinfo/vala-list
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] any latest vala binary for windows?

[oyster via vala-list]

By the way, I also tried to build directly from C code
(https://download.gnome.org/sources/vala/0.42/vala-0.42.1.tar.xz)
but
```
...

c:(.text+0xd2f): undefined reference to `g_type_check_instance_cast'
../codegen/.libs/libvalaccodegen.a(valaccodecontrolflowmodule.o):valaccodecontrolflowmodule.c:(.text+0x15a5):
undefined reference to `g_type_check_instance_cast'
../codegen/.libs/libvalaccodegen.a(valaccodecontrolflowmodule.o):valaccodecontrolflowmodule.c:(.text+0x231d):
undefined reference to `g_type_register_static'

collect2.exe: error: ld returned 1 exit status
make[3]: *** [Makefile:453: valac.exe] Error 1
make[3]: Leaving directory '/r/vala-0.42.1/compiler'
make[2]: *** [Makefile:367: all] Error 2
make[2]: Leaving directory '/r/vala-0.42.1/compiler'
make[1]: *** [Makefile:541: all-recursive] Error 1
make[1]: Leaving directory '/r/vala-0.42.1'
make: *** [Makefile:429: all] Error 2

```
oyster  于2018年9月20日周四 上午8:40写道：
>
> thanks, but this github's build uses installed vala to compile latest
> source, in other words, there is no pre-built binary. It installs
> mingw-w64-x86_64-vala-0.38.4-1 first, which happens do not work on my
> MSYS2(no matter I input `valac`, `valac --help`, `valac test.vala`,
> there is no message displays;  `valac test.vala` does not produce any
> C file)
>
> Years ago, vala did not work on my MSYS2. Years later, it fails too.
> Maybe vala loves Linux better. Perhaps this is my last time to try
> vala before I totally switch to nim for which I can build the latest
> version without any problem.
>
> bye. good luck to vala and me
> Al Thomas  于2018年9月20日周四 上午8:01写道：
> >
> > > On Thursday, 20 September 2018, 00:45:51 BST, oyster via vala-list 
> > >  wrote:
> > > I give up building from source. So is there any binary vala for
> > > windows? On MSYS2, there is an old mingw-w64-x86_64-vala-0.38.4-1
> >
> > It looks like 0.42.0 is there: 
> > https://github.com/Alexpux/MINGW-packages/pull/4350
> >
> > I'm not a Windows user so can't really help further.
> >
> > Al
> >
> >
> >
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] any latest vala binary for windows?

[oyster via vala-list]

thanks, but this github's build uses installed vala to compile latest
source, in other words, there is no pre-built binary. It installs
mingw-w64-x86_64-vala-0.38.4-1 first, which happens do not work on my
MSYS2(no matter I input `valac`, `valac --help`, `valac test.vala`,
there is no message displays;  `valac test.vala` does not produce any
C file)

Years ago, vala did not work on my MSYS2. Years later, it fails too.
Maybe vala loves Linux better. Perhaps this is my last time to try
vala before I totally switch to nim for which I can build the latest
version without any problem.

bye. good luck to vala and me
Al Thomas  于2018年9月20日周四 上午8:01写道：
>
> > On Thursday, 20 September 2018, 00:45:51 BST, oyster via vala-list 
> >  wrote:
> > I give up building from source. So is there any binary vala for
> > windows? On MSYS2, there is an old mingw-w64-x86_64-vala-0.38.4-1
>
> It looks like 0.42.0 is there: 
> https://github.com/Alexpux/MINGW-packages/pull/4350
>
> I'm not a Windows user so can't really help further.
>
> Al
>
>
>
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

[Vala] any latest vala binary for windows?

[oyster via vala-list]

I give up building from source. So is there any binary vala for
windows? On MSYS2, there is an old mingw-w64-x86_64-vala-0.38.4-1

thanks
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

[Vala] bad configure for MSYS2 + MingW 64 on Win7 64 bits

[oyster via vala-list]

bad configure for MSYS2 + MingW 64 on Win7 64 bits
On my MSYS2 + MingW 64, there exists actually /bin/pkg-config.exe, but
the configure tries to find /bin/pkg-config.sh
it will fail without doubt. I have to

```
export GLIB_CFLAGS="$(pkg-config --cflags glib-2.0)"
export GLIB_LIBS="$(pkg-config --libs glib-2.0)"

export GMODULE_CFLAGS="$(pkg-config --cflags gmodule-2.0)"
export GMODULE_LIBS="$(pkg-config --libs gmodule-2.0)"

export LIBGVC_CFLAGS="$(pkg-config --cflags libgvc)"
export LIBGVC_LIBS="$(pkg-config --libs libgvc)"

./configure
./make -j8
```

btw, vala lives in github.com now. but the strange thing is that I did
not find issues part to report bugs
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] The future of Vala

[oyster]

some killer apps may be a good AD.

2016-09-12 0:51 GMT+08:00 Evan Nemerson :
> On Sun, 2016-09-11 at 17:30 +0200, Timm Bäder wrote:
>> On 10.09, Evan Nemerson wrote:
>> >
>> > This is something I've been thinking about lately, too.  We
>> > currently rely on Jürg and Luca's expertise pretty heavily for
>> > development and patch review, and since they are both busy with
>> > other stuff Vala development has slowed down quite a bit.
>> >
>> > Assuming we can't organize financing to pay Jürg and/or Luca
>> > to work on Vala, I think we need to focus on a more decentralized
>> > development approach where we rely more on contributions from
>> > people with less expertise with the Vala internals.
>>
>> I agree that a more decentralized approach would be better, but as I
>> said that can't possibly happen if nobody ever even tries to work
>> with valac internals. Basically, I'm not saying that Jürg or Luca
>> need to even work on valac, but a patch review now and then would
>> already help a lot. And some of those patches are really quite simple
>> and obviously correct, but no review except theirs has any weight.
>
> I'm not trying to say nobody should try to work on the internals; quite
> the opposite.  I'm saying we need to make it easier to do so.  Even
> patches that look obviously correct on the surface can have unintended
> side-effects which break things is unexpected ways, especially for
> people who aren't extremely familiar with the code.
>
> We currently rely pretty heavily on expert knowledge when looking at
> patches to make sure they don't have unintended side-effects, which
> means a fairly deep knowledge of valac's internals is required for
> reviewing patches.  Unfortunately, the only way to gain that knowledge
> is to work on valac and have patches reviewed, so we end up with a bit
> of a chicken-and-egg problem.
>
> For a lot of patches we can use testing as an additional check to make
> sure the patch doesn't break anything.  With that in place, the bar for
> trusting reviewers is significantly lower, to the point where people
> who are less familiar with the valac internals could do reviews for a
> lot more patches, and Jürg and Luca needn't be bothered for most
> issues.
>
> Think of it as a way to build up the trustworthiness of a patch.  In
> order to be included in valac, a patch needs a certain level of trust.
> Code reviews each build up a bit of trust, and the more expertise the
> reviewer has with the vala internals the greater the weight of each
> review.  Passing automated tests also boosts the level of trust in a
> patch; the better the automated tests, the more trust we start with,
> and the less we need to add to get it to the point where we trust it
> enough to get it in the compiler.
>
>> > 
>>
>> I assume "more testing" is basically interesting because we need less
>> (sophisticated) review? That might be true from a functionality POV
>> but not regarding architecture etc. But more tests are always good of
>> course.
>
> I certainly wouldn't think of it as a less sophisticated review
> process.  If anything, I think it's more sophisticated.  I would say
> it's interesting because it would let us accept patches when the
> reviewers have less expertise in valac itself, because at least we know
> the patch doesn't break everything.
>
> Obviously automated testing can't replace humans entirely.  We would
> still need human reviewers, and big architectural changes would still
> require feedback from people like Jürg and Luca, but not all patches
> would.  If we don't have to bother them with the little stuff
> development can move a lot faster, and when something big comes up
> *then* we can pull them in.  Both of them are still (AFAIK) available
> for the occasional review, they just don't have the same amount of time
> for such reviews they once did.
>
> While solid tests may not be as helpful for deciding if major
> architectural changes provide a net gain, they are critical for
> actually writing them.  In a large project like valac, even if they're
> made by someone with a lot of expertise in the internals major changes
> are very likely to break something.  A comprehensive test suite lets us
> be much more confident in changes like that, so the question becomes
> whether or not we want the change, not whether making it will break
> everything.
>
> It's also worth noting that getting patches merged also means people
> are going to be more likely to contribute again, and as more of their
> patches are merged and they work on the compiler more the level of
> trust the community has in them will likely grow, and their patch
> reviews will carry more weight.  Eventually, that list of two people I
> consider to really be experts in vala's internals may grow.
>
>
> Evan
> ___
> vala-list mailing list
> vala-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/vala-list
>

Re: [Vala] Just a news I've read about popularity langage

[oyster]

C# and vala both stays on the picture (
http://sogrady-media.redmonk.com/sogrady/files/2016/07/lang.rank_.Q316.plot-WM.png
)
Is there any deeper comparation between vala and C#

BTW, TeX is also on the picture, but is it a computer language?

BTW2, currently, I am (re)study red/rebol, J and Forth, which are all
in not popular patterns but charming

2016-07-22 6:09 GMT+08:00 Dev_NIX :
> I readed time ago about Dova (
> https://wiki.gnome.org/action/show/Projects/Dova), seems like the project
> was stopped to focus efforts on the language itself.
>
> I wonder if a stronger community could help building a standard application
> framework 100% in Vala, with easier building tools and a good dependency
> manager.
>
>
>
> --
>
> *   EOF   *
>
> 2016-07-21 23:59 GMT+02:00 Mario Daniel Ruiz Saavedra <
> desideran...@rocketmail.com>:
>
>> For a package manager, GNU Guix could be of use. Regarding a standard
>> library, that's GLib.
>>
>> El jue., jul. 21, PM a 16:56, Dev_NIX
>>  escribió:
>> I understand your point, but maybe (for example) nodejs have a lower
>> learning curve and a faster way to get work done because it have a great
>> package manager.
>>
>> As fas as I never used Vala beyond multiple personal little experiments, I
>> feel that could be tools to make the life of starters better. For example,
>> there is a *great* project that helped me in every step, Autovala.
>>
>> One question: is there a "standard" Vala library/classes?
>>
>> --
>>
>> *  EOF  *
>>
>>
>> 2016-07-21 18:25 GMT+02:00 pelzflorian (Florian Pelz) <
>> pelzflor...@pelzflorian.de>:
>>
>> > On 07/21/2016 05:12 PM, Guillaume Poirier-Morency wrote:
>> > > Le jeudi 21 juillet 2016 à 17:43 +0300, Aleksandr Palamar a écrit :
>> > >>3. Package Manager, Vala already has a nice place with lot of nice
>> > >> VAPIs
>> > >>(https://github.com/nemequ/vala-extra-vapis), but better approach
>> > >> to
>> > >>have own package manager with auto-resolving of dependencies (like
>> > >> NPM in
>> > >>Node or Cargo in Rust).
>> > >
>> > > I would really enjoy a source package manager to retreive bindings and
>> > > external Vala projects. So far, I'm happy with Meson and subprojects.
>> > >
>> >
>> > Why a custom package manager?
>> >
>> > For the apps / libraries there is the distribution’s package manager.
>> > Please do not make yet another package manager for those. This is a
>> > solved problem.
>> >
>> > What remains are VAPIs. Why is a custom package manager a better
>> > approach than the vala-extra-vapis you are linking to? Your
>> > distribution’s package manager should take care of dependency resolution
>> > for the libraries the VAPIs are for. It also should take care of
>> > downloading the library’s source code when requested.
>> >
>> > Regards,
>> > Florian Pelz
>> > ___
>> > vala-list mailing list
>> > vala-list@gnome.org
>> > https://mail.gnome.org/mailman/listinfo/vala-list
>>
>> >
>> ___
>> vala-list mailing list
>> vala-list@gnome.org
>> https://mail.gnome.org/mailman/listinfo/vala-list
>>
>>
> ___
> vala-list mailing list
> vala-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/vala-list
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] 2 questions on valac in msys2

[oyster]

thank you, Gilzad Hamuni
in fact, I have another way: while EXE is running, try to delete all
the DLLs. If one DLLs is in used, it can not be deleted. However, this
method could fail if some DLLs are loaded later

2016-06-23 20:41 GMT+08:00 Gilzad Hamuni <gil...@gmx.net>:
> Hi,
> I can try to give you some ideas for the first question from my experiences 
> with msys+vala (Win32).
>
> In a real linux environment we can use ldd to find out which libraries an 
> executable depends on.
>
> $ ldd hello
>
> But in my version of msys/mingw ldd doesn't work. However, I don't update my 
> msys to avoid conflicts with too quickly updated libraries. So you might have 
> a working version of it by now.
>
> Another way is to use the Dependency Walker [1] which seems to be suggested 
> among developers. I haven't had many experiences with it though.
>
> The third way I know is just trial and error. You copy your hello.exe into a 
> different directory and call it directly from the system (outside the 
> msys-environment). Windows will then tell you which DLL it is missing. You 
> can then copy the requested DLL to the same directory and attempt to run 
> hello.exe again. Windows will tell you what other DLL is missing. So you 
> repeat this procedure until you have all the DLLs that hello.exe needs. You 
> surely don't need to provide all DLLs from mingw, thus you'll save some 
> space, too.
>
> If you still need to reduce the required disk space of your app+dlls, you can 
> try to pack them with UPX [2]. Just note that some anti-virus programs used 
> to detect self-extracting executables as harmful.
>
>
> Unfortunately I don't have a clue about your second question, I'm sorry.
>
>
> [1] http://www.dependencywalker.com/
> [2] http://upx.sourceforge.net/
>
>> Gesendet: Donnerstag, 23. Juni 2016 um 04:31 Uhr
>> Von: oyster <lepto.pyt...@gmail.com>
>> An: "vala-list@gnome.org" <vala-list@gnome.org>
>> Betreff: [Vala] 2 questions on valac in msys2
>>
>> they are 2 relative questions I found in my msys2 on Windows 7
>>
>> 1. how to distribute EXE for PC without glib/gtk/etc? Currently, I
>> copy all DLLs under /msys64 to the same directory where the EXE stays.
>> The problem is that it is not so nice, and the DLLs take up 150Mbytes!
>> So is there an automatic way to copy only necessary DLLs?
>>
>> 2. If I run hello_gtk.exe in the dos prompt window of Windows7, when I
>> close it, nothing is displayed. However, in msys2, I have changed the
>> current working directory to where hello_gtk.exe can be found, the I
>> run and close hello_gtk.exe
>> [code]
>> $ ./hello_gtk.exe
>>
>> # then I close hello_gtk.exe
>>
>> (hello_gtk.exe:43496): GLib-GObject-WARNING **: attempt to override
>> closure->va_marshal (63a48a20) with new marshal
>> (66710ea8)
>> [/code]
>>
>> Why? and how to eliminate it? Thanks
>> ___
>> vala-list mailing list
>> vala-list@gnome.org
>> https://mail.gnome.org/mailman/listinfo/vala-list
>>
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

[Vala] 2 questions on valac in msys2

[oyster]

they are 2 relative questions I found in my msys2 on Windows 7

1. how to distribute EXE for PC without glib/gtk/etc? Currently, I
copy all DLLs under /msys64 to the same directory where the EXE stays.
The problem is that it is not so nice, and the DLLs take up 150Mbytes!
So is there an automatic way to copy only necessary DLLs?

2. If I run hello_gtk.exe in the dos prompt window of Windows7, when I
close it, nothing is displayed. However, in msys2, I have changed the
current working directory to where hello_gtk.exe can be found, the I
run and close hello_gtk.exe
[code]
$ ./hello_gtk.exe

# then I close hello_gtk.exe

(hello_gtk.exe:43496): GLib-GObject-WARNING **: attempt to override
closure->va_marshal (63a48a20) with new marshal
(66710ea8)
[/code]

Why? and how to eliminate it? Thanks
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] why valac says "error: Failed to execute child process (Exec format error)"

[oyster]

yeah, uninstall and reinstall pkg-config solve this problem. now valac
can produce EXE on my sys2. Thank you all.

2016-06-22 16:02 GMT+08:00 Al Thomas <astav...@yahoo.co.uk>:
>
>
>
> ________
> From: oyster <lepto.pyt...@gmail.com>
> Sent: Wednesday, 22 June 2016, 2:05
> Subject: Re: [Vala] why valac says "error: Failed to execute child process
> (Exec format error)"
>
> I have to do these "export operation" every time when I run msys2
> since I don't know how to let msys2 do this automaticaly yet
> [code]
> export LANG=en
> export PATH=/usr/local/bin:/usr/bin:/bin:/opt/bin:/mingw64/bin
> export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/mingw64/lib/pkgconfig
> [/code]
>
> https://github.com/ghcjs/ghcjs/wiki/Preparing-the-Windows-build-environment
> suggests editing .bashrc in your MSYS2 home directory to set the variables.
>
>
> mingw-w64-x86_64-pkg-config seems to be same with what I have
> installed with "pacman -S pkg-config"
> [code]
> $ pacman -S mingw-w64-x86_64-pkg-config
> error: duplicated database entry 'curl'
> error: duplicated database entry 'filesystem'
> error: duplicated database entry 'libcurl'
> warning: mingw-w64-x86_64-pkg-config-0.29.1-1 is up to date -- reinstalling
> resolving dependencies...
> looking for conflicting packages...
>
> Packages (1) mingw-w64-x86_64-pkg-config-0.29.1-1
>
> Total Installed Size:  1.32 MiB
> Net Upgrade Size:  0.00 MiB
> [/code]
>
> You should probably uninstall first:
> pacman -R pkg-config
> Also https://sourceforge.net/p/msys2/wiki/MSYS2%20installation/
> advises "Sometimes a package upgrade fails with failed to commit transaction
> (conflicting files) and some-pkg: /path/to/some/file exists in filesystem.
> If you're sure you didn't put the offending files there manually, move or
> delete the files and start the upgrade again."
>
>
>
> $ echo $PKG_CONFIG_PATH
> /usr/lib/pkgconfig:/usr/share/pkgconfig:/lib/pkgconfig:/mingw64/lib/pkgconfig
>
> $ ls  /mingw64/lib/pkgconfig/go*.pc
> /mingw64/lib/pkgconfig/gobject-2.0.pc
> /mingw64/lib/pkgconfig/gobject-introspection-1.0.pc
> /mingw64/lib/pkgconfig/gobject-introspection-no-export-1.0.pc
>
> [/code]
>
> The problem identified from the link below was one version of pkg-config
> wasn't
> finding the right path. You could also try setting PKG_CONFIG_PATH to just
> /mingw64/lib/pkgconfig
>
>
> 2016-06-22 0:32 GMT+08:00 Al Thomas <astav...@yahoo.co.uk>:
>> This comment (
>>
>> https://github.com/commercialhaskell/stack/issues/377#issuecomment-118182127
>> )
>> says "I should be using the package mingw-w64-x86_64-pkg-config instead of
>> pkg-config"
>>
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] why valac says "error: Failed to execute child process (Exec format error)"

[oyster]

I have to do these "export operation" every time when I run msys2
since I don't know how to let msys2 do this automaticaly yet
[code]
export LANG=en
export PATH=/usr/local/bin:/usr/bin:/bin:/opt/bin:/mingw64/bin
export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/mingw64/lib/pkgconfig
[/code]

mingw-w64-x86_64-pkg-config seems to be same with what I have
installed with "pacman -S pkg-config"
[code]
$ pacman -S mingw-w64-x86_64-pkg-config
error: duplicated database entry 'curl'
error: duplicated database entry 'filesystem'
error: duplicated database entry 'libcurl'
warning: mingw-w64-x86_64-pkg-config-0.29.1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) mingw-w64-x86_64-pkg-config-0.29.1-1

Total Installed Size:  1.32 MiB
Net Upgrade Size:  0.00 MiB
[/code]

gobjetct has been installed, although I don't know how I installed it,
maybe "pacman -S mingw-w64-x86_64-gobject-introspection" did, maybe
not
[code I erase many other pacakges here]
$ pkg-config --list-all
gobject-introspection-no-export-1.0 gobject-introspection - GObject
Introspection
gobject-2.0 GObject - GLib Type, Object,
Parameter and Signal Library
gobject-introspection-1.0   gobject-introspection - GObject
Introspection


$ echo $PKG_CONFIG_PATH
/usr/lib/pkgconfig:/usr/share/pkgconfig:/lib/pkgconfig:/mingw64/lib/pkgconfig

$ ls  /mingw64/lib/pkgconfig/go*.pc
/mingw64/lib/pkgconfig/gobject-2.0.pc
/mingw64/lib/pkgconfig/gobject-introspection-1.0.pc
/mingw64/lib/pkgconfig/gobject-introspection-no-export-1.0.pc

[/code]

this can be tested by compiling a gobject sample
"someobject.smallest.c" found on
http://blog.csdn.net/xbl1986/article/details/6701047 , sorry the
webpage is in Chinese, but the code is in English
[code]
$ gcc someobject.smallest.c `pkg-config --cflags --libs gobject-2.0`
$ ./a.exe
init the type system
init type system OK 
-- some_object_class_init # 41
-- some_object_init # 48
-- some_object_dispose # 25
-- some_object_finalize # 32
finish GObject Demo 
[/code]

however
[code]
$ valac --cc=gcc ./helloworld.vala
Package gobject-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gobject-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gobject-2.0' found
Compilation failed: 1 error(s), 0 warning(s)
error: pkg-config exited with status 1

# I can compile the produced C file as I mentioned in last post
$ gcc helloworld.vala.c -o helloworld.vala.exe `pkg-config --cflags
--libs glib-2.0` `pkg-config --cflags --libs gobject-2.0`

$ ./helloworld.vala.exe
hello world
[/code]

2016-06-22 0:32 GMT+08:00 Al Thomas <astav...@yahoo.co.uk>:
>
>
>
> 
> From: oyster <lepto.pyt...@gmail.com>
> Sent: Tuesday, 21 June 2016, 16:53
> Subject: Re: [Vala] why valac says "error: Failed to execute child process
> (Exec format error)"
>
> sorry, I installed gcc/pkgconfig/gobject now
> $ pacman -S mingw-w64-x86_64-gcc
> $ pacman -S pkg-config
>
> This comment (
> https://github.com/commercialhaskell/stack/issues/377#issuecomment-118182127
> )
> says "I should be using the package mingw-w64-x86_64-pkg-config instead of
> pkg-config"
>
>
> $ pacman -S mingw-w64-x86_64-gobject-introspection
>
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] why valac says "error: Failed to execute child process (Exec format error)"

[oyster]

$ gcc hello.vala.c
hello.vala.c:5:18: fatal error: glib.h: No such file or directory
compilation terminated.

#the following line means gobject-2.0 is installed on my msys2, and
can be found by pkg-config
$ gcc hello.vala.c $(pkg-config --cflags --libs gobject-2.0)

$ ./a.exe
hello

2016-06-21 23:55 GMT+08:00 oyster <lepto.pyt...@gmail.com>:
> for my old msys/mingw
> "echo $CC" is empty
>
> $ valac --cc=gcc hello.vala
> error: Failed to execute child process (Exec format error)
> error: Failed to execute child process (Exec format error)
> error: Failed to execute child process (Exec format error)
> Compilation failed: 3 error(s), 0 warning(s)
>
> $ gcc
> gcc.exe: fatal error: no input files
> compilation terminated.
>
> 2016-06-21 23:21 GMT+08:00 ben <iofel...@gmail.com>:
>> What does
>> $ echo $CC
>> show?
>>
>> Does
>> $ valac --cc=gcc ./hello.vala
>> work?
>>
>> On Tue, 2016-06-21 at 22:56 +0800, oyster wrote:
>>> $ echo $PATH
>>> /usr/local/bin:/usr/bin:/bin:/opt/bin:/c/Windows/System32:/c/Windows:
>>> /c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:
>>> /mingw64/bin
>>>
>>> to delete all possible things in old Msys, I run
>>> $ export PATH=/usr/local/bin:/usr/bin:/bin:/opt/bin:/mingw64/bin
>>>
>>> $ echo $PATH
>>> /usr/local/bin:/usr/bin:/bin:/opt/bin:/mingw64/bin
>>>
>>> $ vala ./hello.vala
>>> Compilation failed: 3 error(s), 0 warning(s)
>>> error: Failed to execute child process (No such file or directory)
>>> error: Failed to execute child process (No such file or directory)
>>> error: Failed to execute child process (No such file or directory)
>>>
>>> 2016-06-21 22:44 GMT+08:00 Al Thomas <astav...@yahoo.co.uk>:
>>> >
>>> >
>>> > 
>>> > From: oyster <lepto.pyt...@gmail.com>
>>> > Sent: Tuesday, 21 June 2016, 15:38
>>> > Subject: Re: [Vala] why valac says "error: Failed to execute child
>>> > process
>>> > (Exec format error)"
>>> >
>>> > Msys2 (msys2-x86_64-20160205.exe) has been installed, and I have
>>> > used
>>> > $  pacman -Sy pacman
>>> > $  pacman -Syu
>>> > $  pacman -Su
>>> > which all say " there is nothing to do" now
>>> >
>>> >
>>> > I use this line to install Vala in msys2.exe
>>> > $  pacman -S mingw-w64-x86_64-vala
>>> >
>>> > then
>>> > $ export LANG=en
>>> > $ export PATH=$PATH:/mingw64/bin
>>> >
>>> > What does
>>> > echo $PATH
>>> > show? Does it still include your old MSYS path so those
>>> > binaries/libraries
>>> > are being picked up first?
>>> >
>>> >
>>> > $ vala ./hello.vala
>>> > Compilation failed: 3 error(s), 0 warning(s)
>>> > error: Failed to execute child process (No such file or directory)
>>> > error: Failed to execute child process (No such file or directory)
>>> > error: Failed to execute child process (No such file or directory)
>>> >
>>> >
>>> ___
>>> vala-list mailing list
>>> vala-list@gnome.org
>>> https://mail.gnome.org/mailman/listinfo/vala-list
>> ___
>> vala-list mailing list
>> vala-list@gnome.org
>> https://mail.gnome.org/mailman/listinfo/vala-list
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] why valac says "error: Failed to execute child process (Exec format error)"

[oyster]

for my old msys/mingw
"echo $CC" is empty

$ valac --cc=gcc hello.vala
error: Failed to execute child process (Exec format error)
error: Failed to execute child process (Exec format error)
error: Failed to execute child process (Exec format error)
Compilation failed: 3 error(s), 0 warning(s)

$ gcc
gcc.exe: fatal error: no input files
compilation terminated.

2016-06-21 23:21 GMT+08:00 ben <iofel...@gmail.com>:
> What does
> $ echo $CC
> show?
>
> Does
> $ valac --cc=gcc ./hello.vala
> work?
>
> On Tue, 2016-06-21 at 22:56 +0800, oyster wrote:
>> $ echo $PATH
>> /usr/local/bin:/usr/bin:/bin:/opt/bin:/c/Windows/System32:/c/Windows:
>> /c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:
>> /mingw64/bin
>>
>> to delete all possible things in old Msys, I run
>> $ export PATH=/usr/local/bin:/usr/bin:/bin:/opt/bin:/mingw64/bin
>>
>> $ echo $PATH
>> /usr/local/bin:/usr/bin:/bin:/opt/bin:/mingw64/bin
>>
>> $ vala ./hello.vala
>> Compilation failed: 3 error(s), 0 warning(s)
>> error: Failed to execute child process (No such file or directory)
>> error: Failed to execute child process (No such file or directory)
>> error: Failed to execute child process (No such file or directory)
>>
>> 2016-06-21 22:44 GMT+08:00 Al Thomas <astav...@yahoo.co.uk>:
>> >
>> >
>> > 
>> > From: oyster <lepto.pyt...@gmail.com>
>> > Sent: Tuesday, 21 June 2016, 15:38
>> > Subject: Re: [Vala] why valac says "error: Failed to execute child
>> > process
>> > (Exec format error)"
>> >
>> > Msys2 (msys2-x86_64-20160205.exe) has been installed, and I have
>> > used
>> > $  pacman -Sy pacman
>> > $  pacman -Syu
>> > $  pacman -Su
>> > which all say " there is nothing to do" now
>> >
>> >
>> > I use this line to install Vala in msys2.exe
>> > $  pacman -S mingw-w64-x86_64-vala
>> >
>> > then
>> > $ export LANG=en
>> > $ export PATH=$PATH:/mingw64/bin
>> >
>> > What does
>> > echo $PATH
>> > show? Does it still include your old MSYS path so those
>> > binaries/libraries
>> > are being picked up first?
>> >
>> >
>> > $ vala ./hello.vala
>> > Compilation failed: 3 error(s), 0 warning(s)
>> > error: Failed to execute child process (No such file or directory)
>> > error: Failed to execute child process (No such file or directory)
>> > error: Failed to execute child process (No such file or directory)
>> >
>> >
>> ___
>> vala-list mailing list
>> vala-list@gnome.org
>> https://mail.gnome.org/mailman/listinfo/vala-list
> ___
> vala-list mailing list
> vala-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/vala-list
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] why valac says "error: Failed to execute child process (Exec format error)"

[oyster]

sorry, I installed gcc/pkgconfig/gobject now
$ pacman -S mingw-w64-x86_64-gcc
$ pacman -S pkg-config
$ pacman -S mingw-w64-x86_64-gobject-introspection

$ valac ./hello.vala
Package gobject-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gobject-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gobject-2.0' found
Compilation failed: 1 error(s), 0 warning(s)
error: pkg-config exited with status 1

$ pkg-config --libs --cflags gobject-2.0
-mms-bitfields -I/mingw64/include/glib-2.0
-I/mingw64/lib/glib-2.0/include -I/mingw64/include -L/mingw64/lib
-LC:/building/msys64/mingw64/lib/../lib -L/mingw64/lib
-LC:/building/msys64/mingw64/lib -L/mingw64/lib -lgobject-2.0 -lffi
-lglib-2.0 -lintl -pthread -lws2_32 -lole32 -lwinmm -lshlwapi -lpcre
-lintl -lpcre

$ valac ./hello.vala --ccode
$ gcc hello.c $(pkg-config --cflags --libs glib-2.0)
$ ./a.exe
hello


2016-06-21 23:13 GMT+08:00 Al Thomas <astav...@yahoo.co.uk>:
>
>
>
>
> ____
> From: oyster <lepto.pyt...@gmail.com>
> Sent: Tuesday, 21 June 2016, 15:56
> Subject: Re: [Vala] why valac says "error: Failed to execute child process
> (Exec format error)"
>
> to delete all possible things in old Msys, I run
> $ export PATH=/usr/local/bin:/usr/bin:/bin:/opt/bin:/mingw64/bin
>
> $ echo $PATH
> /usr/local/bin:/usr/bin:/bin:/opt/bin:/mingw64/bin
>
> $ vala ./hello.vala
>
> That should really be 'valac'. 'vala' without the 'c' will also compile to a
> temporary directory and run the binary.
> This adds additional complexity to your testing.
>
>
> Compilation failed: 3 error(s), 0 warning(s)
> error: Failed to execute child process (No such file or directory)
> error: Failed to execute child process (No such file or directory)
> error: Failed to execute child process (No such file or directory)
>
> This is now a different error. The files are not being found. Have you also
> installed MSYS2 gcc and pkg-config?
>
>
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] why valac says "error: Failed to execute child process (Exec format error)"

[oyster]

$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/opt/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/mingw64/bin

to delete all possible things in old Msys, I run
$ export PATH=/usr/local/bin:/usr/bin:/bin:/opt/bin:/mingw64/bin

$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/opt/bin:/mingw64/bin

$ vala ./hello.vala
Compilation failed: 3 error(s), 0 warning(s)
error: Failed to execute child process (No such file or directory)
error: Failed to execute child process (No such file or directory)
error: Failed to execute child process (No such file or directory)

2016-06-21 22:44 GMT+08:00 Al Thomas <astav...@yahoo.co.uk>:
>
>
> ____
> From: oyster <lepto.pyt...@gmail.com>
> Sent: Tuesday, 21 June 2016, 15:38
> Subject: Re: [Vala] why valac says "error: Failed to execute child process
> (Exec format error)"
>
> Msys2 (msys2-x86_64-20160205.exe) has been installed, and I have used
> $  pacman -Sy pacman
> $  pacman -Syu
> $  pacman -Su
> which all say " there is nothing to do" now
>
>
> I use this line to install Vala in msys2.exe
> $  pacman -S mingw-w64-x86_64-vala
>
> then
> $ export LANG=en
> $ export PATH=$PATH:/mingw64/bin
>
> What does
> echo $PATH
> show? Does it still include your old MSYS path so those binaries/libraries
> are being picked up first?
>
>
> $ vala ./hello.vala
> Compilation failed: 3 error(s), 0 warning(s)
> error: Failed to execute child process (No such file or directory)
> error: Failed to execute child process (No such file or directory)
> error: Failed to execute child process (No such file or directory)
>
>
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] why valac says "error: Failed to execute child process (Exec format error)"

[oyster]

"valac hello.vala --ccode" generates "hello.c" correctly

however I can't understand how to debug further

2016-06-21 19:37 GMT+08:00 Al Thomas <astav...@yahoo.co.uk>:
>
>
>
> ________
> From: oyster <lepto.pyt...@gmail.com>
> Sent: Tuesday, 21 June 2016, 6:49
> Subject: Re: [Vala] why valac says "error: Failed to execute child process
> (Exec format error)"
>
> $ file $(which valac)
> /opt/windows_32/vala-my-build/bin/valac.exe: PE32 executable for MS
> Windows (console) Intel 80386 32-bit
>
> $ file $(which  pkg-config)
> /opt/windows_32/bin/pkg-config.exe: PE32 executable for MS Windows
> (console) Intel 80386 32-bit
> LOVLJIDY@LOVLJIDY-PC ~
>
> $ file $(which gcc)
> /opt/windows_32/bin/gcc.exe: PE32 executable for MS Windows (console)
> Intel 80386 32-bit
>
> $ file /e/msys/opt/windows_32/bin/libglib-2.0-0.dll
> /e/msys/opt/windows_32/bin/libglib-2.0-0.dll: PE32 executable for MS
> Windows (DLL) (console) Intel 80386 32-bit
>
> Well that seems OK.
>
> Now try 'valac hello.vala --ccode' and see if you get the error.
> The --ccode will by pass this block of code:
> https://git.gnome.org/browse/vala/tree/compiler/valacompiler.vala#n468
>
> If you don't get the error then it means the error is in that block
> somwhere.
> There are a number of GLib functions that call out to the operating system.
> These could be causing your error:
> Environment.get_variable ()
> and from
> https://git.gnome.org/browse/vala/tree/codegen/valaccodecompiler.vala#n51
> Process.spawn_command_line_sync ()
> You could try small test Vala programs to see which of those are causing the
> problem.
> As to the solution if Process.spawn_command_line_sync () is not working on
> MSYS
> I don't know. Make the leap to MSYS2 so you are following an active
> packaging system?
>
> Al
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] why valac says "error: Failed to execute child process (Exec format error)"

[oyster]

Msys2 (msys2-x86_64-20160205.exe) has been installed, and I have used
$  pacman -Sy pacman
$  pacman -Syu
$  pacman -Su
which all say " there is nothing to do" now


I use this line to install Vala in msys2.exe
$  pacman -S mingw-w64-x86_64-vala

then
$ export LANG=en
$ export PATH=$PATH:/mingw64/bin

$ vala ./hello.vala
Compilation failed: 3 error(s), 0 warning(s)
error: Failed to execute child process (No such file or directory)
error: Failed to execute child process (No such file or directory)
error: Failed to execute child process (No such file or directory)

however, "hello.vala.c" has been created

2016-06-21 21:24 GMT+08:00 oyster <lepto.pyt...@gmail.com>:
> yes, I have installed Msys2 ( msys2-x86_64-20160205.exe)
>
> $ pacman -S mingw-w64-vala
> error: target not found: mingw-w64-vala
>
> $ pacman -S mingw-w32-vala
> error: target not found: mingw-w32-vala
>
> 2016-06-21 17:44 GMT+08:00 Dmitry Golovin <d...@golovin.in>:
>> Hi,
>>
>> Do you use (old, unmaintained) MinGW/MSYS or MSYS2 
>> (https://msys2.github.io/)? It should not be a problem with MSYS2: just type
>>
>> pacman -S mingw-w64-vala
>>
>> It should be the latest version, so you don't need to compile it yourself.
>>
>> Regards,
>> Dmitry
>>
>> 21.06.2016, 08:49, "oyster" <lepto.pyt...@gmail.com>:
>>>  $ file $(which valac)
>>> /opt/windows_32/vala-my-build/bin/valac.exe: PE32 executable for MS
>>> Windows (console) Intel 80386 32-bit
>>>
>>> $ file $(which pkg-config)
>>> /opt/windows_32/bin/pkg-config.exe: PE32 executable for MS Windows
>>> (console) Intel 80386 32-bit
>>> LOVLJIDY@LOVLJIDY-PC ~
>>>
>>> $ file $(which gcc)
>>> /opt/windows_32/bin/gcc.exe: PE32 executable for MS Windows (console)
>>> Intel 80386 32-bit
>>>
>>> $ file /e/msys/opt/windows_32/bin/libglib-2.0-0.dll
>>> /e/msys/opt/windows_32/bin/libglib-2.0-0.dll: PE32 executable for MS
>>> Windows (DLL) (console) Intel 80386 32-bit
>>>
>>> and this is a test on a 64bits application for comparation:
>>> $ file /e/greensoft/3d/blender/blender-2.77.1-git.9d431f1-AMD64/blender.exe
>>> /e/greensoft/3d/blender/blender-2.77.1-git.9d431f1-AMD64/blender.exe:
>>> PE32+ executable for MS Windows (console) Mono/.Net assembly
>>>
>>> 2016-06-21 5:27 GMT+08:00 Al Thomas <astav...@yahoo.co.uk>:
>>>>  
>>>>  From: oyster <lepto.pyt...@gmail.com>
>>>>  Sent: Monday, 20 June 2016, 16:08
>>>>  Subject: Re: [Vala] why valac says "error: Failed to execute child process
>>>>  (Exec format error)"
>>>>
>>>>  so what is the possible solution to find out which 32 and 64 bits DLLs
>>>>  are conflictive?
>>>>
>>>>  According to this Stack Overflow answer, if you have Visual Studio install
>>>>  "Dumpbin will report DLLs as machine (x86) or machine (x64)". See
>>>>  
>>>> http://stackoverflow.com/questions/197951/how-can-i-determine-for-which-platform-an-executable-is-compiled
>>>>  Otherwise
>>>>  
>>>> http://stackoverflow.com/questions/495244/how-can-i-test-a-windows-dll-to-determine-if-it-is-32bit-or-64bit
>>>>  may help.
>>>>
>>>>  You should check the format of valac, gcc and pkg-config
>>>>
>>>>  I am sure my GCC produces 32bits exe/dll files even on my 64 bits machine.
>>>>
>>>>  please note, as I have mentioned in
>>>>  https://mail.gnome.org/archives/vala-list/2016-June/msg00027.html
>>>>  1) vala-0.18.0-mingw32-bin.tar.xz from http://linbox.free.fr/vala/ can
>>>>  compile hello.vala without problem
>>>>  2) Then I compile vala-0.32 from source with vala-0.18.0. Then I
>>>>  overwrite vala-0.18.0 with my new compiled vala-0.32( which is for
>>>>  i386 and above, i.e. 32bits)
>>>>  3) my new compiled vala-0.32 complains "error: Failed to execute child
>>>>  process (Exec format error)" when it is used to compile hello.vala(
>>>>  which can be compiled by vala-0.18.0)
>>>
>>> ___
>>> vala-list mailing list
>>> vala-list@gnome.org
>>> https://mail.gnome.org/mailman/listinfo/vala-list
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] why valac says "error: Failed to execute child process (Exec format error)"

[oyster]

yes, I have installed Msys2 ( msys2-x86_64-20160205.exe)

$ pacman -S mingw-w64-vala
error: target not found: mingw-w64-vala

$ pacman -S mingw-w32-vala
error: target not found: mingw-w32-vala

2016-06-21 17:44 GMT+08:00 Dmitry Golovin <d...@golovin.in>:
> Hi,
>
> Do you use (old, unmaintained) MinGW/MSYS or MSYS2 
> (https://msys2.github.io/)? It should not be a problem with MSYS2: just type
>
> pacman -S mingw-w64-vala
>
> It should be the latest version, so you don't need to compile it yourself.
>
> Regards,
> Dmitry
>
> 21.06.2016, 08:49, "oyster" <lepto.pyt...@gmail.com>:
>>  $ file $(which valac)
>> /opt/windows_32/vala-my-build/bin/valac.exe: PE32 executable for MS
>> Windows (console) Intel 80386 32-bit
>>
>> $ file $(which pkg-config)
>> /opt/windows_32/bin/pkg-config.exe: PE32 executable for MS Windows
>> (console) Intel 80386 32-bit
>> LOVLJIDY@LOVLJIDY-PC ~
>>
>> $ file $(which gcc)
>> /opt/windows_32/bin/gcc.exe: PE32 executable for MS Windows (console)
>> Intel 80386 32-bit
>>
>> $ file /e/msys/opt/windows_32/bin/libglib-2.0-0.dll
>> /e/msys/opt/windows_32/bin/libglib-2.0-0.dll: PE32 executable for MS
>> Windows (DLL) (console) Intel 80386 32-bit
>>
>> and this is a test on a 64bits application for comparation:
>> $ file /e/greensoft/3d/blender/blender-2.77.1-git.9d431f1-AMD64/blender.exe
>> /e/greensoft/3d/blender/blender-2.77.1-git.9d431f1-AMD64/blender.exe:
>> PE32+ executable for MS Windows (console) Mono/.Net assembly
>>
>> 2016-06-21 5:27 GMT+08:00 Al Thomas <astav...@yahoo.co.uk>:
>>>  
>>>  From: oyster <lepto.pyt...@gmail.com>
>>>  Sent: Monday, 20 June 2016, 16:08
>>>  Subject: Re: [Vala] why valac says "error: Failed to execute child process
>>>  (Exec format error)"
>>>
>>>  so what is the possible solution to find out which 32 and 64 bits DLLs
>>>  are conflictive?
>>>
>>>  According to this Stack Overflow answer, if you have Visual Studio install
>>>  "Dumpbin will report DLLs as machine (x86) or machine (x64)". See
>>>  
>>> http://stackoverflow.com/questions/197951/how-can-i-determine-for-which-platform-an-executable-is-compiled
>>>  Otherwise
>>>  
>>> http://stackoverflow.com/questions/495244/how-can-i-test-a-windows-dll-to-determine-if-it-is-32bit-or-64bit
>>>  may help.
>>>
>>>  You should check the format of valac, gcc and pkg-config
>>>
>>>  I am sure my GCC produces 32bits exe/dll files even on my 64 bits machine.
>>>
>>>  please note, as I have mentioned in
>>>  https://mail.gnome.org/archives/vala-list/2016-June/msg00027.html
>>>  1) vala-0.18.0-mingw32-bin.tar.xz from http://linbox.free.fr/vala/ can
>>>  compile hello.vala without problem
>>>  2) Then I compile vala-0.32 from source with vala-0.18.0. Then I
>>>  overwrite vala-0.18.0 with my new compiled vala-0.32( which is for
>>>  i386 and above, i.e. 32bits)
>>>  3) my new compiled vala-0.32 complains "error: Failed to execute child
>>>  process (Exec format error)" when it is used to compile hello.vala(
>>>  which can be compiled by vala-0.18.0)
>>
>> ___
>> vala-list mailing list
>> vala-list@gnome.org
>> https://mail.gnome.org/mailman/listinfo/vala-list
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] why valac says "error: Failed to execute child process (Exec format error)"

[oyster]

 $ file $(which valac)
/opt/windows_32/vala-my-build/bin/valac.exe: PE32 executable for MS
Windows (console) Intel 80386 32-bit

$ file $(which  pkg-config)
/opt/windows_32/bin/pkg-config.exe: PE32 executable for MS Windows
(console) Intel 80386 32-bit
LOVLJIDY@LOVLJIDY-PC ~

$ file $(which gcc)
/opt/windows_32/bin/gcc.exe: PE32 executable for MS Windows (console)
Intel 80386 32-bit

$ file /e/msys/opt/windows_32/bin/libglib-2.0-0.dll
/e/msys/opt/windows_32/bin/libglib-2.0-0.dll: PE32 executable for MS
Windows (DLL) (console) Intel 80386 32-bit

and this is a test on a 64bits application for comparation:
$ file /e/greensoft/3d/blender/blender-2.77.1-git.9d431f1-AMD64/blender.exe
/e/greensoft/3d/blender/blender-2.77.1-git.9d431f1-AMD64/blender.exe:
PE32+ executable for MS Windows (console) Mono/.Net assembly

2016-06-21 5:27 GMT+08:00 Al Thomas <astav...@yahoo.co.uk>:
>
>
>
> ________
> From: oyster <lepto.pyt...@gmail.com>
> Sent: Monday, 20 June 2016, 16:08
> Subject: Re: [Vala] why valac says "error: Failed to execute child process
> (Exec format error)"
>
> so what is the possible solution to find out which 32 and 64 bits DLLs
> are conflictive?
>
> According to this Stack Overflow answer, if you have Visual Studio install
> "Dumpbin will report DLLs as machine (x86) or machine (x64)". See
> http://stackoverflow.com/questions/197951/how-can-i-determine-for-which-platform-an-executable-is-compiled
> Otherwise
> http://stackoverflow.com/questions/495244/how-can-i-test-a-windows-dll-to-determine-if-it-is-32bit-or-64bit
> may help.
>
> You should check the format of valac, gcc and pkg-config
>
>
>
> I am sure my GCC produces 32bits exe/dll files even on my 64 bits machine.
>
> please note, as I have mentioned in
> https://mail.gnome.org/archives/vala-list/2016-June/msg00027.html
> 1) vala-0.18.0-mingw32-bin.tar.xz from http://linbox.free.fr/vala/ can
> compile hello.vala without problem
> 2) Then I compile vala-0.32 from source with vala-0.18.0. Then I
> overwrite vala-0.18.0 with my new compiled vala-0.32( which is for
> i386 and above, i.e. 32bits)
> 3) my new compiled vala-0.32 complains "error: Failed to execute child
> process (Exec format error)" when it is used to compile hello.vala(
> which can be compiled by vala-0.18.0)
>
>
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] why valac says "error: Failed to execute child process (Exec format error)"

[oyster]

Hi,

so what is the possible solution to find out which 32 and 64 bits DLLs
are conflictive?

I am sure my GCC produces 32bits exe/dll files even on my 64 bits machine.

please note, as I have mentioned in
https://mail.gnome.org/archives/vala-list/2016-June/msg00027.html
1) vala-0.18.0-mingw32-bin.tar.xz from http://linbox.free.fr/vala/ can
compile hello.vala without problem
2) Then I compile vala-0.32 from source with vala-0.18.0. Then I
overwrite vala-0.18.0 with my new compiled vala-0.32( which is for
i386 and above, i.e. 32bits)
3) my new compiled vala-0.32 complains "error: Failed to execute child
process (Exec format error)" when it is used to compile hello.vala(
which can be compiled by vala-0.18.0)

Regards.
Lee June
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] why valac says "error: Failed to execute child process (Exec format error)"

[oyster]

currently, the following command line creates EXE file in my msys
without problem as Dmitry says
[quote]
$ valac hello.vala
error: Failed to execute child process (Exec format error)
error: Failed to execute child process (Exec format error)
error: Failed to execute child process (Exec format error)
Compilation failed: 3 error(s), 0 warning(s)

$ gcc -o hello.exe hello.vala.c `pkg-config --cflags --libs glib-2.0`

#or "gcc -o hello.exe hello.vala.c `pkg-config --cflags --libs glib`
", since there is both glib.pc and glib-2.0.pc

$ ./hello.exe
hello
[/quote]
but obviously it is not so automatic

Another way relies on https://sourceforge.net/projects/valainstaller/,
but I don't know how to compile cloned master vala code

C U
Lee June

2016-06-17 19:39 GMT+08:00 Dmitry Golovin <d...@golovin.in>:
> Hi,
>
> I had similar problem and solved it just by first generating C code (valac -C 
> ...) and then compiling resulting code with GCC.
>
> Regards,
> Dmitry
>
> 15.06.2016, 18:42, "oyster" <lepto.pyt...@gmail.com>:
>> I am using mingw + msys on win7 64bits. The gcc can compile to produce
>> EXE file, and pkg-config can run no problem
>>
>> I can compile vala_0.32.0 without problem
>>
>> but when I try to use "valac -v hello.vala" to compile any vala source, I 
>> find
>> [quote]
>> Loaded package 
>> `E:\msys\opt\windows_32\vala-my-build\share/vala-0.32/vapi/glib-2.0.vapi'
>> Loaded package 
>> `E:\msys\opt\windows_32\vala-my-build\share/vala-0.32/vapi/gobject-2.0.vapi'
>> error: Failed to execute child process (Exec format error)
>> ...
>> Compilation failed: 3 error(s), 0 warning(s)
>> [/quote]
>>
>> Any hints to find what is the problem? Thanks
>> ___
>> vala-list mailing list
>> vala-list@gnome.org
>> https://mail.gnome.org/mailman/listinfo/vala-list
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

[Vala] error: Failed to execute child process (Exec format error)

[oyster]

My compiled valac says "error: Failed to execute child process (Exec
format error)"
any hints to trace what is the problem?

1. I have a pre-installed Mingw + msys on my win7 64 bits to compile
32bits applications, which can compile CPP/C program without problem.
pkg-config is avaliable too. And I don't want to install yet another
mingw+msys since I have installed many libs

2. Install old vala
I downloaded vala-0.18.0-mingw32-bin.tar from
http://linbox.free.fr/vala/, and decompressed it into
/opt/windows_32/vala-my-build, then I add
/opt/windows_32/vala-my-build into PATH

3. test old vala on hello.vala to prove vala-0.18 runs with my mingw+msys
[I am hello.vala]
void main()
{print("hello\n");}
[/I am hello.vala]

[compile hello]
$ valac hello.vala
r:/hello.vala.c: In function 'main':
r:/hello.vala.c:20:2: warning: 'g_type_init' is deprecated (declared at E:/msys/
opt/windows_32/include/glib-2.0/gobject/gtype.h:681) [-Wdeprecated-declarations]

  g_type_init ();
  ^
[compile hello]

then run hello.exe
[run hello.exe]
$ hello.exe
hello
[/run hello.exe]

4. then download
https://wiki.gnome.org/Projects/Vala/Release#Vala_0.32.0 and
decompress it into /r/vala-0.32.0

5. compile Vala_0.32.0 and install into my mingw+msys
[compile Vala_0.32.0 and install into my mingw+msys]
$ cd /r/vala-0.32.0
$ ./configure --prefix=/opt/windows_32/vala-my-build
$ make
$ make install
[/compile Vala_0.32.0 and install into my mingw+msys]

6. testing new-compiled vala-0.32 on hello.vala failed
[test new-compiled vala-0.32]
$ valac hello.vala
error: Failed to execute child process (Exec format error)
error: Failed to execute child process (Exec format error)
error: Failed to execute child process (Exec format error)
Compilation failed: 3 error(s), 0 warning(s)
[/test new-compiled vala-0.32]

7. in case you want this failed test. Of cause, it can not succeed
since we have met the faliure in step 6
[make test]
$ make test
cd tests && make  check
make[1]: Entering directory `/r/vala-0.32.0/tests'
make  check-am
make[2]: Entering directory `/r/vala-0.32.0/tests'
make  check-TESTS
make[3]: Entering directory `/r/vala-0.32.0/tests'
TEST: Building...  FAIL
Compilation failed: 6 error(s), 0 warning(s)
error: Failed to execute child process (Exec format error)
error: Failed to execute child process (Exec format error)
error: Failed to execute child process (Exec format error)
error: Failed to execute child process (Exec format error)
error: Failed to execute child process (Exec format error)
error: Failed to execute child process (Exec format error)
Makefile:2214: recipe for target `check-TESTS' failed
make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory `/r/vala-0.32.0/tests'
Makefile:2088: recipe for target `check-am' failed
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/r/vala-0.32.0/tests'
Makefile:2090: recipe for target `check' failed
make[1]: *** [check] Error 2
make[1]: Leaving directory `/r/vala-0.32.0/tests'
Makefile:968: recipe for target `test' failed
make: *** [test] Error 2
[/make test]
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list

[Vala] why valac says "error: Failed to execute child process (Exec format error)"

[oyster]

I am using mingw + msys on win7 64bits. The gcc can compile to produce
EXE file, and pkg-config can run no problem

I can compile vala_0.32.0 without problem

but when I try to use "valac -v hello.vala" to compile any vala source, I find
[quote]
Loaded package 
`E:\msys\opt\windows_32\vala-my-build\share/vala-0.32/vapi/glib-2.0.vapi'
Loaded package 
`E:\msys\opt\windows_32\vala-my-build\share/vala-0.32/vapi/gobject-2.0.vapi'
error: Failed to execute child process (Exec format error)
...
Compilation failed: 3 error(s), 0 warning(s)
[/quote]

Any hints to find what is the problem? Thanks
___
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list