New answers tagged compiling
0
I'm experiencing what seems to be the same issue: whereas other packages end up building an executable and then stripping it into the directory ./project_build_arm/my_device/root/usr/bin/ , the package I added gets built and then stripped into ./build_arm/staging_dir/usr/bin/ instead.
To work around this problem, currently all I do is copy the stripped ...
0
It's a shot in the dark, but since LiS looks like it involves a kernel module (http://www.gcom.com/home/linux/lis/index.html), you probably need the kernel development package.
So try running this as root:
yum -y install kernel-devel kernel-headers
Will it build now?
0
So the solutions is really simple take the latest source from:
https://github.com/lwfinger
make & make install
So this works well for realtek-8723.
And there is a small blog post I wrote about it -> http://l33tsource.com/blog/2013/05/08/Yoga-with-WLAN.html
1
You can use the following steps to compile tmux 1.7 on CentOS 5.8:
Install developer tools
yum groupinstall "Development Libraries"
yum groupinstall "Development Tools"
yum install rpm-build gcc
Setup .rpmmacros file
$ cat > /home/<myusername>/.rpmmacros << EOF
%packager Your Name
%vendor Your Orgnazation
%_topdir ...
0
Fedora has rather new kernels, often the driver sources floating around are for older kernel versions. Check the requisite kernel version, rummage through the Fedora fora, check for possibly relevant bug reports, look for not-yet-official drivers by the kernel hackers (not the vendor; vendors often live under the illusion that it is possible to have one ...
0
You tried this?
int __devinit = rtl_pci_probe(struct pci_dev *pdev,const struct pci_device_id *id);
3
I would take a look a these CentOS howtos to get started. CentOS is the community edition of RHEL. It's pretty much identical to what Red Hat provides in their version of the distro.
I Need to Build a Custom Kernel
I Need the Kernel Source
How To Compile A Kernel - The CentOS Way
3
The actual lines around 679 in Lib/test/regrtest.py are:
NOTTESTS = {
'test_support',
'test_future1',
'test_future2',
}
This defines a mutable set and is syntax back-ported from 3.1 to 2.7. This syntax is not available in 2.6 or earlier version of python.
That your test raises a syntax error is probably because your default python is pre-2.7. ...
1
You can update MANPATH (as well as INFOPATH) to point at your personal directory's man pages. Unfortunately, there's no single way to tell software to also look in your include paths. You might have to set CFLAGS (but not always) or other variable used in the build system.
1
It seems latest vizzini driver supports kernel versions <= 3.4.x
Top 50 recent answers are included
