Debian bug report logs - junk, last week
This includes messages sent to debian-bugs-done
which did not have a bug reference number in the Subject line
(these are ignored), as well as messages which contained an
unknown or out of date bug report number (these cause a warning
to be sent to the sender).
Message received at debian-bugs:
From rem.ods.com!david Sat Jun 17 20:36:27 1995
Return-Path: <david@rem.ods.com>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0sNB9q-0005z9C; Sat, 17 Jun 95 20:36 PDT
Received: from istwok.ods.com by pixar.com with SMTP id AA28691
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sat, 17 Jun 1995 20:34:55 -0700
Received: from rem.ods.com by istwok.ods.com (4.1/SMI-4.1)
id AA05366; Sat, 17 Jun 95 22:36:37 CDT
Received: by rem.ods.com (4.1/SMI-4.1)
id AA19968; Sat, 17 Jun 95 22:37:24 CDT
From: david@rem.ods.com (David Engel)
Message-Id: <9506180337.AA19968@rem.ods.com>
Subject: Re: Bug #855: strange elf build fault... solution
To: jdassen@WI.LeidenUniv.NL (J.H.M.Dassen)
Date: Sat, 17 Jun 1995 22:37:24 -0500 (CDT)
Cc: debian-bugs@pixar.com, david@ods.com
In-Reply-To: <199506171727.RAA09370@ind302fb.wi.leidenuniv.nl> from "J.H.M.Dassen" at Jun 17, 95 07:27:33 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 771
> Please update the gcc-elf package to use this replacement for
> /usr/bin/gcc-elf. Though I haven't had problems with
> as-elf, g++-elf and ld-elf, they can cause this problem too.
> Please replace these too, with their analogue.
Please try the ELF version of gcc-2.7.0 that I will upload as soon as
buster allows me to get in. Unlike the previous ELF versions, this
one was compiled by me and has the i486-linuxelf prefix built in so it
doesn't need any script kluges. If you're not daring enough to try
2.7.0, I'll try to locate the ELF patches for 2.6.3 and compile it
myself.
David
--
David Engel Optical Data Systems, Inc.
david@ods.com 1101 E. Arapaho Road
(214) 234-6400 Richardson, TX 75081
Reply sent to david@rem.ods.com (David Engel):
Unknown problem report number 855.
Full text available.
Message received at debian-bugs:
From WI.LeidenUniv.NL!jdassen Sat Jun 17 10:30:18 1995
Return-Path: <jdassen@WI.LeidenUniv.NL>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0sN1hJ-0007mBC; Sat, 17 Jun 95 10:30 PDT
Received: from mailhost.WI.LeidenUniv.NL (zeus128.wi.leidenuniv.nl) by pixar.com with SMTP id AA04785
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sat, 17 Jun 1995 10:28:50 -0700
Received: from ind302fb.wi.leidenuniv.nl (jdassen@ind302fb [132.229.16.36])
by mailhost.WI.LeidenUniv.NL (8.6.10a/FHM-1.20-M) with ESMTP id TAA03174
Sat, 17 Jun 1995 19:29:32 +0200 (MET)
From: jdassen@WI.LeidenUniv.NL (J.H.M.Dassen)
Organization: Leiden University,
Dept. of Mathematics & Computer Science,
The Netherlands
Received: from (jdassen@localhost)
by ind302fb.wi.leidenuniv.nl (8.6.10a/FHM-1.03-S) id RAA09370
Sat, 17 Jun 1995 17:27:34 GMT (MET)
Message-Id: <199506171727.RAA09370@ind302fb.wi.leidenuniv.nl>
Subject: Bug #855: strange elf build fault... solution
To: debian-bugs@pixar.com, david@ods.com
Date: Sat, 17 Jun 1995 19:27:33 +0200 (MDT)
Return-Receipt-To: jdassen@WI.LeidenUniv.NL
X-Home-Page: <URL:http://www.wi.leidenuniv.nl/home/jdassen>
X-Mailer: ELM [version 2.4 PL24 (modified)]
Content-Type: text
Content-Length: 1680
David,
Please update the gcc-elf package to use this replacement for
/usr/bin/gcc-elf. Though I haven't had problems with
as-elf, g++-elf and ld-elf, they can cause this problem too.
Please replace these too, with their analogue.
-- CUT ME --
#!/bin/perl -w
# This is a replacement for /usr/bin/gcc-elf. gcc-elf used to be:
# #!/bin/sh
# exec /usr/i486-linuxelf/bin/gcc -b i486-linuxelf $* -fno-force-mem \
# -I/usr/i486-linuxelf/include
# but this caused problems, since shell interpretation of the
# parameters was done twice. Example (from ppp-2.1.2b-1):
# cc -c -o options.o -O2 -DDEBUGALL -I.. -D_linux_=1 \
# -DGIDSET_TYPE=gid_t "-DIMPLEMENTATION=\" (Linux 1.0.1)\"" options.c
# gcc: (Linux: No such file or directory
# gcc: 1.0.1)": No such file or directory
# options.c:0: unterminated string or character constant
# options.c:0: possible real start of unterminated constant
# When calling the old gcc-elf, the first shell removed the double quotes,
# and the second shell removes the double quotes which were quoted.
#
# Thanks to David Engel for recognising the problem, and to Bart Schuller
# for suggesting this solution.
# Prepend gcc and options to parameters
unshift(@ARGV, ('/usr/i486-linuxelf/bin/gcc', '-b', 'i486-linuxelf'));
# Append options
push(@ARGV, ('-fno-force-mem', '-I/usr/i486-linuxelf/include'));
exec(@ARGV); # More than one element in the list, so perl calls
# execvp(3), as per perlfunc(1)
-- OUCH! --
Greetings,
Ray
--
ART A friend of mine in Tulsa, Okla., when I was about eleven years old.
I'd be interested to hear from him. There are so many pseudos around taking
his name in vain.
- The Hipcrime Vocab by Chad C. Mulligan
Reply sent to jdassen@WI.LeidenUniv.NL (J.H.M.Dassen):
Unknown problem report number 855.
Full text available.
Ian Jackson /
iwj10@thor.cam.ac.uk,
with the debian-bugs tracking mechanism