From: JohnT <democritus7@att.net>
To: libffi-discuss@sourceware.org
Subject: building/testing libffi-3.2.1
Date: Sat, 02 Jul 2016 22:52:00 -0000 [thread overview]
Message-ID: <5778459B.8030501@att.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]
Hello. I needed this lib and header file for something I wanted to build,
and though my system said it was installed, the gnu build system wasn't
finding it. So I got the source, built it and installed in /usr, and still
the files weren't found. On reviewing the install, I found that the
default was to install libffi-3.2.1 stuff in a new folder under /usr/lib.
And the header files went into an include folder under that, instead of
into /user/include where the build system would look. I copied those
headers into /user/include and got my build done, but you might want to
review this to see if the nonstandard spot for installation is where you
really want it.
Below are the test results for my build on a Dell Optiplex 790, 2nd
generation i5 processor at 2400 mhz running 32-bit Mageia 5 Linux, using
GCC 4.9.2 built for i586-mageia-linux-gnu, the default Mageia 5 GCC.
John Tellefson
Salina, KS
************ Test Results *******************
WARNING: Couldn't find the global config file.
Test Run By me on Sat Jul 2 17:36:01 2016
Native configuration is i686-pc-linux-gnu
=== libffi tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ../../testsuite/config/default.exp as tool-and-target-specific
interface file.
Running ../../testsuite/libffi.call/call.exp ...
=== libffi Summary ===
# of expected passes 2365
--
http://www.mozilla.org Firefox browser, Thunderbird email, Seamonkey all-in-one, Sunbird calendar and more. Free secure open-source software for Windows, Linux, Mac OS and other operating systems
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2016-07-02 22:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5778459B.8030501@att.net \
--to=democritus7@att.net \
--cc=libffi-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).