Welcome, Guest. Please login or register.
Did you miss your activation email?
Monday 16 December 2024, 04:39:48 am

Login with username, password and session length

Visit the Official Endian Bug tracker  HERE
14261 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  General Support
| | |-+  Compiling software in efw 2.4.1
0 Members and 2 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Compiling software in efw 2.4.1  (Read 15920 times)
coanda
Full Member
***
Offline Offline

Posts: 13


« on: Thursday 11 August 2011, 04:30:00 am »

I'm totally new to EFW but not to Linux or compiling software. I've read forum posts that say to install build-essential with smart but when I try to do that I get " error: 'build-essential' matches no packages ", I thought perhaps I need to add some channels (which I assume is smart nomenclature for repositories) but I can't find any documentation on how to do that or where to find them.

Searching for gcc, make, or the kernel headers comes up empty, but I guess that they're in the development channel if I ever find it. I'm running on an Atom processor and don't really want to set up a toolchain for cross-compiling on my x86_64 desktop.

Any help would be great, thanks.
Logged
coanda
Full Member
***
Offline Offline

Posts: 13


« Reply #1 on: Thursday 11 August 2011, 04:53:47 am »

Apparently the command efw-upgrade lets you choose a development version which might have the tools that I need but when I ran that command it asked me for a user name and I didn't realize that it wanted one for the site it was connecting to. Anyways, now efw-upgrade fails to locate the file that it needs and I can't find where you would go to reset this tool.

Does anyone have any idea where I would go to clear out the settings that I made running efw-upgrade the first time?
Logged
coanda
Full Member
***
Offline Offline

Posts: 13


« Reply #2 on: Thursday 11 August 2011, 05:14:26 am »

No man page, no --help output, not really much in the way of useful documentation on how to do some of this. I guess what can you really expect from a community version.

Turns out that "efw-upgrade -s" will let you re-select the channel to use.

Moving on, turns out that no matter what I use for a username on either the production or development channel I get the same errors, I read something that said to use your email address but this is all that I get:

Code:
root@fw1:~ # efw-upgrade -s
Please choose the appropriate channel for your environment and hit [ENTER]:
1) Production (stable releases)
2) Development (bleeding edge)
2
Please enter your username and hit [ENTER]:
email@address


Loading cache...
Updating cache...                                                            ############################################################################################################# [100%]

Fetching information for 'efw-community'...                                                                                                                                                      
-> h t t p : / / email@address:*@updates.endian.org / devel / repodata / repomd.xml                                                                                                                
repomd.xml                                                                                                                                                                                 [ 25%]
error: Failed acquiring release file for 'efw-community':                                                                                                                                        
error: h t t p : / / email%40address:community@updates.endian.org / devel / repodata / repomd.xml: The requested URL returned error: 401

Updating cache...                                                            ############################################################################################################# [100%]

Channels have no new packages.
ERROR: Error during upgrade

Sorry, I had to mangle the link text because the forum says that I can't post clickable links.
Logged
coanda
Full Member
***
Offline Offline

Posts: 13


« Reply #3 on: Thursday 11 August 2011, 05:19:38 am »

Turns out that you have to register at endian.com/en/community/efw-updates/, but I stll get "channels have no new packages" so I don't think this is the solution that I'm looking for.
Logged
coanda
Full Member
***
Offline Offline

Posts: 13


« Reply #4 on: Thursday 11 August 2011, 08:21:24 am »

No updates available on either channel.

On the sourceforge page I found the package EFW-COMMUNITY-2.4.1-devel-srpm-rpms.tar.gz that has the rpm files that I need but when you try to install them you get

Code:
root@fw1:~/EFW-COMMUNITY-2.4.1-201011120951/DEVEL_RPMS # rpm -ivh *
error: Failed dependencies:
libtool is needed by build-essential-0.4-endian3.i586
ncurses-devel is needed by build-essential-0.4-endian3.i586
libselinux-devel is needed by build-essential-0.4-endian3.i586
glibc-headers is needed by build-essential-0.4-endian3.i586
kernel-devel is needed by build-essential-0.4-endian3.i586
kernel-smp-devel is needed by build-essential-0.4-endian3.i586
rpm-build is needed by build-essential-0.4-endian3.i586
procinfo is needed by build-essential-0.4-endian3.i586
busybox is needed by build-essential-0.4-endian3.i586
newt-devel is needed by build-essential-0.4-endian3.i586
libsmooth is needed by build-essential-0.4-endian3.i586
kernel-PAE-devel is needed by build-essential-0.4-endian3.i586
zlib-devel is needed by build-essential-0.4-endian3.i586
glibc-devel >= 2.2.90-12 is needed by gcc-3.4.6-10.endian8.i586
glibc-devel >= 2.2.90-12 is needed by gcc4-4.1.2-14.endian1.i586

Another forum eluded to the fact that the developers didn't want to give out these packages but that seems pretty dumb to me. Does anyone know where I can find these rpms?
Logged
coanda
Full Member
***
Offline Offline

Posts: 13


« Reply #5 on: Thursday 11 August 2011, 08:47:50 am »

I individually installed the devel rpms but had to --nodeps on gcc and build-essential but now I need the kernel headers to be able to compile a module for my kernel. I'd ask for help again but by the activity in this forum I'd say that's pretty much pointless, I'm reading 6 month old posts from people asking the same questions that appear to have been abandoned altogether. At this point I'm just trying to provide information for the next sorry sap that's trying to figure this out.
Logged
coanda
Full Member
***
Offline Offline

Posts: 13


« Reply #6 on: Thursday 11 August 2011, 09:36:22 am »

It's starting to look like the last version of Endian that you could get the kernel-devel package for was 2.2. That's pretty stupid if you ask me.
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.078 seconds with 19 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com