[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#207391: glibc: does not build: version-info.h and other problems.



On Wed, Aug 27, 2003 at 09:14:13AM +0900, GOTO Masanori wrote:
> At Tue, 26 Aug 2003 13:15:58 -0500,
> Zed Pobre wrote:
> > Severity: serious
> 
> Please don't use this tag if you modify our original libc6 package.

    *sigh*  If it makes you feel better, I'll run it again without the
patch, but I don't expect anything to change.


> > I have been attempting to build glibc with the parenthesis added to
> > 10_cvs.dpatch as noted in bug#202243 (this is the first, minimally
> > invasive patch, not the final patch that actually truncates instead of
> > rounding).  As it consists of parenthesis being added to four lines, I
> > don't think my modifications are the cause of the problem.  Running
> > apt-get build-dep glibc shows that I'm not missing any stated
> > build-dependencies.  However, when compiling, I get at one point:
> 
> So your patch breaks something?

    No, the point of all that was to explain that the patch could not
be responsible for the breakage I saw.


> Use 2.3.2-4, it contains the latest utimes update.

    Once it actually hits the mirrors, I plan to.  However, I thought
you folks might want to know about a situation where libc6 failed to
build.


> > After this point it actually continues compiling (though I get more
> > errors like this about various stamp.o and stamp.oS files as it goes
> > along), so although as a novice to glibc I find this unsettling, it's
> > not a major issue until it gets down to:
> 
> You should search 'error' parts.

    I'm sorry, I don't understand you.


> > At this point the compilation completely aborts.  Taking a closer look
> > at the version-info.h file, it contains:
[...]
> 
> I forgot why this message were appeared; please use 2.3.2-4.

    I'll test recompiling with stock 2.3.2-3 today, and then 2.3.2-4
as soon as I can find a copy of it.

-- 
Zed Pobre <zed@debian.org> a.k.a. Zed Pobre <zed@resonant.org>
PGP key and fingerprint available on finger; encrypted mail welcomed.

Attachment: pgpugEqjY_uvm.pgp
Description: PGP signature


Reply to: