Re: [Tinycc-devel] TinyCC 0.9.26 released
On Fri, Feb 15, 2013 at 03:17:46PM +0100, Thomas Preud'homme wrote:
Greetings everybody,
it is my pleasure to finally announce the release of TinyCC 0.9.26. This
release has been longer than previously to come along but it's finally here.
Bravo!
At least for future reference, you should have given an URL to download the
source code
(e.g. as a .tar.gz file) and preferably, some hash code (e.g. MD5 or SHA1) of
it.
Cheers
PS I'l following the list occasionally, and I am not able to find easily that
URL.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basileatstarynkevitchdotnet mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] TinyCC 0.9.26 released
Greetings everybody, it is my pleasure to finally announce the release of TinyCC 0.9.26. This release has been longer than previously to come along but it's finally here. Bravo! You did a very good job for the release! At least for future reference, you should have given an URL to download the source code (e.g. as a .tar.gz file) and preferably, some hash code (e.g. MD5 or SHA1) of it. Same for me. I found http://download.savannah.gnu.org/releases/tinycc/ but I'm not sure that's the right place. A GPG signature would be welcome too :) One more little thing: the http://tinycc.org/ web site (that redirects to http://bellard.org/tcc/) does not mention the last release. Maybe the website could be updated to mention that tcc is still maintained and a new version was released? Regards, Didier signature.asc Description: PGP signature ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] TinyCC 0.9.26 released
At least for future reference, you should have given an URL to download the source code (e.g. as a .tar.gz file) and preferably, some hash code (e.g. MD5 or SHA1) of it. Same for me. I found http://download.savannah.gnu.org/releases/tinycc/ but I'm not sure that's the right place. A GPG signature would be welcome too :) Right right. When I sent the email the binaries were not uploaded yet. So here are some checksum: MD5: 5fb28e4abc830c46a7f54c1f637fb25d SHA1: 7110354d3637d0e05f43a006364c897248aed5d0 SHA256: 521e701ae436c302545c3f973a9c9b7e2694769c71d9be10f70a2460705b6d71 See attached the corresponding gpg signature. Thanks! One more little thing: the http://tinycc.org/ web site (that redirects to http://bellard.org/tcc/) does not mention the last release. Maybe the website could be updated to mention that tcc is still maintained and a new version was released? This website belongs to Fabrice Bellard and as such neither Grischka nor me can modify it. I sent an email to Fabrice just after the announce to notify him about the release and ask him to update his website. I haven't got any answer yet so I guess he simply didn't read the mail yet. OK, that's fine. Regards, Didier signature.asc Description: PGP signature ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] TinyCC 0.9.26 released
Le samedi 16 février 2013 10:42:17, Thomas Preud'homme a écrit : So here are some checksum: MD5: 5fb28e4abc830c46a7f54c1f637fb25d SHA1: 7110354d3637d0e05f43a006364c897248aed5d0 SHA256: 521e701ae436c302545c3f973a9c9b7e2694769c71d9be10f70a2460705b6d71 See attached the corresponding gpg signature. Sorry, I should have done a detached signature. I uploaded the detached signature and a file tcc-0.9.26.tar.bz2.checksums with these 3 checksums to the download area in savannah. Best regards, Thomas signature.asc Description: This is a digitally signed message part. ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
[Tinycc-devel] What C version tcc is supposed to implement?
tcc_define_symbol(s, __STDC_VERSION__, 199901L);
This define pretends it is ISO/IEC 9899:1999 (E)
Because __STDC_VERSION__ is set to 199901L
This code should be legal:
#include stdio.h
#include wchar.h
int main()
{
#if defined(__STDC_VERSION__) (__STDC_VERSION__ = 199901L)
wchar_t* s = LABCDEFGHIJKLMNOPQRSTUVWXYZ;
char* p = (char*)s;
printf(%x %x %x %x\n, p[0],p[1],p[2],p[3]);
printf(%x %x %x %x\n, p[4],p[5],p[6],p[7]);
wprintf(LHello World\n);
#else
printf(Not an ISO C compiler\n);
#endif
}
It compiles with no error on RPi, treats wchar_t as an uint32_t (as on
Linux) yet does nothing with wprintf!
jullien@sims ~ $ tcc foo.c -o foo ./foo
41 0 0 0
42 0 0 0
jullien@sims ~ $
If tcc is 199901L, as said in ISO/IEC 9899:1999 (E) it should also define:
_ _STDC_ _ The integer constant 1, intended to indicate a conforming
implementation.
_ _STDC_HOSTED_ _ The integer constant 1 if the implementation is a hosted
implementation or the integer constant 0 if it is not.
_ _STDC_VERSION_ _ The integer constant 199901L
_ _STDC_IEC_559_ _ The integer constant 1, intended to indicate conformance
to the
specifications in annex F (IEC 60559 floating-point arithmetic).
_ _STDC_IEC_559_COMPLEX_ _ The integer constant 1, intended to indicate
adherence to the specifications in informative annex G (IEC 60559
compatible complex arithmetic).
_ _STDC_ISO_10646_ _ An integer constant of the form mmL (for example,
199712L), intended to indicate that values of type wchar_t are the
coded representations of the characters defined by ISO/IEC 10646, along
with all amendments and technical corrigenda as of the specified year and
month.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
[Tinycc-devel] Can't git clone anymore
c:\tmpgit clone git://repo.or.cz/tinycc.git Cloning into 'tinycc'... remote: Counting objects: 5037, done. remote: Compressing objects: 100% (1558/1558), done. remote: Total 5037 (delta 3427), reused 5037 (delta 3427) Receiving objects: 100% (5037/5037), 2.30 MiB | 404 KiB/s, done. Resolving deltas: 100% (3427/3427), done. warning: remote HEAD refers to nonexistent ref, unable to checkout. And tinycc contains only .git Same with mob: c:\tmpgit clone -b mob git://repo.or.cz/tinycc.git Cloning into 'tinycc'... remote: Counting objects: 5037, done. remote: Compressing objects: 100% (1558/1558), done. remote: Total 5037 (delta 3427), reused 5037 (delta 3427)Receiving objects Receiving objects: 100% (5037/5037), 2.30 MiB | 404 KiB/s, done. Resolving deltas: 100% (3427/3427), done. warning: Remote branch mob not found in upstream origin, using HEAD instead warning: remote HEAD refers to nonexistent ref, unable to checkout. Same thing from linux box jullien@sims ~/tmp $ git clone -b mob git://repo.or.cz/tinycc.git Cloning into 'tinycc'... fatal: Remote branch mob not found in upstream origin ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] What C version tcc is supposed to implement?
Hello Christian,
Am 16.02.2013 12:04, schrieb Christian Jullien:
tcc_define_symbol(s, __STDC_VERSION__, 199901L);
This define pretends it is ISO/IEC 9899:1999 (E)
Strictly speaking that's optimistic, because it also depends on the C
library on which tcc has no influence (some embedded C libs can be
configured to not support wchar for instance). But in your case it's
simply an error on your part.
Because __STDC_VERSION__ is set to 199901L
This code should be legal:
It's legal, but doesn't do what you want:
int main()
{
When a program is started stdout/err/in have no orientation yet. The
first input/output operation determines which orientation it gets ...
#if defined(__STDC_VERSION__) (__STDC_VERSION__ = 199901L)
wchar_t* s = LABCDEFGHIJKLMNOPQRSTUVWXYZ;
char* p = (char*)s;
printf(%x %x %x %x\n, p[0],p[1],p[2],p[3]);
... and printf is byte-oriented, so stdout will from now on be
byte-oriented, and the string is output...
printf(%x %x %x %x\n, p[4],p[5],p[6],p[7]);
... stdout is byte-oriented, printf is byte-oriented, so the string is
output ...
wprintf(LHello World\n);
... and this doesn't work, because stdout is byte-oriented, but wprintf
requires a stream that isn't byte-oriented. If you had checked for
errors you would have seen one. Once a stream has an orientation it
can't be switched anymore. Remove the printf's and leave only wprintf
and it works. Alternatively if you want to output wide characters on a
byte-oriented stream use printf and %ls. For the whole background see
fwide(3) and wprintf(3).
Ciao,
Michael.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] What C version tcc is supposed to implement?
Thank you Michael,
I'm really sorry, my intention was not that someone tried to debug this
silly program.
The purpose of this small program was to illustrate that I don't know what C
version tcc is supposed to implement, with which feature.
I admit that this quick and dirty program is odd.
If __STDC_VERSION__ is set to 199901L we can assume that other features of
ISO/IEC 9899:1999 (E) are present which it not true.
Christian
-Original Message-
From: tinycc-devel-bounces+eligis=orange...@nongnu.org
[mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of
Michael Matz
Sent: samedi 16 février 2013 19:58
To: tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] What C version tcc is supposed to implement?
Hello Christian,
Am 16.02.2013 12:04, schrieb Christian Jullien:
tcc_define_symbol(s, __STDC_VERSION__, 199901L);
This define pretends it is ISO/IEC 9899:1999 (E)
Strictly speaking that's optimistic, because it also depends on the C
library on which tcc has no influence (some embedded C libs can be
configured to not support wchar for instance). But in your case it's simply
an error on your part.
Because __STDC_VERSION__ is set to 199901L This code should be legal:
It's legal, but doesn't do what you want:
int main()
{
When a program is started stdout/err/in have no orientation yet. The first
input/output operation determines which orientation it gets ...
#if defined(__STDC_VERSION__) (__STDC_VERSION__ = 199901L)
wchar_t* s = LABCDEFGHIJKLMNOPQRSTUVWXYZ;
char* p = (char*)s;
printf(%x %x %x %x\n, p[0],p[1],p[2],p[3]);
... and printf is byte-oriented, so stdout will from now on be
byte-oriented, and the string is output...
printf(%x %x %x %x\n, p[4],p[5],p[6],p[7]);
... stdout is byte-oriented, printf is byte-oriented, so the string is
output ...
wprintf(LHello World\n);
... and this doesn't work, because stdout is byte-oriented, but wprintf
requires a stream that isn't byte-oriented. If you had checked for errors
you would have seen one. Once a stream has an orientation it can't be
switched anymore. Remove the printf's and leave only wprintf and it works.
Alternatively if you want to output wide characters on a byte-oriented
stream use printf and %ls. For the whole background see
fwide(3) and wprintf(3).
Ciao,
Michael.
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] What C version tcc is supposed to implement?
Am 16.02.2013 20:16, schrieb Christian Jullien: Thank you Michael, I'm really sorry, my intention was not that someone tried to debug this silly program. The purpose of this small program was to illustrate that I don't know what C version tcc is supposed to implement, with which feature. I admit that this quick and dirty program is odd. If __STDC_VERSION__ is set to 199901L we can assume that other features of ISO/IEC 9899:1999 (E) are present which it not true. Then you have to be a bit more specific about which features you're missing, as wchar_t's aren't. There are of course some, but usually arcane ones that even GCC doesn't implement (e.g. strict adherence to the floating point environment model, and the associated pragmas). I can tell you that tcc aims to implement c99 (when reasonably possible), so setting __STDC_VERSION__ to the value it has right now is sensible. Not necessarily all optional features of it (e.g. _Complex support is missing right now, but that's mentioned in the TODO). You cited some macros that are supposed to be set, and the state of them is: __STDC__ : set correctly __STDC_VERSION__ : set correctly __STDC_HOSTED__ : not set (incorrectly, it should probably be set to 1 given that tcc assumes a normal main() and that the rest of the provided facilities is provided by the C library not under tcc control) __STDC_IEC_559__ : Optional, correctly not set __STDC_IEC_559_COMPLEX__ : Optional, correctly not set __STDC_ISO_10646 : Optional, setting it would require quite some testing because it would have to be matched against a certain version of the 10646 standard. Not much value in doing that. So, in short, if your question was really only the subject: tcc aims to a large subset of ISO/IEC 9899:1999, hosted implementation, minus _Complex and minus IEC 559. Modulo bugs, and modulo missing features I forgot :), if you have any specific in mind, tell us. Ciao, Michael. ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] What C version tcc is supposed to implement?
So, in short, if your question was really only the subject: tcc aims to a large subset of ISO/IEC 9899:1999, hosted implementation, minus _Complex and minus IEC 559. Modulo bugs, and modulo missing features I forgot :), if you have any specific in mind, tell us. Yes, and you replied to my question perfectly. This is a guidance on how tcc should evolve (toward better, possibly full, ISO/IEC 9899:1999 (E) support). Having ported some of my projects on more than 100 different systems, I rely on what C macros tells me to try to have a portable source code. POSIX macros also give me hints of what I can use. autoconf + ./configure is one help but, unfortunately, it does on run on all possible system. I member the nightmare to port on Vax VMS, IBM OS390 not counting exotic systems like BeOS, SkyOS, QNX ... Christian -Original Message- From: tinycc-devel-bounces+eligis=orange...@nongnu.org [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Michael Matz Sent: samedi 16 février 2013 21:18 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] What C version tcc is supposed to implement? Am 16.02.2013 20:16, schrieb Christian Jullien: Thank you Michael, I'm really sorry, my intention was not that someone tried to debug this silly program. The purpose of this small program was to illustrate that I don't know what C version tcc is supposed to implement, with which feature. I admit that this quick and dirty program is odd. If __STDC_VERSION__ is set to 199901L we can assume that other features of ISO/IEC 9899:1999 (E) are present which it not true. Then you have to be a bit more specific about which features you're missing, as wchar_t's aren't. There are of course some, but usually arcane ones that even GCC doesn't implement (e.g. strict adherence to the floating point environment model, and the associated pragmas). I can tell you that tcc aims to implement c99 (when reasonably possible), so setting __STDC_VERSION__ to the value it has right now is sensible. Not necessarily all optional features of it (e.g. _Complex support is missing right now, but that's mentioned in the TODO). You cited some macros that are supposed to be set, and the state of them is: __STDC__ : set correctly __STDC_VERSION__ : set correctly __STDC_HOSTED__ : not set (incorrectly, it should probably be set to 1 given that tcc assumes a normal main() and that the rest of the provided facilities is provided by the C library not under tcc control) __STDC_IEC_559__ : Optional, correctly not set __STDC_IEC_559_COMPLEX__ : Optional, correctly not set __STDC_ISO_10646 : Optional, setting it would require quite some testing because it would have to be matched against a certain version of the 10646 standard. Not much value in doing that. So, in short, if your question was really only the subject: tcc aims to a large subset of ISO/IEC 9899:1999, hosted implementation, minus _Complex and minus IEC 559. Modulo bugs, and modulo missing features I forgot :), if you have any specific in mind, tell us. Ciao, Michael. ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] Option number is ambiguous (number-footnotes, number-sections) (texi2html) (patch)
On Fri, Feb 15, 2013 at 5:42 PM, Thomas Preud'homme robo...@celest.fr wrote: Le vendredi 15 février 2013 19:14:23, Austin English a écrit : This was around before 0.9.26, but I forgot to report it: make[1]: Leaving directory `/home/austin/src/tinycc/lib' ./texi2pod.pl tcc-doc.texi tcc.pod pod2man --section=1 --center= --release= tcc.pod tcc.1 texi2html -monolithic -number tcc-doc.texi Option number is ambiguous (number-footnotes, number-sections) Try `texi2html --help' for more information. make: [tcc-doc.html] Error 2 (ignored) makeinfo tcc-doc.texi austin@aw25 ~/src/tinycc $ texi2html --version 5.0 austin@aw25 ~/src/tinycc $ uname -a Linux aw25 3.5.3-gentoo #4 SMP Wed Oct 24 21:55:24 PDT 2012 x86_64 Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux The following patch fixes it: diff --git a/Makefile b/Makefile index 705b585..9376132 100644 --- a/Makefile +++ b/Makefile @@ -300,7 +300,7 @@ endif # documentation and man page tcc-doc.html: tcc-doc.texi - -texi2html -monolithic -number $ + -texi2html -monolithic -number-sections $ tcc.1: tcc-doc.texi -$(top_srcdir)/texi2pod.pl $ tcc.pod Go ahead and commit it to the mob branch. As I said I'd like to release more often, around 1 release a year like before. Let's make the next release even better than this one :) Best regards, Thomas It fails to push: austin@debian-home:~/src/tinycc$ git push ssh://m...@repo.or.cz/srv/git/tinycc.git docfix:mob Counting objects: 5, done. Delta compression using up to 8 threads. Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 320 bytes, done. Total 3 (delta 2), reused 0 (delta 0) The mob user cannot _create_ the 'mob' branch, sorry error: hooks/update exited with error code 2 error: hook declined to update refs/heads/mob To ssh://m...@repo.or.cz/srv/git/tinycc.git ! [remote rejected] docfix - mob (hook declined) error: failed to push some refs to 'ssh://m...@repo.or.cz/srv/git/tinycc.git' may be related to the problem someone else posted of not being able to do a git pull? -- -Austin ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] Can't git clone anymore
Le samedi 16 février 2013 18:28:52, Christian Jullien a écrit : c:\tmpgit clone git://repo.or.cz/tinycc.git Cloning into 'tinycc'... remote: Counting objects: 5037, done. remote: Compressing objects: 100% (1558/1558), done. remote: Total 5037 (delta 3427), reused 5037 (delta 3427) Receiving objects: 100% (5037/5037), 2.30 MiB | 404 KiB/s, done. Resolving deltas: 100% (3427/3427), done. warning: remote HEAD refers to nonexistent ref, unable to checkout. And tinycc contains only .git Same with mob: c:\tmpgit clone -b mob git://repo.or.cz/tinycc.git Cloning into 'tinycc'... remote: Counting objects: 5037, done. remote: Compressing objects: 100% (1558/1558), done. remote: Total 5037 (delta 3427), reused 5037 (delta 3427)Receiving objects Receiving objects: 100% (5037/5037), 2.30 MiB | 404 KiB/s, done. Resolving deltas: 100% (3427/3427), done. warning: Remote branch mob not found in upstream origin, using HEAD instead warning: remote HEAD refers to nonexistent ref, unable to checkout. Same thing from linux box jullien@sims ~/tmp $ git clone -b mob git://repo.or.cz/tinycc.git Cloning into 'tinycc'... fatal: Remote branch mob not found in upstream origin Sorry, maybe I did something wrong. I'll check my history later out of curiosity but it seems mob was destroyed indeed. It should be ok now. Best regards, Thomas signature.asc Description: This is a digitally signed message part. ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] Option number is ambiguous (number-footnotes, number-sections) (texi2html) (patch)
Le samedi 16 février 2013 23:05:54, Austin English a écrit : On Fri, Feb 15, 2013 at 5:42 PM, Thomas Preud'homme robo...@celest.fr wrote: Le vendredi 15 février 2013 19:14:23, Austin English a écrit : This was around before 0.9.26, but I forgot to report it: make[1]: Leaving directory `/home/austin/src/tinycc/lib' ./texi2pod.pl tcc-doc.texi tcc.pod pod2man --section=1 --center= --release= tcc.pod tcc.1 texi2html -monolithic -number tcc-doc.texi Option number is ambiguous (number-footnotes, number-sections) Try `texi2html --help' for more information. make: [tcc-doc.html] Error 2 (ignored) makeinfo tcc-doc.texi austin@aw25 ~/src/tinycc $ texi2html --version 5.0 austin@aw25 ~/src/tinycc $ uname -a Linux aw25 3.5.3-gentoo #4 SMP Wed Oct 24 21:55:24 PDT 2012 x86_64 Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux The following patch fixes it: diff --git a/Makefile b/Makefile index 705b585..9376132 100644 --- a/Makefile +++ b/Makefile @@ -300,7 +300,7 @@ endif # documentation and man page tcc-doc.html: tcc-doc.texi - -texi2html -monolithic -number $ + -texi2html -monolithic -number-sections $ tcc.1: tcc-doc.texi -$(top_srcdir)/texi2pod.pl $ tcc.pod Go ahead and commit it to the mob branch. As I said I'd like to release more often, around 1 release a year like before. Let's make the next release even better than this one :) Best regards, Thomas It fails to push: austin@debian-home:~/src/tinycc$ git push ssh://m...@repo.or.cz/srv/git/tinycc.git docfix:mob Counting objects: 5, done. Delta compression using up to 8 threads. Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 320 bytes, done. Total 3 (delta 2), reused 0 (delta 0) The mob user cannot _create_ the 'mob' branch, sorry error: hooks/update exited with error code 2 error: hook declined to update refs/heads/mob To ssh://m...@repo.or.cz/srv/git/tinycc.git ! [remote rejected] docfix - mob (hook declined) error: failed to push some refs to 'ssh://m...@repo.or.cz/srv/git/tinycc.git' may be related to the problem someone else posted of not being able to do a git pull? Indeed. I don't remember having done anything strange but that might be possible in the excitement of the release. I'll check that later. It should be fine now. Please try again. Best regards, Thomas signature.asc Description: This is a digitally signed message part. ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
[Tinycc-devel] Page´s reboot
Congratulations all tinycc'ers for a new release !. Some one did mention again of the original site (oudated) and other talks about links, etc. Little things that helps very much to this effort. I think that better than waiting for Fabrice is just made a new page, modest but updated. For example, the dominion tinycc.com.ar (Argentina) it´s available. I know this isn't the same as .org or .net but could be better than the original-dead page. And it´s free ;-) Alejandro ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] Can't git clone anymore
Thanks Thomas, it works again now -Original Message- From: Thomas Preud'homme [mailto:robo...@celest.fr] Sent: samedi 16 février 2013 23:39 To: Christian Jullien Cc: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Can't git clone anymore Le samedi 16 février 2013 18:28:52, Christian Jullien a écrit : c:\tmpgit clone git://repo.or.cz/tinycc.git Cloning into 'tinycc'... remote: Counting objects: 5037, done. remote: Compressing objects: 100% (1558/1558), done. remote: Total 5037 (delta 3427), reused 5037 (delta 3427) Receiving objects: 100% (5037/5037), 2.30 MiB | 404 KiB/s, done. Resolving deltas: 100% (3427/3427), done. warning: remote HEAD refers to nonexistent ref, unable to checkout. And tinycc contains only .git Same with mob: c:\tmpgit clone -b mob git://repo.or.cz/tinycc.git Cloning into 'tinycc'... remote: Counting objects: 5037, done. remote: Compressing objects: 100% (1558/1558), done. remote: Total 5037 (delta 3427), reused 5037 (delta 3427)Receiving objects Receiving objects: 100% (5037/5037), 2.30 MiB | 404 KiB/s, done. Resolving deltas: 100% (3427/3427), done. warning: Remote branch mob not found in upstream origin, using HEAD instead warning: remote HEAD refers to nonexistent ref, unable to checkout. Same thing from linux box jullien@sims ~/tmp $ git clone -b mob git://repo.or.cz/tinycc.git Cloning into 'tinycc'... fatal: Remote branch mob not found in upstream origin Sorry, maybe I did something wrong. I'll check my history later out of curiosity but it seems mob was destroyed indeed. It should be ok now. Best regards, Thomas ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
