Next | Query returned 99 messages, browsing 91 to 100 | previous

History of commit frequency

CVS Commit History:


   2005-03-07 01:25:39 by Thomas Klausner | Files touched by this commit (2)
Log message:
Add RCS Id to patch-aa.
   2005-03-03 10:18:47 by Daniel de Kok | Files touched by this commit (2)
Log message:
Make libffi buildable on NetBSD/amd64 (fixes PR pkg/29512).

Ack by wiz@.
   2005-02-23 23:24:35 by Alistair G. Crooks | Files touched by this commit (505)
Log message:
Add RMD160 digests.
   2004-10-03 02:13:34 by Todd Vierling | Files touched by this commit (908)
Log message:
Libtool fix for PR pkg/26633, and other issues.  Update libtool to 1.5.10
in the process.  (More information on tech-pkg.)

Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.

Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
   2004-09-22 10:10:08 by Johnny C. Lam | Files touched by this commit (703)
Log message:
Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:

	lib/libfoo.a
	lib/libfoo.la
	lib/libfoo.so
	lib/libfoo.so.0
	lib/libfoo.so.0.1

one simply needs:

	lib/libfoo.la

and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.

Also make LIBTOOLIZE_PLIST default to "yes".
   2004-04-12 02:00:49 by Soren Jacobsen | Files touched by this commit (1)
Log message:
No longer used.
   2004-03-28 22:46:52 by Julio M. Merino Vidal | Files touched by this commit (1)
Log message:
Initial addition, used by sablevm ATM.
   2003-12-24 10:53:50 by Julio M. Merino Vidal | Files touched by this commit (69)
Log message:
s/@netbsd.org/@NetBSD.org/ in MAINTAINER.
   2003-07-18 14:39:40 by Alistair G. Crooks | Files touched by this commit (5) | Imported package
Log message:
Initial import of libffi-2.0beta into the NetBSD Packages Collection.

The libffi library provides a portable, high level programming
interface to various calling conventions.  This allows a programmer to
call any function specified by a call interface description at
run-time.

Some programs may not know at the time of compilation what arguments
are to be passed to a function.  For instance, an interpreter may be
told at run-time about the number and types of arguments used to call
a given function.  Libffi can be used in such programs to provide a
bridge from the interpreter program to compiled code.

Ffi stands for Foreign Function Interface.  A foreign function
interface is the popular name for the interface that allows code
written in one language to call code written in another language.  The
libffi library really only provides the lowest, machine dependent
layer of a fully featured foreign function interface.  A layer must
exist above libffi that handles type conversions for values passed
between the two languages.

Next | Query returned 99 messages, browsing 91 to 100 | previous