Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Émeric Vigier" <emeric.vigier@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] PowerPC: scsi/sg.h missing in glibc-2.18 / linux-headers-3.10.20 toolchain
Date: Mon, 24 Mar 2014 14:43:16 -0400 (EDT)	[thread overview]
Message-ID: <778977534.278661.1395686596735.JavaMail.root@mail> (raw)
In-Reply-To: <1996794731.250375.1395685034656.JavaMail.root@mail>

Hi makers,

I struggled to cross-compile (powerpc) strace-4.8 with linux-headers-3.10.20
and glibc-2.18.It does not find <scsi/sg.h> in my toolchain. Indeed there is
none in my sysroot:

$ find output/ -path "*/scsi/sg.h"
output/build/glibc-2.18/sysdeps/unix/sysv/linux/scsi/sg.h
output/build/linux-headers-3.10.20/include/scsi/sg.h

I have a duplicate buildroot with linux-headers-3.2.52 and the same glibc.
It succeeds to compile strace. Indeed headers are present in sysroot:

$ find output/ -path "*/scsi/sg.h"
output/build/linux-headers-3.2.52/include/scsi/sg.h
output/build/glibc-2.18/sysdeps/unix/sysv/linux/scsi/sg.h
output/build/linux-3.2.x/include/scsi/sg.h
output/host/usr/powerpc-buildroot-linux-gnu/sysroot/usr/include/scsi/sg.h

I checked linux API changes but nothing about SCSI:
http://man7.org/tlpi/api_changes/index.html

I worked around this problem with a simple copy:
$ cp output/build/glibc-2.18/sysdeps/unix/sysv/linux/scsi/sg.h \
     output/host/usr/powerpc-buildroot-linux-gnu/sysroot/usr/incl

I'd like to know how to truly fix this issue. Is this a bug in the toolchain 
cross-compilation?

thanks,
Emeric

       reply	other threads:[~2014-03-24 18:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1996794731.250375.1395685034656.JavaMail.root@mail>
2014-03-24 18:43 ` Émeric Vigier [this message]
2014-03-25 23:27   ` [Buildroot] PowerPC: scsi/sg.h missing in glibc-2.18 / linux-headers-3.10.20 toolchain Arnout Vandecappelle

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=778977534.278661.1395686596735.JavaMail.root@mail \
    --to=emeric.vigier@savoirfairelinux.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox