gcc/libgo
Ian Lance Taylor c9548fa4f1 libgo: fix makefile buglet
Fix a small bug in the libgo Makefile recipe that constructs the
    directory from which to pick up libgcc_s.so ; the gccgo invocation
    with -print-libgcc-file-name was missing the flags, which meant that
    for -m32 builds we'd see the 64-bit libgcc dir.
    
    Reviewed-on: https://go-review.googlesource.com/78836

From-SVN: r254984
2017-11-21 06:19:10 +00:00
..
config
go
misc/cgo
runtime
testsuite
aclocal.m4
config.h.in
configure Adapt Solaris 12 references 2017-11-14 18:31:01 +00:00
configure.ac libgo: adapt Solaris 12 references 2017-11-14 14:26:04 +00:00
godeps.sh
libgo.imp
LICENSE
Makefile.am libgo: fix makefile buglet 2017-11-21 06:19:10 +00:00
Makefile.in libgo: fix makefile buglet 2017-11-21 06:19:10 +00:00
match.sh
MERGE
merge.sh
mkrsysinfo.sh libgo: adapt Solaris 12 references 2017-11-14 14:26:04 +00:00
mksigtab.sh
mksysinfo.sh libgo: adapt Solaris 12 references 2017-11-14 14:26:04 +00:00
mvifdiff.sh
PATENTS
README
README.gcc
sysinfo.c
VERSION

See ../README.

This is the runtime support library for the Go programming language.
This library is intended for use with the Go frontend.

This library should not be stripped when it is installed.  Go code
relies on being able to look up file/line information, which comes
from the debugging info using the libbacktrace library.

The library has only been tested on GNU/Linux using glibc, and on
Solaris.  It should not be difficult to port to other operating
systems.

Directories:

go
  A copy of the Go library from http://golang.org/, with several
  changes for gccgo.

runtime
  Runtime functions, written in C, which are called directly by the
  compiler or by the library.

Contributing
============

To contribute patches to the files in this directory, please see
http://golang.org/doc/gccgo_contribute.html .

The master copy of these files is hosted at
http://code.google.com/p/gofrontend .  Changes to these files require
signing a Google contributor license agreement.  If you are the
copyright holder, you will need to agree to the individual contributor
license agreement at
http://code.google.com/legal/individual-cla-v1.0.html.  This agreement
can be completed online.

If your organization is the copyright holder, the organization will
need to agree to the corporate contributor license agreement at
http://code.google.com/legal/corporate-cla-v1.0.html.

If the copyright holder for your code has already completed the
agreement in connection with another Google open source project, it
does not need to be completed again.