From: Neil Jerram <neil@ossau.uklinux.net>
Subject: 1.6 branch not compiling?
Date: 20 Jan 2004 22:31:34 +0000 [thread overview]
Message-ID: <m3ektutfp5.fsf@laruns.ossau.uklinux.net> (raw)
Is it just me, or does the 1.6 branch in CVS not compile?
I get:
raw-ltdl.c:2172: warning: `struct direct' declared inside parameter list
raw-ltdl.c:2172: warning: its scope is only this definition or declaration, which is probably not what you want.
raw-ltdl.c: In function `lt_argz_insertdir':
raw-ltdl.c:3573: argument `dp' doesn't match prototype
raw-ltdl.c:2172: prototype declaration
raw-ltdl.c:3586: dereferencing pointer to incomplete type
raw-ltdl.c:3586: dereferencing pointer to incomplete type
raw-ltdl.c:3591: dereferencing pointer to incomplete type
raw-ltdl.c:3602: dereferencing pointer to incomplete type
raw-ltdl.c:3611: dereferencing pointer to incomplete type
raw-ltdl.c:3621: dereferencing pointer to incomplete type
raw-ltdl.c:3621: dereferencing pointer to incomplete type
raw-ltdl.c:3621: dereferencing pointer to incomplete type
raw-ltdl.c:3621: dereferencing pointer to incomplete type
raw-ltdl.c:3621: dereferencing pointer to incomplete type
raw-ltdl.c: In function `list_files_by_dir':
raw-ltdl.c:3639: `DIR' undeclared (first use in this function)
raw-ltdl.c:3639: (Each undeclared identifier is reported only once
raw-ltdl.c:3639: for each function it appears in.)
raw-ltdl.c:3639: `dirp' undeclared (first use in this function)
raw-ltdl.c:3640: parse error before `int'
raw-ltdl.c:3647: warning: implicit declaration of function `opendir'
raw-ltdl.c:3652: warning: implicit declaration of function `readdir'
raw-ltdl.c:3652: warning: assignment makes pointer from integer without a cast
raw-ltdl.c:3653: dereferencing pointer to incomplete type
raw-ltdl.c:3654: warning: passing arg 4 of `lt_argz_insertdir' from incompatible pointer type
raw-ltdl.c:3656: `errors' undeclared (first use in this function)
raw-ltdl.c:3660: warning: implicit declaration of function `closedir'
raw-ltdl.c:3666: warning: control reaches end of non-void function
make[3]: *** [guile-ltdl.lo] Error 1
make[3]: Leaving directory `/home/neil/Guile/bra/guile-core/libguile-ltdl'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/neil/Guile/bra/guile-core/libguile-ltdl'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/neil/Guile/bra/guile-core'
make: *** [all] Error 2
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-01-20 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 22:31 Neil Jerram [this message]
2004-01-21 3:41 ` 1.6 branch not compiling? Rob Browning
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3ektutfp5.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
/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).