Santiago Vila wrote:
> The message about jobserver disappeared when I disabled parallel build.
> I guess it is some kind of Makefile bug.
The message was:
warning: jobserver unavailable: using -j1.
To me, this sounds like 'make' could not create a jobserver, because the
jobservers rely on named
Santiago Vila wrote:
> And yes, I assume it already works in maintainer mode, but only if mcs is in
> PATH.
The point of distributing the csharpexec-test.exe as a binary is to
be able to have C# support in 'msgunfmt' even when the environment
contains a C# execution engine but no C# compiler.
Br
Santiago Vila wrote:
> For completeness: Would it make sense to add an indication, somewhere, about
> the way
> to create the .exe from the .cs? This is something that surely everybody using
> mono knows, but I had to search for it. I guess this would be correct:
>
> mcs -out:csharpexec-test.exe
Adrian Bunk wrote:
> In practice the main usecase for Mono on Linux is porting of
> proprietary Windows programs to Linux.
>
> > and also isn't it useful for building mobile apps [2]?
>
> "Build cross-platform Android & iOS apps using C# and .NET in Visual
> Studio on Windows and macOS."[3]
>
Santiago Vila wrote:
> Summary: There is no source for gettext-tools/m4/csharpexec-test.exe.
Fixed through
https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=1bda6586b87f7e258c16bd0dca5c43048b9920a9
Thanks for the report.
> Note: The Debian package disabled the mono stuff in vers
Hi Santiago, Samuel,
> The upload of gettext 0.21 for Debian unstable has made package "dasher",
> maintained by Samuel Thibault (in Cc), not to build anymore, as reported here
> by Lucas Nussbaum:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978315
>
> We are not sure where is exactly
Adrian Bunk wrote:
> For reproducing and my tiny testcase I was using
> gcc (Debian 7.1.0-13) 7.1.0
> from Debian unstable - that is GCC 7.2 release candidate 2
> with minimal Debian patching.
OK thanks.
Now about your test case: It is not valid C to try to compile just an
expression.
=
Hi Adrian,
Could you please give the complete output of "gcc --version"?
Given that [1] references an URL that contains the string
'gcc7-20170126' whereas gcc 7 was released on 2017-05-02 [2],
it could be that the report is about a gcc prerelease that
came 3 months before the gcc 7 release.
Brun
Hi Sylvain,
> I received the bug report below when compiling GNU FreeDink on
> Debian/kFreeBSD and Debian/Hurd.
>
> It seems that there's an issue with install-reloc:
> https://buildd.debian.org/status/fetch.php?pkg=freedink&arch=kfreebsd-amd64&ver=1.08.20120427-1&stamp=1335561117
> https://build
et me know if this fixes the Freedink
builds on GNU/kFreeBSD or not.
2012-05-01 Bruno Haible
relocatable-prog: Enable ELF ORIGIN trick also on GNU/kFreeBSD.
* m4/relocatable.m4 (gl_RELOCATABLE_BODY): Treat kFreeBSD like Linux.
* build-aux/reloc-ldflags: Likewise.
S
Jim Meyering wrote:
> # Test with seekable stdin; the followon process must see remaining data.
> -cat < ${p}in.tmp
> +cat < ${p}in.tmp
This can be simplified to:
tr @ '\177' < ${p}in.tmp
Bruno
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscr
Jim Meyering wrote:
> Thanks for the suggestion. It looks like a good one.
The suggestion also applies to the 'md5' module, after which the 'sha1' module
is modeled.
But if you apply the suggestion to both the sha1 and md5 modules, we get
an additional difference to glibc code.
OTOH, Simon hims
12 matches
Mail list logo
