Re: [Guile-commits] GNU Guile branch, wip-1-8-mingw-build, updated. release_1-8-7-22-g7edad77

Re: [Guile-commits] GNU Guile branch, wip-1-8-mingw-build, updated. release_1-8-7-22-g7edad77

[Ludovic Courtès]

Hi Neil,

"Neil Jerram" <neil@ossau.uklinux.net> writes:

> commit f41529c37b4a740aa555741ca78faa55fafcb3c0
> Author: Neil Jerram <neil@ossau.uklinux.net>
> Date:   Tue Mar 2 23:23:52 2010 +0000
>
>     Make test scripts check GUILE environment variable
>     
>     So that they use the guile (or guile.exe, in the MinGW case) that was
>     just built, and not just any guile that can be found in the PATH.

The ‘TESTS_ENVIRONMENT’ variable in ‘test-suite/standalone/Makefile.am’
normally ensures that tests are run with the just-built guile, when run
with ‘make check’.

Thanks,
Ludo’.

Re: [Guile-commits] GNU Guile branch, wip-1-8-mingw-build, updated. release_1-8-7-22-g7edad77

[Neil Jerram]

ludo@gnu.org (Ludovic Courtès) writes:

> Hi Neil,
>
> "Neil Jerram" <neil@ossau.uklinux.net> writes:
>
>> commit f41529c37b4a740aa555741ca78faa55fafcb3c0
>> Author: Neil Jerram <neil@ossau.uklinux.net>
>> Date:   Tue Mar 2 23:23:52 2010 +0000
>>
>>     Make test scripts check GUILE environment variable
>>     
>>     So that they use the guile (or guile.exe, in the MinGW case) that was
>>     just built, and not just any guile that can be found in the PATH.
>
> The ‘TESTS_ENVIRONMENT’ variable in ‘test-suite/standalone/Makefile.am’
> normally ensures that tests are run with the just-built guile, when run
> with ‘make check’.

Thanks.  I'll look into this more carefully then.

     Neil

Re: [Guile-commits] GNU Guile branch, wip-1-8-mingw-build, updated. release_1-8-7-22-g7edad77

[Neil Jerram]

Neil Jerram <neil@ossau.uklinux.net> writes:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hi Neil,
>>
>> "Neil Jerram" <neil@ossau.uklinux.net> writes:
>>
>>> commit f41529c37b4a740aa555741ca78faa55fafcb3c0
>>> Author: Neil Jerram <neil@ossau.uklinux.net>
>>> Date:   Tue Mar 2 23:23:52 2010 +0000
>>>
>>>     Make test scripts check GUILE environment variable
>>>     
>>>     So that they use the guile (or guile.exe, in the MinGW case) that was
>>>     just built, and not just any guile that can be found in the PATH.
>>
>> The ‘TESTS_ENVIRONMENT’ variable in ‘test-suite/standalone/Makefile.am’
>> normally ensures that tests are run with the just-built guile, when run
>> with ‘make check’.
>
> Thanks.  I'll look into this more carefully then.

FWIW, the problem was the ".exe" extension that the MinGW cross-build
adds to generated executables.  On Linux, even if you have Wine
installed, so that NAME.exe is runnable, and even if NAME.exe is in the
PATH, the shell won't find NAME.exe if you ask it for NAME.

(When compiling on Windows I would guess that there isn't this problem.
CMD.EXE will certainly find NAME.exe, and I can imagine that the MSYS
shell has been patched to do that too.)

But anyway, following more careful thinking and feedback from the
"Reconsideration of MinGW" thread, I think that that method of
cross-building (i.e. with a cross-compiler and Wine on Linux) is pretty
unfruitful and I don't propose to continue it.

I'll leave the wip-1-8-mingw-build branch in the repository, in case
it's of interest, and because I don't know if branches can be deleted.
Is there a nice way of marking a branch as obsolete/historical, or of
adding an explanatory note to it?

Regards,
     Neil

Re: [Guile-commits] GNU Guile branch, wip-1-8-mingw-build, updated. release_1-8-7-22-g7edad77

[Andy Wingo]

On Fri 26 Mar 2010 01:31, Neil Jerram <neil@ossau.uklinux.net> writes:

> Neil Jerram <neil@ossau.uklinux.net> writes:
>
> But anyway, following more careful thinking and feedback from the
> "Reconsideration of MinGW" thread, I think that that method of
> cross-building (i.e. with a cross-compiler and Wine on Linux) is pretty
> unfruitful and I don't propose to continue it.

We have a cross-compilation problem in general right now, no?

Thinking a little about this, I would think that you would need a C
cross-compiler, and a Guile cross-compiler. So Guile's build needs a way
to specify a Guile to use during the build process.

> I'll leave the wip-1-8-mingw-build branch in the repository, in case
> it's of interest, and because I don't know if branches can be deleted.

To delete, git push origin :wip-1-8-mingw-build. (I'm not suggesting
that the branch be deleted.)

> Is there a nice way of marking a branch as obsolete/historical, or of
> adding an explanatory note to it?

I don't know. It would only be for purposes of gitweb/cgit, I don't
think git has this concept.

Andy
-- 
http://wingolog.org/

Re: [Guile-commits] GNU Guile branch, wip-1-8-mingw-build, updated. release_1-8-7-22-g7edad77

[Thien-Thi Nguyen]

() Andy Wingo <wingo@pobox.com>
() Fri, 26 Mar 2010 13:07:24 +0100

   On Fri 26 Mar 2010 01:31, Neil Jerram <neil@ossau.uklinux.net> writes:

   > Is there a nice way of marking a branch as obsolete/historical, or of
   > adding an explanatory note to it?

   I don't know. It would only be for purposes of gitweb/cgit, I don't
   think git has this concept.

Perhaps "git tag" with some kind of conventional prefix?  E.g.,

$ { date -u +"%F %T UTC" ; echo ; } > TMP
$ cat >>TMP <<EOF
This branch is live|dead|zombified|historic|pickled|putrescent|etc.
We keep it around because <explanation>.
If you delete it, someone might complain.
If you add to it, you probably are confused.
EOF
$ git tag -F TMP BRANCH-NAME-nb

This way one can easily ignore *-nb tags.  Using a suffix ensures
that the tag hierarchy mirrors the branch hierarchy (if any).

thi

Re: [Guile-commits] GNU Guile branch, wip-1-8-mingw-build, updated. release_1-8-7-22-g7edad77

[Neil Jerram]

Andy Wingo <wingo@pobox.com> writes:

> We have a cross-compilation problem in general right now, no?

Not that I'm aware of; at least not for branch_release-1-8.  I think the
problems that drove me to conclude that MinGW cross-compilation isn't
productive are all Windows-specific, to do with differences between the
emulated build environment and a real Windows environment.

> Thinking a little about this, I would think that you would need a C
> cross-compiler, and a Guile cross-compiler. So Guile's build needs a way
> to specify a Guile to use during the build process.

We have this: GUILE_FOR_BUILD.

However, that prompts me to realize that perhaps I'm not really
addressing your question properly.  Because for my MinGW/Wine build I
actually had to suppress the use of GUILE_FOR_BUILD (see [1]).  So
perhaps what I've been doing isn't actually cross-compiling in the sense
that you're thinking.

[1] http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commit;h=c9e1f32768232495d1452a45110115ac7c035acd

>> I'll leave the wip-1-8-mingw-build branch in the repository, in case
>> it's of interest, and because I don't know if branches can be deleted.
>
> To delete, git push origin :wip-1-8-mingw-build. (I'm not suggesting
> that the branch be deleted.)

Ah yes, thanks.

Regards,
       Neil

Re: [Guile-commits] GNU Guile branch, wip-1-8-mingw-build, updated. release_1-8-7-22-g7edad77

[Neil Jerram]

Thien-Thi Nguyen <ttn@gnuvola.org> writes:

> Perhaps "git tag" with some kind of conventional prefix?  E.g.,
>
> $ { date -u +"%F %T UTC" ; echo ; } > TMP
> $ cat >>TMP <<EOF
> This branch is live|dead|zombified|historic|pickled|putrescent|etc.
> We keep it around because <explanation>.
> If you delete it, someone might complain.
> If you add to it, you probably are confused.
> EOF
> $ git tag -F TMP BRANCH-NAME-nb

That's great, thanks.

I skipped the date, because git tags are dated anyway.  And I preferred
a prefix "branch-notes/" than a suffix "-nb".

I think the result works very well in the web interface (at least
gitweb, I haven't tried cgit yet).

Regards,
        Neil