All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Pfeiffer <roto@gmx.net>
To: Debian Bug Tracking System <submit@bugs.debian.org>,
	SE-Linux <selinux@tycho.nsa.gov>,
	Russell Coker <russell@coker.com.au>
Subject: gcc-2.95: checking for va_list assignment copy... configure: error: no
Date: Sun, 01 Aug 2004 19:58:48 +0200	[thread overview]
Message-ID: <1091383127.1295.283.camel@debby> (raw)

Package: gcc-2.95
Version: 1:2.95.4-22
Severity: normal


Trying to build a SE-Linux dpkg package with gcc-2.95 and this script:

=========================================== 
#!/bin/sh -x
cd $HOME/russellpackages/dpkg/ && \
rm -rf * && \
curl -f -O http://selinux.lemuria.org/newselinux/dpkg/dpkg_1.10.22.orig.tar.gz && \
curl -f -O http://selinux.lemuria.org/newselinux/dpkg/dpkg_1.10.22-se1.diff.gz && \
tar -xzvf *\.tar.gz && \
cd dpkg-1.10.22/ && \
cp ../dpkg_1.10.22-se1.diff.gz . && \
gzip -cd dpkg_1.10.22-se1.diff.gz | patch -p1 && \
chmod +x debian/rules && \
autoconf && \
fakeroot debian/rules binary
=================================================

ends like this:
---------------------------------------------------- 
checking for initscr in -lncurses... yes
checking if TIOCNOTTY is defined in sys/ioctl.h... yes
checking for va_copy... no
checking for va_list assignment copy... configure: error: no
make: *** [/home/shorty/russellpackages/dpkg/dpkg-1.10.22/build/configure-stamp] Error 1
----------------------------------------------------

Google hints that
"gcc build has failed to install varargs.h"
<http://www.uclibc.org/lists/uclibc/2003-February/005694.html>

$ locate varargs.h
/usr/lib/gcc-lib/powerpc-linux/2.95.4/include/varargs.h
/usr/lib/gcc-lib/powerpc-linux/3.0.4/include/varargs.h
/usr/lib/gcc-lib/powerpc-linux/3.3.4/include/varargs.h
/usr/lib/gcc/powerpc-linux/3.4.1/include/varargs.h

Trying to build the package with the mentioned script above plus gcc-3.3
or gcc-3.0 or gcc-3.4 each time successfully builds these packages:

dpkg-dev_1.10.22-se1_all.deb
dpkg-doc_1.10.22-se1_all.deb
dpkg_1.10.22-se1_powerpc.deb
dselect_1.10.22-se1_powerpc.deb

HTH

Regards
Wolfgang


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.4.25-ben1
Locale: LANG=C, LC_CTYPE=C

Versions of packages gcc-2.95 depends on:
ii  binutils                   2.14.90.0.7-8 The GNU assembler, linker and bina
ii  cpp-2.95                   1:2.95.4-22   The GNU C preprocessor
ii  libc6                      2.3.2.ds1-13  GNU C Library: Shared libraries an
-- no debconf information
-- 
Profile, links: http://profiles.yahoo.com/wolfgangpfeiffer


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

             reply	other threads:[~2004-08-01 17:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-01 17:58 Wolfgang Pfeiffer [this message]
2004-08-02  8:10 ` gcc-2.95: checking for va_list assignment copy... configure: error: no Russell Coker
2004-08-02 10:04   ` Wolfgang Pfeiffer
2004-08-02 10:13     ` Russell Coker
2004-08-03 11:12       ` Wolfgang Pfeiffer

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=1091383127.1295.283.camel@debby \
    --to=roto@gmx.net \
    --cc=russell@coker.com.au \
    --cc=selinux@tycho.nsa.gov \
    --cc=submit@bugs.debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.