From: Bill Northcott <w.northcott@unsw.edu.au>
To: James E Wilson <wilson@specifixinc.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Libobjc and libffi on Darwin
Date: Sat, 14 Aug 2004 02:15:00 -0000 [thread overview]
Message-ID: <4517FDBE-ED97-11D8-8B8E-000393D3D676@unsw.edu.au> (raw)
In-Reply-To: <411D680D.8060604@specifixinc.com>
On 14/08/2004, at 11:17 AM, James E Wilson wrote:
> Bill Northcott wrote:
>> ffi.h never got installed. ffitarget.h was installed in the compiler
>> includes directory. Any suggestions where this should be fixed?
>
> Maybe you are looking in the wrong place? ffi.h gets installed in a
> different place than ffitarget.h.
>
> If it really wasn't installed, then look at the Makefile in the
> $target/libffi/include directory. There should be an install rule for
> the ffi.h file. Works backwards from there to figure out why it
> wasn't called.
>
Thanks for the comments. I got it fixed by patching build-gcc thus:
Index: build_gcc
===================================================================
RCS file: /cvsroot/gcc/gcc/Attic/build_gcc,v
retrieving revision 1.1.2.9
diff -c -c -r1.1.2.9 build_gcc
*** build_gcc 6 Aug 2004 20:15:31 -0000 1.1.2.9
--- build_gcc 12 Aug 2004 07:23:42 -0000
***************
*** 289,294 ****
--- 289,297 ----
# include
HEADERPATH=$DEST_ROOT/include/gcc/darwin/$MAJ_VERS
mkdir -p .$HEADERPATH || exit 1
+ # fudge for odd headers not really gcc like ffi.h
+ cp -p $DIR/dst-$BUILD-$BUILD/$DEST_ROOT/include/*.h \
+ .$DEST_ROOT/include
cp -rp $DIR/dst-$BUILD-$BUILD$HEADERPATH/c++ \
.$HEADERPATH/ || exit 1
for t in $TARGETS ; do
Bill Northcott
next prev parent reply other threads:[~2004-08-14 2:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 4:12 Bill Northcott
2004-08-14 0:58 ` Tom Tromey
2004-08-14 3:28 ` Andrew Pinski
2004-08-14 1:18 ` James E Wilson
2004-08-14 2:15 ` Bill Northcott [this message]
2004-08-14 2:16 ` Andrew Pinski
2004-08-14 8:15 ` James E Wilson
2004-08-14 18:25 ` Dale Johannesen
2004-08-15 1:42 ` Bill Northcott
2004-08-15 3:53 Bill Northcott
2004-08-15 6:57 ` Andrew Pinski
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=4517FDBE-ED97-11D8-8B8E-000393D3D676@unsw.edu.au \
--to=w.northcott@unsw.edu.au \
--cc=gcc@gcc.gnu.org \
--cc=wilson@specifixinc.com \
/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).