Re: [Bug-xorriso] please help to compile arm cross platform

[Thomas Schmitt]

Hi,

> 1) no effect CFLAGS="$CFLAGS -DLibburn_use_sg_dummY"

Sorry, my fault.
CFLAGS (or the more appropriate CPPFLAGS) gets only into effect
by a run of

  ./configure ...options...


> 2) build with such settings => ./configure ...other.options...  
> --enable-libcdio

I assume you did the  xorriso -version  run with this second
result.
It looks like the ./configure run brought CFLAGS into effect
which then overrode the --enable-libcdio configuration:

> libburn OS adapter:  internal X/Open adapter sg-dummy

This adapter is ok for writing ISO 9660 to regular files,
to pipes and to writable block devices.
E.g. USB stick stdio:/dev/sdb or a thoroughly formatted
DVD+RW stdio:/dev/sr0.
Files underneath /dev directory need the prefix "stdio:".
(They are not driven directly by SCSI/MMC commands but indirectly
 via the POSIX standard i/o functions.)

-------------------------------------------------------------

The adapters for SG_IO and libcdio can operate all kinds of
optical media. Not only the ones suitable for random-access
POSIX writing.
In order to try with libcdio, you will have to

  export CFLAGS=...normal.value.without.dummy.option...
  ./configure ...options... --enable-libcdio
  make clean
  make

You will need libcdio runtime libraries and libcdio development
headers for that. Version 0.83 at least.

In case of success, xorriso -version should report something like

  libburn OS adapter:  sg-libcdio h84 with libcdio 0.84 ...

If this compilation works, and if you have an optical drive
attached, then you could check whether xorriso finds the drive:

  (cd releng && ./manual_devices -x ../xorriso/xorriso )

should list the attached drives which offer rw-permission to
the user and then ask for a drive address for further examination.
Empty input selects the first found drive.

-------------------------------------------------------------

> 3) my system centos 5 2.6.18-348.4.1.el5, building =>
> official synology package for build => arm-marvell-linux-gnueabi
> CFLAGS=-I/usr/local/arm-marvell-linux-gnueabi/arm-marvell-linux-gnueabi/libc/include

When searching for these names i came to
  
http://www.plugcomputer.org/405/us/gplugd/tool-chain/arm-marvell-linux-gnueabi.tar.bz2
which contains
  
arm-marvell-linux-gnueabi/arm-marvell-linux-gnueabi/libc/marvell-fv7/usr/include/scsi/sg.h

But in there i see

  unsigned char * sbp;        /* [i], [*o] points to sense_buffer memory */

which does not explain the compiler error message.

So i am clueless about the cause of the problem.

What do you see in your scsi/sg.h file ?
If this also says "unsigned char * sbp" then there must the some
other explanation.

Is it sure that the effectively included file <scsi/sg.h> stems
from the arm-marvell include directory ?
Can you make an experiment ?

Deface the include file

  ...
  } sg_iovec_t;

+ Hello compiler. Please produce an error.

  typedef struct sg_io_hdr
  { 
  ...

Then compile and check whether you get the intentional error
  
  export CFLAGS=...normal.value.without.dummy.option...
  ./configure ...options... --disable-libcdio
  make clean
  make

If only the known complaint about void pointer dereferencing
appears, then the file <scsi/sg.h> would come from somewhere else.

-------------------------------------------------------------

I am much interested in finding the cause of the failure.
Is there a chance that i could ssh-login into an equivalent
compiling environment ?
Some experiments with xorriso's source might help to get a clue.


Have a nice day :)

Thomas