Bug 40491 - /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or d...
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: General
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-25 12:01 CET by Janek Walkenhorst
Modified: 2019-01-03 07:22 CET (History)
0 users

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janek Walkenhorst univentionstaff 2016-01-25 12:01:38 CET
It is not possible to include <gnu/stubs.h> on i386 with gcc-multilib installed.

 In file included from /usr/include/features.h:388:0,
                  from /usr/include/stdint.h:26,
                  from ../../../include/grub/xen.h:34,
                  from ../../../grub-core/commands/xen/lsxen.c:23:
 /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory

The files stubs-32.h and stubs-64.h come from different packages, and on amd64 the files are in the same directory:
 root@amd64: ~# dpkg -L libc6-dev|sort|grep stubs
 /usr/include/x86_64-linux-gnu/gnu/stubs-64.h
 /usr/include/x86_64-linux-gnu/gnu/stubs.h
 root@amd64: ~# dpkg -L libc6-dev-i386|sort|grep stubs
 /usr/include/x86_64-linux-gnu/gnu/stubs-32.h
but on i386 the file stubs-32.h is not found because the files for amd64 are in a different directory:
 root@i386: ~# dpkg -L libc6-dev-amd64|sort|grep stubs
 /usr/include/gnu/stubs-64.h
 /usr/include/gnu/stubs.h
 root@i386: ~# dpkg -L libc6-dev|sort|grep stubs
 /usr/include/i386-linux-gnu/gnu/stubs-32.h
 /usr/include/i386-linux-gnu/gnu/stubs.h

On amd64 /usr/include/gnu is a symlink:
 root@amd64: ~# ll -d /usr/include/gnu
 lrwxrwxrwx 1 root root 20 Nov 26 20:05 /usr/include/gnu -> x86_64-linux-gnu/gnu/
 root@amd64: ~# dpkg -S /usr/include/gnu
 libc6-dev-i386: /usr/include/gnu
but on i386 it is a directory:
 root@amd64: ~# ll -d /usr/include/gnu
 lrwxrwxrwx 1 root root 20 Nov 26 20:05 /usr/include/gnu -> x86_64-linux-gnu/gnu/
 root@amd64: ~# dpkg -S /usr/include/gnu
 libc6-dev-i386: /usr/include/gnu
Comment 1 Janek Walkenhorst univentionstaff 2016-01-25 16:50:51 CET
Workaround for building:

Backup /var/univention/buildsystem2/pbuilder/ucs_4.1-0-errata4.1-0.tgz

sudo pbuilder login --save-after-login --basetgz /var/univention/buildsystem2/pbuilder/ucs_4.1-0-errata4.1-0.tgz
# apt-get update
# apt-get install libc6-dev libc6-amd64-dev
# cd /usr/include/gnu
# ln -s /usr/include/i386-linux-gnu/gnu/stubs-32.h .
# exit

build package

Restore /var/univention/buildsystem2/pbuilder/ucs_4.1-0-errata4.1-0.tgz
Comment 2 Janek Walkenhorst univentionstaff 2016-02-04 17:08:39 CET
(In reply to Janek Walkenhorst from comment #1)
> Workaround for building:
> 
> Backup /var/univention/buildsystem2/pbuilder/ucs_4.1-0-errata4.1-0.tgz
> 
> sudo pbuilder login --save-after-login --basetgz
> /var/univention/buildsystem2/pbuilder/ucs_4.1-0-errata4.1-0.tgz
> # apt-get update
> # apt-get install libc6-dev libc6-amd64-dev
apt-get install libc6-dev libc6-dev-amd64
> # cd /usr/include/gnu
> # ln -s /usr/include/i386-linux-gnu/gnu/stubs-32.h .
> # exit
> 
> build package
> 
> Restore /var/univention/buildsystem2/pbuilder/ucs_4.1-0-errata4.1-0.tgz
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:22:24 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.