seanjensengrey / pentoo

Automatically exported from code.google.com/p/pentoo
0 stars 0 forks source link

sys-kernel/ax88179_178a: warnings about section mismatch #95

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I get the same warnings when compiling the module w/o ebuild and users of the 
device mention no problems.

Still I'd like to solve these warnings:
WARNING: 
/var/tmp/portage/sys-kernel/ax88179_178a-1.3.0/work/AX88179_178A_LINUX_DRIVER_v1
.3.0_SOURCE/ax88179_178a.o(.data+0x40): Section mismatch in reference from the 
variable asix_driver to the function .text:ax_suspend()

WARNING: 
/var/tmp/portage/sys-kernel/ax88179_178a-1.3.0/work/AX88179_178A_LINUX_DRIVER_v1
.3.0_SOURCE/ax88179_178a.o(.data+0x48): Section mismatch in reference from the 
variable asix_driver to the function .text:ax_resume()

Original issue reported on code.google.com by Wuod...@gmail.com on 24 Feb 2013 at 12:45

Attachments:

GoogleCodeExporter commented 9 years ago
ASIX will fix this Warning compiler message issue in next revision 
AX88179/AX88178A Linux driver source soon. I will update the revised driver 
source onto AX88179 Driver Download web page 
(http://www.asix.com.tw/download.php?sub=driverdetail&PItemID=131) and here 
later when it is ready for release. Thanks a lot for your great feedback.

Original comment by allancho...@gmail.com on 25 Feb 2013 at 4:21

GoogleCodeExporter commented 9 years ago
zero@Nu ~ $ less 
/var/log/portage/sys-kernel:ax88179_178a-1.3.0:20130308-031653.log
 * Package:    sys-kernel/ax88179_178a-1.3.0
 * Repository: pentoo
 * USE:        amd64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/3.7.5-pentoo/build
 * Found sources for kernel version:
 *     3.7.5-pentoo
 * Checking for suitable kernel configuration options...
 [ ok ]
>>> Unpacking source...
>>> Unpacking AX88179_178A_LINUX_DRIVER_v1.3.0_SOURCE.tar.bz2 to 
/var/tmp/portage/sys-kernel/ax88179_178a-1.3.0/work
>>> Source unpacked in /var/tmp/portage/sys-kernel/ax88179_178a-1.3.0/work
>>> Preparing source in 
/var/tmp/portage/sys-kernel/ax88179_178a-1.3.0/work/AX88179_178A_LINUX_DRIVER_v1
.3.0_SOURCE ...
>>> Source prepared.
>>> Configuring source in 
/var/tmp/portage/sys-kernel/ax88179_178a-1.3.0/work/AX88179_178A_LINUX_DRIVER_v1
.3.0_SOURCE ...
>>> Source configured.
>>> Compiling source in 
/var/tmp/portage/sys-kernel/ax88179_178a-1.3.0/work/AX88179_178A_LINUX_DRIVER_v1
.3.0_SOURCE ...
ln: failed to create symbolic link <E2><80><98>Module.symvers<E2><80><99>: File 
exists
 * Preparing ax88179_178a module
make -j32 -l32 HOSTCC=x86_64-pc-linux-gnu-gcc 
CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' default 
make -C /lib/modules/3.7.0-pentoo-r1/build 
SUBDIRS=/var/tmp/portage/sys-kernel/ax88179_178a-1.3.0/work/AX88179_178A_LINUX_D
RIVER_v1.3.0_SOURCE modules
make[1]: Entering directory `/usr/src/linux-3.7.0-pentoo-r1'
make[1]: *** No rule to make target `modules'.  Stop.
make[1]: Leaving directory `/usr/src/linux-3.7.0-pentoo-r1'
make: *** [default] Error 2
 * ERROR: sys-kernel/ax88179_178a-1.3.0 failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sys-kernel/ax88179_178a-1.3.0'`,
 * the complete build log and the output of `emerge -pqv '=sys-kernel/ax88179_178a-1.3.0'`.
 * This ebuild is from an overlay named 'pentoo': '/usr/src/pentoo/portage/trunk/'
 * The complete build log is located at '/var/log/portage/sys-kernel:ax88179_178a-1.3.0:20130308-031653.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sys-kernel/ax88179_178a-1.3.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/ax88179_178a-1.3.0/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-kernel/ax88179_178a-1.3.0/work/AX88179_178A_LINUX_DRIVER_v1.3.0_SOURCE'
 * S: '/var/tmp/portage/sys-kernel/ax88179_178a-1.3.0/work/AX88179_178A_LINUX_DRIVER_v1.3.0_SOURCE'

It doesn't build, why it no build?

Original comment by sidhayn on 8 Mar 2013 at 3:18

GoogleCodeExporter commented 9 years ago
The attached revised AX88179/AX88178A Linux driver source v1.4.0 Beta4 should 
be able to solve the previous "Section mismatch" compiler warning message 
issue. Please help to confirm this point and let us know your test results soon 
for further process. 

For the new "emake failed" compiler failure issue, we don't know what the error 
message means? Please double check if this issue was still happened on the 
revised driver source or not? If yes, please let us know what are the compiler 
environment differences between the previous "Section mismatch" compiler 
warning message issue and the new issue for further investigation. Thanks a lot.

Original comment by allancho...@gmail.com on 8 Mar 2013 at 6:24

Attachments:

GoogleCodeExporter commented 9 years ago
The emake failed is very likely not your error Allan.  Most likely it is a 
gentoo related issue based on how we are automatically building it.  The most 
likely cause it my local kernel sources are messed up in some way.

We will test the new beta driver for you gladly.  Aside from the compiler 
warnings being fixed is there anything we need to be aware of?

Original comment by sidhayn on 8 Mar 2013 at 1:48

GoogleCodeExporter commented 9 years ago
This ASIX's AX88179 revised linux driver had modified to improve some issues 
found during the Linux kernel mainline driver submission. 

The ax88179_178a.c driver had been successfully submitted onto Linux kernel 
mainline source on Mar. 3rd. You can refer to the "Re: [PATCH resubmit] 
ax88179_178a: ASIX AX88179_178A USB 3.0/2.0 to gigabit ethernet adapter driver" 
driver patch submission thread 
(http://article.gmane.org/gmane.linux.kernel/1450119/match=ax88179_178a) for 
details. 

Please let us know if you had found any issue on this driver. Thanks a lot.

Original comment by allancho...@gmail.com on 8 Mar 2013 at 3:19

GoogleCodeExporter commented 9 years ago
Allan,

Please ignore my original complaint of build failure, that was (as I expected) 
completely on my end.

here are the warnings from your 1.4.0_beta4 which you attached to this ticket

  CC [M]  /var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/work/AX88179_178A_LINUX_DRIVER_v1.4.0_SOURCE/ax88179_178a.o
/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/work/AX88179_178A_LINUX_DRI
VER_v1.4.0_SOURCE/ax88179_178a.c: In function 'ax88179_write_cmd_async':
/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/work/AX88179_178A_LINUX_DRI
VER_v1.4.0_SOURCE/ax88179_178a.c:260:1: note: Function ax88179_write_cmd_async 
is missing from the size_overflow hash table +ax88179_write_cmd_async+5+16671+
/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/work/AX88179_178A_LINUX_DRI
VER_v1.4.0_SOURCE/ax88179_178a.c:260:1: note: Function ax88179_write_cmd_async 
is missing from the size_overflow hash table +ax88179_write_cmd_async+5+16671+

I'm more than happy to build test things for you, I have a user with your 
hardware already and I've been meaning to buy a few so I'll have to get on that 
now that the module builds ;-)

Original comment by sidhayn on 11 Mar 2013 at 4:28

GoogleCodeExporter commented 9 years ago
For the "is missing from the size_overflow hash table" warning message, you can 
visit the grsecurity forums 
(http://forums.grsecurity.net/viewtopic.php?f=7&t=3043) to get some hints as 
below to improve this issue and let us know if you found any issues on our 
latest AX88179 Linux driver source. Thanks a lot. 

=======

If the marked function's parameter can be traced back to a parameter of the 
caller then the plugin checks if the caller is already in the hash table (or it 
is marked with the attribute). If it isn't then the plugin prints the following 
message:
Code: Select allFunction %s is missing from the size_overflow hash table 
+%s+%d+%u+" (caller's name, parameter's number, hash)
If anyone sees this message, please send it to me by e-mail 
(re.emese@gmail.com) so that I can put the caller into the hash table, 
otherwise the plugin will not apply the overflow check to it.
....

Original comment by allancho...@gmail.com on 11 Mar 2013 at 9:01

GoogleCodeExporter commented 9 years ago
Allan 

Warnings like:
Function foo is missing from the size overflow has table"
are related to us using the hardened kernel.

Thanks a lot for your responses, I'll look at that new driver!

= Details about the warnings "Function is missing from the size_overflow hash 
table" =
The build log of other packages which build kernel modules is also full of 
those warnings, see for example compat-{wireless,drivers}.

We enable the "size overflow plugin" of the PaX set of patches to the kernel by 
setting CONFIG_PAX_SIZE_OVERFLOW=y in our kernel config, see:
Inside the Size Overflow Plugin: 
http://forums.grsecurity.net/viewtopic.php?f=7&t=3043

Didn't have time to understand all of that, but seems there's a hash table for 
the kernel functions and additional modules from other sources are not in that 
hash table.
Quote from the bottom of that article:
[quote]If anyone's interested in compiling other userland programs with the 
plugin then please send the hash table and the patch to me please :).[/quote]

Original comment by Wuod...@gmail.com on 11 Mar 2013 at 9:08

GoogleCodeExporter commented 9 years ago
 Any progress on this - here's my log from trying to ebuild this tonight.  I know I have had a working ASIX module previous for the StarTech.com USB31000S USB 3.0 USB-LAN adapter but it's no longer working.

* Could not find a Makefile in the kernel source directory.
 * Please ensure that /usr/src/linux points to a complete set of Linux sources
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Could not find a usable .config in the kernel source directory.
 * Please ensure that /usr/src/linux points to a configured set of Linux sources.
 * If you are using KBUILD_OUTPUT, please set the environment var so that
 * it points to the necessary object directory so that it might find .config.
 * ERROR: sys-kernel/ax88179_178a-1.4.0_beta4 failed (setup phase):
 *   Kernel not configured; no .config found in 
 * 
 * Call stack:
 *           ebuild.sh, line  93:  Called pkg_setup
 *           ebuild.sh, line 326:  Called linux-mod_pkg_setup
 *    linux-mod.eclass, line 561:  Called linux-info_pkg_setup
 *   linux-info.eclass, line 907:  Called check_extra_config
 *   linux-info.eclass, line 717:  Called require_configured_kernel
 *   linux-info.eclass, line 294:  Called die
 * The specific snippet of code:
 *          die "Kernel not configured; no .config found in ${KV_OUT_DIR}"
 * 
 * If you need support, post the output of `emerge --info '=sys-kernel/ax88179_178a-1.4.0_beta4'`,
 * the complete build log and the output of `emerge -pqv '=sys-kernel/ax88179_178a-1.4.0_beta4'`.
 * This ebuild is from an overlay named 'pentoo': '/var/lib/layman/pentoo/'
 * The complete build log is located at '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4'
 * S: '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/work/AX88179_178A_LINUX_DRIVER_v1.4.0_SOURCE'
 * 
 * The following package has failed to build or install:
 * 
 *  (sys-kernel/ax88179_178a-1.4.0_beta4::pentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/temp/build.log'
 * 

I think it was a version 3 Beta that I had working earlier - trying to find the 
file now. 

Original comment by da.kah...@gmail.com on 13 May 2013 at 2:09

GoogleCodeExporter commented 9 years ago
your error says you have no .config file in your kernel sources. that's not our 
issue.

Original comment by sidhayn on 13 May 2013 at 1:13

GoogleCodeExporter commented 9 years ago
wi-spy linux # ls -al
total 5092
drwxr-xr-x 8 root root    4096 May  6 18:54 .
drwxr-xr-x 7 root root    4096 May 20 17:48 ..
-rw-r--r-- 1 root root 1031517 May 20 21:31 .config
-rw-r--r-- 1 root root     601 Mar  8 04:41 .missing-syscalls.d
drwxr-xr-x 2 root root    4096 Mar  8 04:41 .tmp_versions
-rw-r--r-- 1 root root  845721 Mar  5 19:38 Module.symvers
-rw-r--r-- 1 root root 3161849 Mar  5 19:29 System.map
drwxr-xr-x 3 root root    4096 May  6 18:54 arch
drwxr-xr-x 4 root root    4096 May  6 18:54 include
drwxr-xr-x 2 root root    4096 May  6 18:54 kernel
-rw-r--r-- 1 root root   14165 Mar  5 19:30 modules.builtin
-rw-r--r-- 1 root root  118470 Mar  5 19:37 modules.order
drwxr-xr-x 6 root root    4096 May  6 18:54 scripts
drwxr-xr-x 3 root root    4096 May  6 18:54 tools
wi-spy linux #

Directory listing shows the .config file as being present.  
Still getting same error even after replacing the .config file as suggested in 
the IRC.

lsmod returns:
wi-spy dakahuna # lsmod
Module                  Size  Used by
usbnet                 19088  0 
ipv6                  298870  26 
rfcomm                 33795  8 
bnep                   13217  2 
snd_hda_codec_hdmi     25721  1 
snd_hda_codec_realtek    57128  1 
joydev                 14277  0 
mousedev               10516  0 
samsung_laptop          9468  0 
iwldvm                106314  0 
mac80211              424448  1 iwldvm
snd_hda_intel          27691  3 
coretemp                6854  0 
snd_hda_codec         105634  3 
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
kvm_intel             116605  0 
snd_hwdep               7349  1 snd_hda_codec
uvcvideo               66908  0 
i915                  495858  2 
kvm                   379400  1 kvm_intel
snd_pcm                78066  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
intel_agp              11998  1 i915
iwlwifi                70120  1 iwldvm
btusb                  12348  0 
intel_gtt              15841  2 i915,intel_agp
videobuf2_vmalloc       3125  1 uvcvideo
videobuf2_memops        3493  1 videobuf2_vmalloc
bluetooth             177471  24 bnep,btusb,rfcomm
drm_kms_helper         29408  1 i915
videobuf2_core         24606  1 uvcvideo
snd_page_alloc          8919  2 snd_pcm,snd_hda_intel
hid_logitech_dj        11286  0 
snd_timer              22746  1 snd_pcm
cfg80211              169414  3 iwlwifi,mac80211,iwldvm
psmouse                67241  0 
snd                    73032  13 
snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_cod
ec,snd_hda_intel
videodev              116955  2 uvcvideo,videobuf2_core
microcode              12251  0 
rfkill                 17864  5 cfg80211,samsung_laptop,bluetooth
drm                   265520  3 i915,drm_kms_helper
media                  15220  2 uvcvideo,videodev
r8169                  49750  0 
i2c_algo_bit            5914  1 i915
lpc_ich                12342  0 
serio_raw               5252  0 
soundcore               7352  1 snd
mii                     5431  2 r8169,usbnet
i2c_i801               13801  0 
rtc_cmos                8882  0 
evdev                  12826  8 
iscsi_tcp               9170  0 
libiscsi_tcp           14850  1 iscsi_tcp
libiscsi               39990  2 libiscsi_tcp,iscsi_tcp
scsi_transport_iscsi    45195  2 iscsi_tcp,libiscsi
tg3                   121319  0 
e1000                  91847  0 
zfs                   770658  0 
zcommon                31401  1 zfs
znvpair                37309  2 zfs,zcommon
zavl                    4812  1 zfs
zunicode              316907  1 zfs
spl                    51924  5 zfs,zavl,zunicode,zcommon,znvpair
xfs                   894585  0 
jfs                   162070  0 
btrfs                 647916  0 
dm_raid                13170  0 
dm_snapshot            26118  0 
hid_sunplus             2380  0 
hid_sony                3539  0 
hid_samsung             3731  0 
hid_pl                  3090  0 
hid_petalynx            2837  0 
hid_monterey            2460  0 
hid_microsoft           3746  0 
hid_logitech           16750  0 
hid_gyration            3027  0 
hid_ezkey               2341  0 
hid_cypress             2781  0 
hid_chicony             3108  0 
hid_cherry              2436  0 
hid_belkin              2561  0 
hid_apple               6414  0 
hid_a4tech              2855  0 
sl811_hcd               9934  0 
hid_generic             2045  0 
usbhid                 39087  3 hid_pl,hid_logitech,hid_logitech_dj
mpt2sas               133683  0 
aic94xx                66197  0 
libsas                 61376  1 aic94xx
lpfc                  506686  0 
qla2xxx               404448  0 
megaraid_sas           69172  0 
megaraid               40563  0 
aacraid                78469  0 
sx8                    12534  0 
DAC960                 68285  0 
hpsa                   50890  0 
cciss                 102557  0 
3w_9xxx                31712  0 
3w_xxxx                22902  0 
mptsas                 35609  0 
scsi_transport_sas     29322  4 mpt2sas,libsas,mptsas,aic94xx
mptfc                  12036  0 
mptspi                 12728  0 
mptscsih               22585  3 mptfc,mptsas,mptspi
mptbase                64048  4 mptfc,mptsas,mptspi,mptscsih
atp870u                24301  0 
dc395x                 28652  0 
qla1280                20768  0 
imm                     9667  0 
parport                36523  1 imm
dmx3191d                9989  0 
sym53c8xx              64536  0 
gdth                   80563  0 
advansys               50795  0 
initio                 15974  0 
BusLogic               21071  0 
arcmsr                 25784  0 
aic7xxx               108437  0 
aic79xx               129772  0 
sg                     27276  0 
pata_pcmcia            10771  0 
pcmcia                 33992  1 pata_pcmcia
pcmcia_core            15379  1 pcmcia
wi-spy dakahuna # 

dmesg shows 
[   54.794155] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   84.162953] usb 3-2: new SuperSpeed USB device number 2 using xhci_hcd
[   84.177671] usb 3-2: Parent hub missing LPM exit latency info.  Power 
management will be impacted.

lsusb shows:

wi-spy dakahuna # lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 0b95:1790 ASIX Electronics Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer
Bus 001 Device 005: ID 8087:07da Intel Corp. 
Bus 001 Device 006: ID 2232:1024  
wi-spy dakahuna # 

error remains

wi-spy dakahuna # emerge ax88179_178a

 * IMPORTANT: 1 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild   R   ~] sys-kernel/ax88179_178a-1.4.0_beta4::pentoo  0 kB

Total: 1 package (1 reinstall), Size of downloads: 0 kB

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) sys-kernel/ax88179_178a-1.4.0_beta4 from pentoo
 * AX88179_178A_LINUX_DRIVER_v1.4.0_BETA4_SOURCE.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ...            [ ok ]
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Could not find a Makefile in the kernel source directory.
 * Please ensure that /usr/src/linux points to a complete set of Linux sources
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Could not find a usable .config in the kernel source directory.
 * Please ensure that /usr/src/linux points to a configured set of Linux sources.
 * If you are using KBUILD_OUTPUT, please set the environment var so that
 * it points to the necessary object directory so that it might find .config.
 * ERROR: sys-kernel/ax88179_178a-1.4.0_beta4 failed (setup phase):
 *   Kernel not configured; no .config found in 
 * 
 * Call stack:
 *           ebuild.sh, line  93:  Called pkg_setup
 *           ebuild.sh, line 326:  Called linux-mod_pkg_setup
 *    linux-mod.eclass, line 561:  Called linux-info_pkg_setup
 *   linux-info.eclass, line 907:  Called check_extra_config
 *   linux-info.eclass, line 717:  Called require_configured_kernel
 *   linux-info.eclass, line 294:  Called die
 * The specific snippet of code:
 *          die "Kernel not configured; no .config found in ${KV_OUT_DIR}"
 * 
 * If you need support, post the output of `emerge --info '=sys-kernel/ax88179_178a-1.4.0_beta4'`,
 * the complete build log and the output of `emerge -pqv '=sys-kernel/ax88179_178a-1.4.0_beta4'`.
 * This ebuild is from an overlay named 'pentoo': '/var/lib/layman/pentoo/'
 * The complete build log is located at '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4'
 * S: '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/work/AX88179_178A_LINUX_DRIVER_v1.4.0_SOURCE'

>>> Failed to emerge sys-kernel/ax88179_178a-1.4.0_beta4, Log file:

>>>  '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/temp/build.log'

 * Messages for package sys-kernel/ax88179_178a-1.4.0_beta4:

 * Could not find a Makefile in the kernel source directory.
 * Please ensure that /usr/src/linux points to a complete set of Linux sources
 * Unable to calculate Linux Kernel version for build, attempting to use running version
 * Could not find a usable .config in the kernel source directory.
 * Please ensure that /usr/src/linux points to a configured set of Linux sources.
 * If you are using KBUILD_OUTPUT, please set the environment var so that
 * it points to the necessary object directory so that it might find .config.
 * ERROR: sys-kernel/ax88179_178a-1.4.0_beta4 failed (setup phase):
 *   Kernel not configured; no .config found in 
 * 
 * Call stack:
 *           ebuild.sh, line  93:  Called pkg_setup
 *           ebuild.sh, line 326:  Called linux-mod_pkg_setup
 *    linux-mod.eclass, line 561:  Called linux-info_pkg_setup
 *   linux-info.eclass, line 907:  Called check_extra_config
 *   linux-info.eclass, line 717:  Called require_configured_kernel
 *   linux-info.eclass, line 294:  Called die
 * The specific snippet of code:
 *          die "Kernel not configured; no .config found in ${KV_OUT_DIR}"
 * 
 * If you need support, post the output of `emerge --info '=sys-kernel/ax88179_178a-1.4.0_beta4'`,
 * the complete build log and the output of `emerge -pqv '=sys-kernel/ax88179_178a-1.4.0_beta4'`.
 * This ebuild is from an overlay named 'pentoo': '/var/lib/layman/pentoo/'
 * The complete build log is located at '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/temp/die.env'.
 * Working directory: '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4'
 * S: '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/work/AX88179_178A_LINUX_DRIVER_v1.4.0_SOURCE'
 * 
 * The following package has failed to build or install:
 * 
 *  (sys-kernel/ax88179_178a-1.4.0_beta4::pentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/sys-kernel/ax88179_178a-1.4.0_beta4/temp/build.log'
 * 
wi-spy dakahuna # ls -al /usr/src/linux/
total 5096
drwxr-xr-x 8 root root    4096 May 20 21:34 .
drwxr-xr-x 7 root root    4096 May 21 20:35 ..
-rw-r--r-- 1 root root 1031517 May 20 21:31 .config
-rw-r--r-- 1 root root     601 Mar  8 04:41 .missing-syscalls.d
drwxr-xr-x 2 root root    4096 Mar  8 04:41 .tmp_versions
-rw-r--r-- 1 root root  845721 Mar  5 19:38 Module.symvers
-rw-r--r-- 1 root root 3161849 Mar  5 19:29 System.map
drwxr-xr-x 3 root root    4096 May  6 18:54 arch
drwxr-xr-x 4 root root    4096 May  6 18:54 include
drwxr-xr-x 2 root root    4096 May  6 18:54 kernel
-rw-r--r-- 1 root root   14165 Mar  5 19:30 modules.builtin
-rw-r--r-- 1 root root  118470 Mar  5 19:37 modules.order
drwxr-xr-x 6 root root    4096 May  6 18:54 scripts
drwxr-xr-x 3 root root    4096 May  6 18:54 tools
-rw-r--r-- 1 root root     968 May 20 21:34 usr-src-linux.txt
wi-spy dakahuna # 

Original comment by da.kah...@gmail.com on 22 May 2013 at 12:52

GoogleCodeExporter commented 9 years ago
Here are the file attachments from the emerge failure. 

Original comment by da.kah...@gmail.com on 22 May 2013 at 1:04

Attachments:

GoogleCodeExporter commented 9 years ago
this is all fine, and hopefully someday going into the kernel so I can drop 
this ebuild

Original comment by sidhayn on 22 May 2013 at 2:16