[powerpc] ftbfs (ql4_nx.c:788:3: error: implicit declaration of function)

[Matthias Klose]

2.6.38-6.34

no verbose build logs available

  CC [M] drivers/scsi/qla4xxx/ql4_nx.o
  CC [M] drivers/net/tulip/pnic.o
/build/buildd/linux-2.6.38/drivers/scsi/qla4xxx/ql4_nx.c: In function 'qla4_8xxx_pci_mem_read_direct':
/build/buildd/linux-2.6.38/drivers/scsi/qla4xxx/ql4_nx.c:717:3: error: implicit declaration of function 'readq'
/build/buildd/linux-2.6.38/drivers/scsi/qla4xxx/ql4_nx.c: In function 'qla4_8xxx_pci_mem_write_direct':
/build/buildd/linux-2.6.38/drivers/scsi/qla4xxx/ql4_nx.c:788:3: error: implicit declaration of function 'writeq'
make[5]: *** [drivers/scsi/qla4xxx/ql4_nx.o] Error 1
make[4]: *** [drivers/scsi/qla4xxx] Error 2
make[3]: *** [drivers/scsi] Error 2

[Jeremy Foshee (jeremyfoshee)]

Hi Matthias,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 733805

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Matthias Klose (doko)]

please ask for a dist-upgrade of the powerpc test machine (davis), and recheck if the kernel builds.

[Lee Jones (lag)]

If this is still an issue, can you post the config you're using?

[Jeremy Foshee (jeremyfoshee)]

Fix Releasing as this seems to have been fixed.

~JFO