Compile on Raspberry PI 3

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Compile on Raspberry PI 3

Hercules390 - General mailing list
Hoping someone can help and point me in the right direction
 

 - Trying to compile Hercules-4.0 (Hyperion) on a Raspberry PI 3
 - Using Raspian Jessie Lite (minus the X-windows Gui, etc..) as the base OS (which I believe is a flavor of Debian)
 - I Git Clone the source
 - I apt-get install the necessary packages plus a few optional ones (bldlvlck passes all it's checks)
 - I use 1Stop to execute compile process which gets and compiles SoftFloat successfully and compiles Hercules to completion with a number of the following messages:
 

 *** Warning: This system can not link to static lib archive ../libhercs.la.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have.
*** But as you try to build a module library, libtool will still create
*** a static module, that should work as long as the dlopening application
*** is linked with the -dlopen flag to resolve symbols at runtime.

 

 Hercules will execute and start successfully but it has a number of devtypes not recognized, the most critical being 3270... it mounts the DASD successfully.  

 

 From searching and reading a number of other threads I know some people had a similar issue with libtools (linking?) performing correctly when 'uname -p" returned no value... on my system it returns "unknown" if that helps anyone.
 

 Any help is appreciated.
 

 Thanks,
 

 Steve...
 

 

Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
Additional info... I compiled with the following parms:

 configure --enable-cckd-bzip2 --enable-het-bzip2 --enable-regina-rexx --enable-optimization="-mcpu=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard"

 

 and I have also tried using:
 

 -mcpu=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard

 

 Same results either way.
 

 Steve...
 

 

 

Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list

On 3/26/2017 8:48 PM, [hidden email] [hercules-390] wrote:

>
>
> Additional info... I compiled with the following parms:
>
> configure --enable-cckd-bzip2 --enable-het-bzip2 --enable-regina-rexx
> --enable-optimization="-mcpu=cortex-a53 -mfpu=neon-fp-armv8
> -mfloat-abi=hard"
>
> and I have also tried using:
>
> -mcpu=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard
>
> Same results either way.
>
> Steve...
>
>
Steve,

Try...

Once soft3h has been compiled. (You can ^C 1Stop at this point)
Create a build directory directory
Copy sf3h directory from parent of source directory to parent of build
directory (may not be necessary if the source and build directory share
the same parent)
Run <source dir>/configure <whatever flags you like> --prefix=<run
directory>
make
make install
export PATH=$PATH:<run directory>/bin
* go to where your hercules.cnf lives.
hercules

--Ivan



[Non-text portions of this message have been removed]

Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
You can specify the configure flags on 1Stop.

On 03/26/2017 08:56 PM, Ivan Warren [hidden email] [hercules-390] wrote:

>
>
>
> On 3/26/2017 8:48 PM, [hidden email] [hercules-390] wrote:
>>
>>
>> Additional info... I compiled with the following parms:
>>
>> configure --enable-cckd-bzip2 --enable-het-bzip2 --enable-regina-rexx
>> --enable-optimization="-mcpu=cortex-a53 -mfpu=neon-fp-armv8
>> -mfloat-abi=hard"
>>
>> and I have also tried using:
>>
>> -mcpu=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard
>>
>> Same results either way.
>>
>> Steve...
>>
>>
> Steve,
>
> Try...
>
> Once soft3h has been compiled. (You can ^C 1Stop at this point)
> Create a build directory directory
> Copy sf3h directory from parent of source directory to parent of build
> directory (may not be necessary if the source and build directory share
> the same parent)
> Run <source dir>/configure <whatever flags you like> --prefix=<run
> directory>
> make
> make install
> export PATH=$PATH:<run directory>/bin
> * go to where your hercules.cnf lives.
> hercules
>
> --Ivan
>
> [Non-text portions of this message have been removed]
>
>


------------------------------------

------------------------------------

Community email addresses:
  Post message: [hidden email]
  Subscribe:    [hidden email]
  Unsubscribe:  [hidden email]
  List owner:   [hidden email]

Files and archives at:
  http://groups.yahoo.com/group/hercules-390

Get the latest version of Hercules from:
  http://www.hercules-390.org


------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/hercules-390/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/hercules-390/join
    (Yahoo! ID required)

<*> To change settings via email:
    [hidden email]
    [hidden email]

<*> To unsubscribe from this group, send an email to:
    [hidden email]

<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/

Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
In reply to this post by Hercules390 - General mailing list
Autotools is confused.  the .la file is not necessarily a static
library.  It is a shell script that builds a library.

Can you check which device managers have been built in the .libs
directory of the build directory.

On 03/26/2017 08:40 PM, [hidden email] [hercules-390] wrote:

>
>
> Hoping someone can help and point me in the right direction
>
>
> - Trying to compile Hercules-4.0 (Hyperion) on a Raspberry PI 3
>
> - Using Raspian Jessie Lite (minus the X-windows Gui, etc..) as the base
> OS (which I believe is a flavor of Debian)
>
> - I Git Clone the source
>
> - I apt-get install the necessary packages plus a few optional ones
> (bldlvlck passes all it's checks)
>
> - I use 1Stop to execute compile process which gets and compiles
> SoftFloat successfully and compiles Hercules to completion with a number
> of the following messages:
>
>
> *** Warning: This system can not link to static lib archive ../libhercs.la.
> *** I have the capability to make that library automatically link in when
> *** you link to this library.  But I can only do this if you have a
> *** shared version of the library, which you do not appear to have.
> *** But as you try to build a module library, libtool will still create
> *** a static module, that should work as long as the dlopening application
> *** is linked with the -dlopen flag to resolve symbols at runtime.
>
>
> Hercules will execute and start successfully but it has a number of
> devtypes not recognized, the most critical being 3270... it mounts the
> DASD successfully.
>
>
> From searching and reading a number of other threads I know some people
> had a similar issue with libtools (linking?) performing correctly when
> 'uname -p" returned no value... on my system it returns "unknown" if
> that helps anyone.
>
>
> Any help is appreciated.
>
>
> Thanks,
>
>
> Steve...
>
>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
In reply to this post by Hercules390 - General mailing list
Ivan,

 The current directory structure is:
 

 - armv7l
 ---> hyperion
 ---> s3fh
 

 thus I believe this is already set the way you requested.
 

 Now by run directory are you saying the directory that Hercules runs out of?  I currently show Hercules to be compiled and placed in /usr/local/bin... thus you would like me to try:
 

 1. Configure with my parms and include  --prefix=usr/local/bin ???
 2. Make and Make Install
 3. Export path and include the usr/local/bin directory
 4. Go back into my source (which is the only place is see Hercules.cnf) and execute Hercules from there.
 

 Thanks for your help and suggestions!
 

 Steve...
 

 

Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
In reply to this post by Hercules390 - General mailing list
John,

 The .libs directory in the build directory contains a number of device files:
 

 hdt3270.a
 hdt3270.la
 hdt3270.lai
 

 it has these 3 file extensions for most of the device types I see:  1052c,1403,2703,2880,3088,3270,3420,3505,3525,3705.   No .so files.
 

 Steve...
Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
So autotools is clearly confused.  You do need a .so file for device
managers; the various other libraries can be .a

I suppose uname -p is the culprit.  I doubt that configuring
    --enable-shared
will be much help, but it is worth at try.  You might also try
    --disable-static

On 03/26/2017 10:18 PM, [hidden email] [hercules-390] wrote:

>
>
> John,
>
>
> The .libs directory in the build directory contains a number of device
> files:
>
> hdt3270.a
> hdt3270.la
> hdt3270.lai
>
> it has these 3 file extensions for most of the device types I see:
>  1052c,1403,2703,2880,3088,3270,3420,3505,3525,3705.   No .so files.
>
> Steve...
>
>
> ------------------------------------------------------------------------
> Posted by: [hidden email]
> ------------------------------------------------------------------------
Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
I'll give those options a try...

 I notice in the configure log the following messages:
 

 checking build system type... armv7l-unknown-linux-gnu
 checking host system type... armv7l-unknown-linux-gnu
 checking target system type... armv7l-unknown-linux-gnu
 

 I'll assume the armv7l comes from the uname -m command
 and
 I'll assume the unknown comes from uname -p command
 

 both verified by manually entering the uname commands.
 

 Steve...

 

Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
What I did on Pi Zero, was more or less:

Run 1Stop until it stops with an error

cd ../armv6*

../hyperion/configure --prefix=/home/bill/tools/hercules --enable-s3fh-altdir=./s3fh

Then manually edited Makefile, decNumber/Makefile, crypto/Makefile
and removed the CPU options to gcc.

And run make.
Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
Hi Steve:

 If you are still having difficulty, or are still using the procedure described by Bill earlier in this thread and reproduced below, would you please do the following:
 

 1) re-clone Hyperion from https://github.com/hercules-390/hyperion https://github.com/hercules-390/hyperion
 2) re-run 1Stop
 

 When 1Stop completes, success or failure, run the following command from the build directory.  Note that 1Stop leaves you in the source directory at completion.
 

 3) make diagnostic
 

 Then please post the output from make diagnostic to this thread.
 

 Many thanks!
 

 Best Regards,
 Steve Orso
 

---In [hidden email], <wrljet@...> wrote :

 What I did on Pi Zero, was more or less:

Run 1Stop until it stops with an error

cd ../armv6*

../hyperion/configure --prefix=/home/bill/tools/hercules --enable-s3fh-altdir=./s3fh

Then manually edited Makefile, decNumber/Makefile, crypto/Makefile
and removed the CPU options to gcc.

And run make.

Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
Steve,

 Here are the diagnostic results:  I appreciate the help!
 

 System information
   /etc/os-release      PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
   uname -a             Linux raspberrypi 4.9.17-v7+ #981 SMP Fri Mar 24 14:21:53 GMT 2017 armv7l GNU/Linux
   uname -m             armv7l
   uname -p             unknown
   uname -s             Linux
 
 Build tools versions
   autoconf             autoconf (GNU Autoconf) 2.69
   automake             automake (GNU automake) 1.14.1
   m4                   m4 (GNU M4) 1.4.17
   make                 GNU Make 4.0
   compiler             gcc (Raspbian 4.9.2-10) 4.9.2
   linker               GNU ld (GNU Binutils for Raspbian) 2.25
 
 Build directories
   source              /home/pi/hyperion
   build               /home/pi/armv7l/hyperion
 Install directories
   prefix              /usr/local
     exec_prefix       /usr/local
       bindir          /usr/local/bin
       libdir          /usr/local/lib
     includedir        /usr/local/include
     datarootdir       /usr/local/share
       datadir         /usr/local/share
       mandir          /usr/local/share/man
       infodir         /usr/local/share/info
       docdir          /usr/local/share/doc/hercv4
 
 Values from automake
   BUILD_HERCIFC        Defined
   BUILD_FTHREADS       Undefined
   BUILD_SHARED         Defined
   OPTION_DYNAMIC_LOAD  Defined
 
 Values from make
   $CC                 gcc
   $CFLAGS             -g -O2 -W -Wall -O2 -mcpu=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard
   $CXX                g++
   $CXXFLAG            -g -O2
   $LDFLAGS            -Wl,--warn-common
   $CPPFLAGS           -DPKGDATADIR=\"/usr/local/share/hercv4\" -DMODULESDIR=\"/usr/local/lib/hercv4\" -DHERC_LOCALEDIR=\"/usr/local/share/locale\"
 
 Values from configure
   $LIBS               -lrt -lz -lresolv -lnsl -lm -ldl  -pthread -lbz2 -L/home/pi/armv7l/s3fh/lib -lSoftFloat
   $S3FH_INC           /home/pi/armv7l/s3fh/include
   $S3FH_LIB           @S3FH_LIB@     (future use)
   $HQA_INC            .
 
 Values generated by Makefile.am
   $AM_CPPFLAGS         -I/home/pi/hyperion -I/home/pi/hyperion/decNumber -I/home/pi/armv7l/s3fh/include -I.
   $DYNAMIC_VERISON     /home/pi/armv7l/hyperion
   $DYNMOD_LD_ADD       libherc.la libhercs.la libhercu.la -lrt -lz -lresolv -lnsl -lm -ldl  -pthread -lbz2 -L/home/pi/armv7l/s3fh/lib -lSoftFloat
   $DYNMOD_LD_FLAGS     -module -no-undefined  -export-dynamic -avoid-version
   $FTHREADS            
   $HDEPS              
   $HDLFLAGS            
   $HERCIFC             hercifc
   $HERCLIBS            
   $HERCLIBS2           libhercs.la libhercu.la libherct.la libhercd.la libherc.la
   $HERCLIN             herclin
   $LDADD               -lrt -lz -lresolv -lnsl -lm -ldl  -pthread -lbz2 -L/home/pi/armv7l/s3fh/lib -lSoftFloat
   $LIB_LD_FLAGS        -export-dynamic  -no-undefined -avoid-version
   $LTDL                ltdl.c
   $tools_ADDLIBS       libhercs.la libhercu.la libherct.la libhercd.la libherc.la -lrt -lz -lresolv -lnsl -lm -ldl  -pthread -lbz2 -L/home/pi/armv7l/s3fh/lib -lSoftFloat
   $tools_LD_FLAGS      
   $XSTATIC

 

Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
Hi Steve:
 

 I have been able to reproduce your issue using the QEMU emulator on Window-10.  While diagnosis continues, your issue does not appear to be related to the ARM cpu optimization options (-m command line options) included in the Makefile.  
 

 In particular, the -mfpu=neon-fp-armv8 -mfloat-abi=hard options relate to exploitation of hardware floating point support.  
 

 In Hercules, one infrequently-used mainframe non-floating point instruction uses floating point in its emulation, and all emulation of mainframe floating point instructions is done in software, not in the host system's hardware.   See float.c, ieee.c, and dfp.c for details if you wish.  The remaining option, -mcpu, enables gcc to optimize for a specific ARM processor and is not required to generate code for ARM.  
 

 Note also that the Raspberry PI is not a "supported" platform for Hercules v4 (Hyperion); there is no certainty that this can be made to work.  
 

 Although it has really been great fun getting an ARM emulator running on my Windows 10 machine.  I just wish it were as fast as Debian/Ubuntu/FreeBSD/Leap/CentOS on Virtualbox.  
 

 Best Regards,
 Steve Orso
 

---In [hidden email], <sglavach@...> wrote :

 Steve,

 Here are the diagnostic results:  I appreciate the help!
 

 [...]
 Values from make
   $CC                 gcc
   $CFLAGS             -g -O2 -W -Wall -O2 -mcpu=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard
   $CXX                g++
   $CXXFLAG            -g -O2
   $LDFLAGS            -Wl,--warn-common
   $CPPFLAGS           -DPKGDATADIR=\"/usr/local/share/hercv4\" -DMODULESDIR=\"/usr/local/lib/hercv4\" -DHERC_LOCALEDIR=\"/usr/local/share/locale\"
  [...]



Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
Either way, thanks for the help!

I know I have seen others stating that have successfully compiled on the rp3, I just haven't pieced the puzzle together yet!

Thanks,

Steve...

> On Mar 29, 2017, at 6:24 PM, [hidden email] [hercules-390] <[hidden email]> wrote:
>
> Hi Steve:
>
> I have been able to reproduce your issue using the QEMU emulator on Window-10.  While diagnosis continues, your issue does not appear to be related to the ARM cpu optimization options (-m command line options) included in the Makefile.  
>
> In particular, the -mfpu=neon-fp-armv8 -mfloat-abi=hard options relate to exploitation of hardware floating point support.  
>
> In Hercules, one infrequently-used mainframe non-floating point instruction uses floating point in its emulation, and all emulation of mainframe floating point instructions is done in software, not in the host system's hardware.   See float.c, ieee.c, and dfp.c for details if you wish.  The remaining option, -mcpu, enables gcc to optimize for a specific ARM processor and is not required to generate code for ARM.  
>
> Note also that the Raspberry PI is not a "supported" platform for Hercules v4 (Hyperion); there is no certainty that this can be made to work.  
>
> Although it has really been great fun getting an ARM emulator running on my Windows 10 machine.  I just wish it were as fast as Debian/Ubuntu/FreeBSD/Leap/CentOS on Virtualbox.  
>
> Best Regards,
> Steve Orso
>
>
> ---In [hidden email], <sglavach@...> wrote :
>
> Steve,
>
> Here are the diagnostic results:  I appreciate the help!
>
> [...]
> Values from make
>   $CC                 gcc
>   $CFLAGS             -g -O2 -W -Wall -O2 -mcpu=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard
>   $CXX                g++
>   $CXXFLAG            -g -O2
>   $LDFLAGS            -Wl,--warn-common
>   $CPPFLAGS           -DPKGDATADIR=\"/usr/local/share/hercv4\" -DMODULESDIR=\"/usr/local/lib/hercv4\" -DHERC_LOCALEDIR=\"/usr/local/share/locale\"
>  [...]
>
Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
I was under the impression that raspberry pi does neither floating point
nor block concurrent access.  I that correct?

Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
I think you havn't kept up with the latest changes..

The issue with floating point was that the original PI was ARM V6 and Debian only supported the hardware float in ArmV7 but the PI  V2 onwards are Arm v7 and   have hardware float.
Raspian was Debian with downgraded h/w float so even the v2 has hard float, but I think there were some issues building Hercules with it enabled..

I don't know about concurrent access, I assume you mean concurrent memory access? There must be some atomic operations because the PIv3 has a quad core CPU

Dave

> -----Original Message-----
> From: [hidden email] [mailto:hercules-
> [hidden email]]
> Sent: 30 March 2017 07:53
> To: [hidden email]
> Subject: Re: [hercules-390] Re: Compile on Raspberry PI 3
>
> I was under the impression that raspberry pi does neither floating point nor
> block concurrent access.  I that correct?
>
>
>
> ------------------------------------
> Posted by: "John P. Hartmann" <[hidden email]>
> ------------------------------------
>
> Community email addresses:
>   Post message: [hidden email]
>   Subscribe:    [hidden email]
>   Unsubscribe:  [hidden email]
>   List owner:   [hidden email]
>
> Files and archives at:
>   http://groups.yahoo.com/group/hercules-390
>
> Get the latest version of Hercules from:
>   http://www.hercules-390.org
>
>
> ------------------------------------
>
> Yahoo Groups Links
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
On 30/03/17 09:00, [hidden email] [hercules-390] wrote:
> I think you havn't kept up with the latest changes..
>
> The issue with floating point was that the original PI was ARM V6 and Debian only supported the hardware float in ArmV7 but the PI  V2 onwards are Arm v7 and   have hardware float.
> Raspian was Debian with downgraded h/w float so even the v2 has hard float, but I think there were some issues building Hercules with it enabled..
>
> I don't know about concurrent access, I assume you mean concurrent memory access? There must be some atomic operations because the PIv3 has a quad core CPU

Raspbian ships two kernels and sets of modules, one for v6 and the other
for v7. It's possible to install a standard Debian on top of that with
KDE etc., and I think that support for v3 will be improving provided
that Debian is able to satisfy itself that all components are
sufficiently "open".

--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]


------------------------------------

------------------------------------

Community email addresses:
  Post message: [hidden email]
  Subscribe:    [hidden email]
  Unsubscribe:  [hidden email]
  List owner:   [hidden email]

Files and archives at:
  http://groups.yahoo.com/group/hercules-390

Get the latest version of Hercules from:
  http://www.hercules-390.org


------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/hercules-390/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/hercules-390/join
    (Yahoo! ID required)

<*> To change settings via email:
    [hidden email]
    [hidden email]

<*> To unsubscribe from this group, send an email to:
    [hidden email]

<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/

Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
In reply to this post by Hercules390 - General mailing list
On Thu, 2017-03-30 at 09:28 +0100, [hidden email] [hercules-390]
wrote:
> I think you havn't kept up with the latest changes..
>
> The issue with floating point was that the original PI was ARM V6 and Debian only supported the hardware float in ArmV7 but the PI  V2 onwards are Arm v7 and   have hardware float.
> Raspian was Debian with downgraded h/w float so even the v2 has hard float, but I think there were some issues building Hercules with it enabled..
>
> I don't know about concurrent access, I assume you mean concurrent memory access? There must be some atomic operations because the PIv3 has a quad core CPU
>
> Dave

Yes, ARM has atomic operations.  I mucked about with the codezero ARM
hypervisor some time ago when it was open source and saw the use of such
instructions.

Harold Grovesteeen

Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
In reply to this post by Hercules390 - General mailing list
I never tried building it on QEMU.  That would take forever.  :-)

(BTW, it takes 5 days to build gcc 6.2 from source on a Pi Zero)

On the Pi Zero, which is a somewhat lesser CPU than the Pi 3, but runs the same
binaries, I have Hyperion working fine.  

The auto-detected -mcpu stuff in your experiment is different from mine, because
the Pi 3 has a different ARM.  But the fix is the same.
Remove all those switches and let the native compiler on the Pi decide what to use.

On mine, with gcc (Raspbian 4.9.2-10) 4.9.2,  I change the CFLAGS from:

 CFLAGS = -g -O2 -W -Wall -O2  -g -g3 -ggdb3 -mcpu=armv6l -mtune=armv6l -frename-registers

to:

CFLAGS = -g -O2 -W -Wall -O2  -g -g3 -ggdb3 -frename-registers

-Bill
Reply | Threaded
Open this post in threaded view
|

Re: Compile on Raspberry PI 3

Hercules390 - General mailing list
I'm pulling my hair out here <g>

 Have tried everything suggested and still looks like issues with linking in certain libraries (libhercX.XX)
 

 On a lark I tried compiling 3.12 from source and had no problems...everything compiles, links and works as expected on the RP3.  Then I tried compiling 4.0 using the gcc parameters that were devised for 3.12 just to humor myself and still no luck.
 

 Steve...
12