Re: [FFADO-devel] [FFADO] #374: compile error on powerpc64-unknown-linux-gnu

[FFADO <ffa...@ff...>]

#374: compile error on powerpc64-unknown-linux-gnu
-----------------------+----------------------------------------------------
   Reporter:  visteya  |       Owner:                                                   
       Type:  bug      |      Status:  new                                              
   Priority:  minor    |   Milestone:                                                   
  Component:  generic  |     Version:  FFADO SVN (trunk)                                
 Resolution:           |    Keywords:  debian powerpc64 predefs.h ELFCLASS64  ELFCLASS32
Device_name:           |  
-----------------------+----------------------------------------------------
Comment (by jwoithe):

 Thanks for the reply and no need to apologise.  My comments were as much
 to document the current situation for future readers of this ticket.

 Since you are willing to work on this I am more than happy for you to do
 so.  It will be much easier for you to do this since you have the hardware
 and software environment which is affected.

 It is true that multiarch complicates things, not so much because it
 exists but because the default width is different depending on the
 architecture (x86, ppc).  In the first instance I think the default
 behaviour of our build environment should target the default width, but
 rather than assume what this might be we should try to come up with a test
 which can confirm it.

 The "file/grep" solution may work so long as there was a definitive file
 name we could check which was guaranteed to apply to the "default"
 compilation environment.  Failing this we may have to arrange for a small
 trivial C program to be compiled using default flags; this could then be
 tested using file/grep (or some binutils utility yet to be identified) to
 see what width it is compiled for.

 Regarding the file/grep, I'm fairly certain that one of the binutils
 programs has a flag which can be used to report the object type (at least
 as far as 32/64 bit goes).  If this provides a more reliable output
 compared to "file" it might be worth looking into it.  In the meantime,
 "file" should be fine.

-- 
Ticket URL: <http://subversion.ffado.org/ticket/374#comment:7>
FFADO <http://subversion.ffado.org/index.fcgi>
Free Firewire Audio Drivers