Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #202627 > unrolled thread

glibc_2.27-8 build fails on Butcher (testing)

Back to article view | Back to linux.debian.user

Contents

  glibc_2.27-8 build fails on Butcher (testing) Tetsuji Rai <t-rai@umin.org> - 2018-11-20 06:10 +0100
    Re: glibc_2.27-8 build fails on Butcher (testing) Roberto C. Sánchez <roberto@debian.org> - 2018-11-20 06:40 +0100
      Re: glibc_2.27-8 build fails on Butcher (testing) Tetsuji Rai <t-rai@umin.org> - 2018-11-20 07:10 +0100
        Re: glibc_2.27-8 build fails on Butcher (testing) Roberto C. Sánchez <roberto@debian.org> - 2018-11-20 07:40 +0100
          Re: glibc_2.27-8 build fails on Butcher (testing) Tetsuji Rai <t-rai@umin.org> - 2018-11-20 07:50 +0100
            Re: glibc_2.27-8 build fails on Butcher (testing) Roberto C. Sánchez <roberto@debian.org> - 2018-11-20 08:00 +0100
              Re: glibc_2.27-8 build fails on Butcher (testing) Tetsuji Rai <t-rai@umin.org> - 2018-11-20 08:10 +0100

#202627 — glibc_2.27-8 build fails on Butcher (testing)

Hi all,

I'm trying to build several packages from their source packages, however
I have not succeeded in building glibc_2.27-8.   It always fails telling
ndbm.h and varargs.h (or stdarg.h) in testsuite building, although I
have installed libgdbm-compat-dev (including /usr/include/ndbm.h) and
stdarg.h, varargs.h (in libstdc++-7-dev and libstdc++-8-dev).  Error
messages are as follows.  These appear many times because they are tried
many times.


Anyone have clues?   I am sure many people have done this.


Thanks in advance!!   Best regards,


-Tetsuji

--------------------------------errors
1--------------------------------------

XFAIL: conform/UNIX98/ndbm.h/conform
original exit status 1
Testing <ndbm.h>
----------------
  Checking whether <ndbm.h> is available... FAIL
    Header <ndbm.h> not available  Compiler message:
    -----------------------------------------------------------------------
   
/home/tetsuji/work-glibc/glibc-2.27/build-tree/amd64-libc/conform/UNIX98/ndbm.h/scratch/ndbm.h-test.c:1:10:
fatal error: ndbm.h: No such file or directory
     #include <ndbm.h>
              ^~~~~~~~
    compilation terminated.
    -----------------------------------------------------------------------

  Checking the namespace of "ndbm.h"... SKIP
---------------------------------errors
2-------------------------------------

XFAIL: conform/UNIX98/varargs.h/conform
original exit status 1
Testing <varargs.h>
-------------------
  Checking whether <varargs.h> is available... FAIL
    Header <varargs.h> not available  Compiler message:
    -----------------------------------------------------------------------
    In file included from
/home/tetsuji/work-glibc/glibc-2.27/build-tree/amd64-libc/conform/UNIX98/varargs.h/scratch/varargs.h-test.c:1:0:
    /usr/lib/gcc/x86_64-linux-gnu/7/include/varargs.h:4:2: error: #error
"GCC no longer implements <varargs.h>."
     #error "GCC no longer implements <varargs.h>."
      ^~~~~
    /usr/lib/gcc/x86_64-linux-gnu/7/include/varargs.h:5:2: error: #error
"Revise your code to use <stdarg.h>."
     #error "Revise your code to use <stdarg.h>."
      ^~~~~
    -----------------------------------------------------------------------

  Checking the namespace of "varargs.h"... SKIP

[toc] | [next] | [standalone]

#202628

On Tue, Nov 20, 2018 at 02:06:17PM +0900, Tetsuji Rai wrote:
> Hi all,
> 
> I'm trying to build several packages from their source packages, however
> I have not succeeded in building glibc_2.27-8.   It always fails telling
> ndbm.h and varargs.h (or stdarg.h) in testsuite building, although I
> have installed libgdbm-compat-dev (including /usr/include/ndbm.h) and
> stdarg.h, varargs.h (in libstdc++-7-dev and libstdc++-8-dev).  Error
> messages are as follows.  These appear many times because they are tried
> many times.
> 
> 
> Anyone have clues?   I am sure many people have done this.

What commands are you using to build the package?  This includes the
commands to download the package and, if applicable, unpack/prepare it
for the build.

Regards,

-Roberto

-- 
Roberto C. Sánchez

[toc] | [prev] | [next] | [standalone]

#202629

As the tutorial ( https://wiki.debian.org/BuildingTutorial ) says,

download with "apt-get source libc6" in my ~/work-glibc, and cd
glibc-2.27, then download build dependencies with "sudo apt-get
build-dep libc6", then rebuild with "debuild -b -uc -us".

After a while, I got these errors.  But I might run "debuild -b -uc -us"
in ~/work-glibc/glibc-2.27/debian.  Does it matter?

Best regards,


On 11/20/18 2:30 PM, Roberto C. Sánchez wrote:
> On Tue, Nov 20, 2018 at 02:06:17PM +0900, Tetsuji Rai wrote:
>> Hi all,
>>
>> I'm trying to build several packages from their source packages, however
>> I have not succeeded in building glibc_2.27-8.   It always fails telling
>> ndbm.h and varargs.h (or stdarg.h) in testsuite building, although I
>> have installed libgdbm-compat-dev (including /usr/include/ndbm.h) and
>> stdarg.h, varargs.h (in libstdc++-7-dev and libstdc++-8-dev).  Error
>> messages are as follows.  These appear many times because they are tried
>> many times.
>>
>>
>> Anyone have clues?   I am sure many people have done this.
> What commands are you using to build the package?  This includes the
> commands to download the package and, if applicable, unpack/prepare it
> for the build.
>
> Regards,
>
> -Roberto
>

[toc] | [prev] | [next] | [standalone]

#202631

On Tue, Nov 20, 2018 at 03:02:12PM +0900, Tetsuji Rai wrote:
> As the tutorial ( https://wiki.debian.org/BuildingTutorial ) says,
> 
> download with "apt-get source libc6" in my ~/work-glibc, and cd
> glibc-2.27, then download build dependencies with "sudo apt-get
> build-dep libc6", then rebuild with "debuild -b -uc -us".
> 
> After a while, I got these errors.  But I might run "debuild -b -uc -us"
> in ~/work-glibc/glibc-2.27/debian.  Does it matter?
> 
Please don't top post.  It is considered impolite.

There are few packages more complex than glibc.  Building using
'debuild' instead of building inside of a clean pbuilder, cowbuilder,
schroot, or other build environment is sure to invite problems.

My recommendation is to use one of those approaches instead of the
'debuild'.

If you are interested in trying to get the build working with debuild
then the entire build output will be needed.  You can redirect the
output to a file (make sure to capture both standard output and standard
error) and then post it somewhere (it will most likely be too large to
send to the list as an attachment).

Regards,

-Roberto

-- 
Roberto C. Sánchez

[toc] | [prev] | [next] | [standalone]

#202632

On 11/20/18 3:30 PM, Roberto C. Sánchez wrote:

> On Tue, Nov 20, 2018 at 03:02:12PM +0900, Tetsuji Rai wrote:
>> As the tutorial ( https://wiki.debian.org/BuildingTutorial ) says,
>>
>> download with "apt-get source libc6" in my ~/work-glibc, and cd
>> glibc-2.27, then download build dependencies with "sudo apt-get
>> build-dep libc6", then rebuild with "debuild -b -uc -us".
>>
>> After a while, I got these errors.  But I might run "debuild -b -uc -us"
>> in ~/work-glibc/glibc-2.27/debian.  Does it matter?
>>
> Please don't top post.  It is considered impolite.
>
> There are few packages more complex than glibc.  Building using
> 'debuild' instead of building inside of a clean pbuilder, cowbuilder,
> schroot, or other build environment is sure to invite problems.
>
> My recommendation is to use one of those approaches instead of the
> 'debuild'.
>
> If you are interested in trying to get the build working with debuild
> then the entire build output will be needed.  You can redirect the
> output to a file (make sure to capture both standard output and standard
> error) and then post it somewhere (it will most likely be too large to
> send to the list as an attachment).
>
> Regards,
>
> -Roberto
>
I want to stick to debuild because it looks like a standard.   I am
recompiling with the logs.  I will report the logs (compressed) later. 
So far error are given to only stdout.  I used

debuild -b -uc -us > ~/glibc-stdout.log 2> ~/glibc-stderr.log &


Regards,

-Tetsuji

[toc] | [prev] | [next] | [standalone]

#202633

On Tue, Nov 20, 2018 at 03:47:44PM +0900, Tetsuji Rai wrote:
> >
> I want to stick to debuild because it looks like a standard.   I am
> recompiling with the logs.  

Suit yourself.  Just be advised that debuild is 'standard' because it
happens to be present and slightly more convenient than building
packages correctly (i.e., in a clean build environment).

> I will report the logs (compressed) later. 
> So far error are given to only stdout.  I used
> 
> debuild -b -uc -us > ~/glibc-stdout.log 2> ~/glibc-stderr.log &
> 
That will make it difficult to correlate outputs and errors.  Better
would be:

debuild -b -uc -us > ~/glibc.log 2>&1

Regards,

-Roberto

-- 
Roberto C. Sánchez

[toc] | [prev] | [next] | [standalone]

#202634

On 11/20/18 3:57 PM, Roberto C. Sánchez wrote:

> I will report the logs (compressed) later. 
>> So far error are given to only stdout.  I used
>>
>> debuild -b -uc -us > ~/glibc-stdout.log 2> ~/glibc-stderr.log &
>>
> That will make it difficult to correlate outputs and errors.  Better
> would be:
>
> debuild -b -uc -us > ~/glibc.log 2>&1
>
> Regards,
>
> -Roberto
>
Ok, I'll do so.

Regards,

-Tetsuji

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web