git build problem on Pi

>  
> I have a new Raspberry Pi and want to compile the Cog Spur VM.
>
> I fetched the latest from SVN (never mind GitHub for now, I'll do
> that soon):
>
>   $ svn co http://squeakvm.org/svn/squeak/branches/Cog
>
> Then I do a build:
>
>   pi@raspberrypi:~/squeak/SVN-
> Cog/Cog/build.linux32ARM/squeak.cog.spur/build $ ./mvm
>   clean? 
>   /home/pi/squeak/SVN-Cog/Cog/spursrc
>   /home/pi/squeak/SVN-Cog/Cog/src/plugins
>   checking sanity of generated src directory... okay
>   checking build system type... armv7l-unknown-linux-gnu
>   checking host system type... armv7l-unknown-linux-gnu
>   
>   Configuring Squeak  (.-) for armv7l-linux-gnu
>   
>   checking whether make sets $(MAKE)... yes
>   checking for gcc... gcc -march=armv6 -mfpu=vfp -mfloat-abi=hard
>   checking for C compiler default output file name... configure:
> error: C compiler cannot create executables
>   See `config.log' for more details.
>   make: *** No rule to make target 'install-squeak'.  Stop.
>
> Does anyone recognize this?

>  
> On Thu, 2016-06-23 at 21:49 -0400, David T. Lewis wrote:
> > ??
> > I have a new Raspberry Pi and want to compile the Cog Spur VM.
> >
> > I fetched the latest from SVN (never mind GitHub for now, I'll do
> > that soon):
> >
> > ?? $ svn co http://squeakvm.org/svn/squeak/branches/Cog
> >
> > Then I do a build:
> >
> > ?? pi@raspberrypi:~/squeak/SVN-
> > Cog/Cog/build.linux32ARM/squeak.cog.spur/build $ ./mvm
> > ?? clean???
> > ?? /home/pi/squeak/SVN-Cog/Cog/spursrc
> > ?? /home/pi/squeak/SVN-Cog/Cog/src/plugins
> > ?? checking sanity of generated src directory... okay
> > ?? checking build system type... armv7l-unknown-linux-gnu
> > ?? checking host system type... armv7l-unknown-linux-gnu
> > ????
> > ?? Configuring Squeak????(.-) for armv7l-linux-gnu
> > ????
> > ?? checking whether make sets $(MAKE)... yes
> > ?? checking for gcc... gcc -march=armv6 -mfpu=vfp -mfloat-abi=hard
> > ?? checking for C compiler default output file name... configure:
> > error: C compiler cannot create executables
> > ?? See `config.log' for more details.
> > ?? make: *** No rule to make target 'install-squeak'.????Stop.
> >
> > Does anyone recognize this?
>
> Yes, I ran into it as well... the build is hard-coded to build for the
> ARMv6 of the original Pi. ??Remove the line with the compiler flags??"-
> march=armv6 -mfpu=vfp -mfloat-abi=hard" in mvm. ??That fixed the issue
> for me for ARMv7 builds.

> On 23-06-2016, at 7:35 PM, David T. Lewis <[hidden email]> wrote:
>
>
> On Thu, Jun 23, 2016 at 10:19:23PM -0400, Phil (list) wrote:
>> {snip}
>> Yes, I ran into it as well... the build is hard-coded to build for the
>> ARMv6 of the original Pi. ??Remove the line with the compiler flags??"-
>> march=armv6 -mfpu=vfp -mfloat-abi=hard" in mvm. ??That fixed the issue
>> for me for ARMv7 builds.
>
> Phil,
>
> Brilliant! I removed the -march=armv6 and it compiles now.\

> On 23-06-2016, at 7:13 PM, Ben Coman <[hidden email]> wrote:
>
>
>
> On Fri, Jun 24, 2016 at 5:37 AM, Bob Westergaard <[hidden email]> wrote:
>
> On Thu, Jun 23, 2016 at 12:54 PM, tim Rowledge <[hidden email]> wrote:
> > What did I miss?
>
> I believe this can happen if you don't *first* run
> scripts/updateSCCSVersions after you clone the repository:
>
>     https://github.com/OpenSmalltalk/vm#important-notice-for-developers
>
> Regards,
> -- Bob
>
> Could mvm be made to look for signs that this has been run and output a warning if it hasn't?
> cheers -ben

>  
>
> > On 23-06-2016, at 7:35 PM, David T. Lewis <[hidden email]>
> > wrote:
> >
> >
> > On Thu, Jun 23, 2016 at 10:19:23PM -0400, Phil (list) wrote:
> > > {snip}
> > > Yes, I ran into it as well... the build is hard-coded to build
> > > for the
> > > ARMv6 of the original Pi. ??Remove the line with the compiler
> > > flags??"-
> > > march=armv6 -mfpu=vfp -mfloat-abi=hard" in mvm. ??That fixed the
> > > issue
> > > for me for ARMv7 builds.
> >
> > Phil,
> >
> > Brilliant! I removed the -march=armv6 and it compiles now.\
>
> That is both weird and in some sense wrong; Eliot & I use the armv6
> flag so far as  I know and don’t have this issue. I *did* have this
> problem a very long time ago though. The question is whether I can
> find any evidence of what I did to get  past it…
>

> The Linux world decided a while back that ARMv7 was the minimum for
> hard float but then the rpi became a thing with its ARMv6 which,
> unlike
> many/most other versions of the v6, included hard float.  So look at
> it
> more as the Linux world viewing ARMv6 as being unsupported like the
> Intel 486 or older (I think they even bumped that up to Pentium
> recently)... i.e. it's unsupported by default on modern distros, but
> of
> course you can still build a custom distro that supports it as they
> did
> for the Pi.  So this puts the original Pi in the odd position of
> being
> unsupported by any of the armhf distros where the Pi 2 and later can
> run most of them.  But running a non-Raspberry armhf distro likely
> also
> means that you have this issue of not being able to build ARMv6
> binaries.

>
>
> > On 23-06-2016, at 7:35 PM, David T. Lewis <[hidden email]> wrote:
> >
> >
> > On Thu, Jun 23, 2016 at 10:19:23PM -0400, Phil (list) wrote:
> >> {snip}
> >> Yes, I ran into it as well... the build is hard-coded to build for the
> >> ARMv6 of the original Pi. ??Remove the line with the compiler flags??"-
> >> march=armv6 -mfpu=vfp -mfloat-abi=hard" in mvm. ??That fixed the issue
> >> for me for ARMv7 builds.
> >
> > Phil,
> >
> > Brilliant! I removed the -march=armv6 and it compiles now.\
>
> That is both weird and in some sense wrong; Eliot & I use the armv6 flag so far as  I know and don???t have this issue. I *did* have this problem a very long time ago though. The question is whether I can find any evidence of what I did to get  past it???
>
> First thing, try `sudo ./mvm`. If you???re using xrdp to connect to your Pi it makes some odd things happen to do with permissions.
>

>  
> On Thu, 2016-06-23 at 19:55 -0700, tim Rowledge wrote:
> > ??
> >
> > > On 23-06-2016, at 7:35 PM, David T. Lewis <[hidden email]>
> > > wrote:
> > >
> > >
> > > On Thu, Jun 23, 2016 at 10:19:23PM -0400, Phil (list) wrote:
> > > > {snip}
> > > > Yes, I ran into it as well... the build is hard-coded to build
> > > > for the
> > > > ARMv6 of the original Pi. ??Remove the line with the compiler
> > > > flags??"-
> > > > march=armv6 -mfpu=vfp -mfloat-abi=hard" in mvm. ??That fixed the
> > > > issue
> > > > for me for ARMv7 builds.
> > >
> > > Phil,
> > >
> > > Brilliant! I removed the -march=armv6 and it compiles now.\
> >
> > That is both weird and in some sense wrong; Eliot & I use the armv6
> > flag so far as????I know and don???t have this issue. I *did* have this
> > problem a very long time ago though. The question is whether I can
> > find any evidence of what I did to get????past it???
> >
>
> IIRC, it has to do with the build of gcc that is installed for (most?)
> ARMv7 distros. ??Are you and Elliot using an armel or armhf based
> installs or just the stock rpi install (which is ARMv6 hf I think)?
> ??Most of the ARM world (with the notable exception of rpi) is running
> armhf these days which is where the problem seems to be (i.e. I was
> able to build using the shipped mvm as-is on armel, but not armhf)
>

>  
> On Thu, 2016-06-23 at 23:52 -0400, Phil (list) wrote:
> > The Linux world decided a while back that ARMv7 was the minimum for
> > hard float but then the rpi became a thing with its ARMv6 which,
> > unlike
> > many/most other versions of the v6, included hard float. ??So look at
> > it
> > more as the Linux world viewing ARMv6 as being unsupported like the
> > Intel 486 or older (I think they even bumped that up to Pentium
> > recently)... i.e. it's unsupported by default on modern distros, but
> > of
> > course you can still build a custom distro that supports it as they
> > did
> > for the Pi. ??So this puts the original Pi in the odd position of
> > being
> > unsupported by any of the armhf distros where the Pi 2 and later can
> > run most of them. ??But running a non-Raspberry armhf distro likely
> > also
> > means that you have this issue of not being able to build ARMv6
> > binaries.
>
> Just thought of a possibly better way to explain this for anyone who
> remembers the bad old days: remember how great it was when the Intel
> 486 came out and you could assume anyone running on a 486 had hardware
> floating point? ??Then the 486SX with disabled FP came out and screwed
> that assumption up. ??The Pi 1 was essentially the reverse of that: a
> 386 with a built-in 387 which became wildly popular... not what the
> Linux world was expecting.

> On Jun 23, 2016, at 6:49 PM, David T. Lewis <[hidden email]> wrote:
>
> I have a new Raspberry Pi and want to compile the Cog Spur VM.
>
> I fetched the latest from SVN (never mind GitHub for now, I'll do that soon):
>
>  $ svn co http://squeakvm.org/svn/squeak/branches/Cog
>
> Then I do a build:
>
>  pi@raspberrypi:~/squeak/SVN-Cog/Cog/build.linux32ARM/squeak.cog.spur/build $ ./mvm
>  clean?
>  /home/pi/squeak/SVN-Cog/Cog/spursrc
>  /home/pi/squeak/SVN-Cog/Cog/src/plugins
>  checking sanity of generated src directory... okay
>  checking build system type... armv7l-unknown-linux-gnu
>  checking host system type... armv7l-unknown-linux-gnu
>
>  Configuring Squeak  (.-) for armv7l-linux-gnu
>
>  checking whether make sets $(MAKE)... yes
>  checking for gcc... gcc -march=armv6 -mfpu=vfp -mfloat-abi=hard
>  checking for C compiler default output file name... configure: error: C compiler cannot create executables
>  See `config.log' for more details.
>  make: *** No rule to make target 'install-squeak'.  Stop.
>
> Does anyone recognize this?
>
> Googling for "compiler cannot create executables" provides lots of random
> advice, but I don't see a file permissions problem and most of the rest
> of the advice looks questionable.
>
> The config.log has this (possibly unrelated):
>
>  gcc: error: unrecognized command line option '-V'
>  gcc: fatal error: no input files
>  compilation terminated.
>
> That looks like the same gcc version issue I had with building Spur on
> my Ubuntu laptop. I had thought it might be easier to just buy a $35
> Raspberry Pi rather than fix the autotools configure, but maybe not.
>
> Are other people seeing these issues, or is it just me?
>
> Compiling and running an interpreter VM on the same Raspberry Pi works
> fine, so I am assuming this is either an autotools issue or something
> related to gcc version for the cog/spur build.
>
> I am attaching the config.log from the ./mvm session in case it helps.
>
> Raspberry Pi OS version information:
>
>  pi@raspberrypi:~/squeak/SVN-Cog/Cog/build.linux32ARM/squeak.cog.spur/build $ cat /proc/version
>  Linux version 4.1.19-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #858 SMP Tue Mar 15 15:56:00 GMT 2016
>
> Thanks,
> Dave
>
> <config.log>

> On Jun 24, 2016, at 6:36 AM, David T. Lewis <[hidden email]> wrote:
>
>
>> On Thu, Jun 23, 2016 at 11:52:48PM -0400, Phil (list) wrote:
>>
>>> On Thu, 2016-06-23 at 19:55 -0700, tim Rowledge wrote:
>>> ??
>>>
>>>> On 23-06-2016, at 7:35 PM, David T. Lewis <[hidden email]>
>>>> wrote:
>>>>
>>>>
>>>>> On Thu, Jun 23, 2016 at 10:19:23PM -0400, Phil (list) wrote:
>>>>> {snip}
>>>>> Yes, I ran into it as well... the build is hard-coded to build
>>>>> for the
>>>>> ARMv6 of the original Pi. ??Remove the line with the compiler
>>>>> flags??"-
>>>>> march=armv6 -mfpu=vfp -mfloat-abi=hard" in mvm. ??That fixed the
>>>>> issue
>>>>> for me for ARMv7 builds.
>>>>
>>>> Phil,
>>>>
>>>> Brilliant! I removed the -march=armv6 and it compiles now.\
>>>
>>> That is both weird and in some sense wrong; Eliot & I use the armv6
>>> flag so far as????I know and don???t have this issue. I *did* have this
>>> problem a very long time ago though. The question is whether I can
>>> find any evidence of what I did to get????past it???
>>
>> IIRC, it has to do with the build of gcc that is installed for (most?)
>> ARMv7 distros. ??Are you and Elliot using an armel or armhf based
>> installs or just the stock rpi install (which is ARMv6 hf I think)?
>> ??Most of the ARM world (with the notable exception of rpi) is running
>> armhf these days which is where the problem seems to be (i.e. I was
>> able to build using the shipped mvm as-is on armel, but not armhf)
>
> Also regarding the gcc version, it looks like the configure script is
> getting rather old. I see this in my config log:
>
> g++: error: unrecognized command line option '-V'
>
> This apparently had no ill effect on the build for Pi, but it's important
> because I think that the -V option has gone away in recent gcc versions,
> and that is what prevented me from being able to build Cog/Spur on my
> Intel Ubuntu laptop. I ran out of patience trying to rebuild the
> autotools configuration, and that is what finally prompted me to buy
> this Raspberry Pi :-)

> On Jun 24, 2016, at 6:36 AM, David T. Lewis <[hidden email]> wrote:
>
>
>> On Thu, Jun 23, 2016 at 11:52:48PM -0400, Phil (list) wrote:
>>
>>> On Thu, 2016-06-23 at 19:55 -0700, tim Rowledge wrote:
>>> ??
>>>
>>>> On 23-06-2016, at 7:35 PM, David T. Lewis <[hidden email]>
>>>> wrote:
>>>>
>>>>
>>>>> On Thu, Jun 23, 2016 at 10:19:23PM -0400, Phil (list) wrote:
>>>>> {snip}
>>>>> Yes, I ran into it as well... the build is hard-coded to build
>>>>> for the
>>>>> ARMv6 of the original Pi. ??Remove the line with the compiler
>>>>> flags??"-
>>>>> march=armv6 -mfpu=vfp -mfloat-abi=hard" in mvm. ??That fixed the
>>>>> issue
>>>>> for me for ARMv7 builds.
>>>>
>>>> Phil,
>>>>
>>>> Brilliant! I removed the -march=armv6 and it compiles now.\
>>>
>>> That is both weird and in some sense wrong; Eliot & I use the armv6
>>> flag so far as????I know and don???t have this issue. I *did* have this
>>> problem a very long time ago though. The question is whether I can
>>> find any evidence of what I did to get????past it???
>>
>> IIRC, it has to do with the build of gcc that is installed for (most?)
>> ARMv7 distros. ??Are you and Elliot using an armel or armhf based
>> installs or just the stock rpi install (which is ARMv6 hf I think)?
>> ??Most of the ARM world (with the notable exception of rpi) is running
>> armhf these days which is where the problem seems to be (i.e. I was
>> able to build using the shipped mvm as-is on armel, but not armhf)
>
> Also regarding the gcc version, it looks like the configure script is
> getting rather old. I see this in my config log:
>
> g++: error: unrecognized command line option '-V'
>
> This apparently had no ill effect on the build for Pi, but it's important
> because I think that the -V option has gone away in recent gcc versions,
> and that is what prevented me from being able to build Cog/Spur on my
> Intel Ubuntu laptop. I ran out of patience trying to rebuild the
> autotools configuration, and that is what finally prompted me to buy
> this Raspberry Pi :-)

> On 23-06-2016, at 2:37 PM, Bob Westergaard <[hidden email]> wrote:
>
>
> On Thu, Jun 23, 2016 at 12:54 PM, tim Rowledge <[hidden email]> wrote:
>> What did I miss?
>
> I believe this can happen if you don't *first* run
> scripts/updateSCCSVersions after you clone the repository:
>
>    https://github.com/OpenSmalltalk/vm#important-notice-for-developers