25 Listopada 2024 05:24:21
Nawigacja
· Strona Główna
· Forum

· Tomato by Shibby
· FreshTomato


Wątki na forum
Najnowsze dyskusje
· DIR868l OFW asus vs ...
· Nowe routery: UX, UC...
· [S] Asus RT-AC56U
· Szukam zaproszenia n...
· [MOD] FreshTomato-AR...
· Asus RT-AC5300 ,prob...
· archer c6 v3.20
· [S] Nighthawk R7000P...
· [S]Asus RT-AC5300 - ...
· Tanie N100 na promce...
· net z telefonu wifi+...
· Tomato - bugi/proble...
· HUAWEI z światłowodem
· Asus TUF-AX3000_V2 p...
· rt-ax88upro częste ...
· [Howto] Xpenology na...
· Jaki router pod Open...
· Ruter z tomato
· Czy to jeszcze NAS?
· RT AC66U B1
Najpopularniejsze obecnie wątki
· DIR868l OFW asus ... [11]
· Nowe routery: UX,... [0]
· [S] Asus RT-AC56U [0]
Ankieta
Jaki procesor posiada twój router?

Broadcom MIPSEL
Broadcom MIPSEL
36% [151 głosów]

Broadcom ARM
Broadcom ARM
52% [219 głosów]

Atheros
Atheros
5% [22 głosów]

Marvell
Marvell
1% [4 głosów]

Ralink
Ralink
1% [3 głosów]

Intel/AMD/VIA
Intel/AMD/VIA
1% [5 głosów]

Żaden z powyższych
Żaden z powyższych
4% [15 głosów]

Ogółem głosów: 419
Musisz zalogować się, aby móc zagłosować.
Rozpoczęto: 02/02/2015 09:38
Twoje IP
3.147.27.129
Zobacz wątek
OpenLinksys » :: OPROGRAMOWANIE :: » Tomato - firmware
 Drukuj wątek
automake
djecstasy
Witam
Chciałem coś samemu skompilować pod tomato jednak natrafiłem na mały problem. Otóż zainstalowałem automake z optware jednak dostaję błąd

-sh: automake: not found

Ktoś miał podobnie? W czym może tkwić problem?
 
shibby
bo to nie tak się robi. Ściągnij źródła nslu2 i stwórz target ddwrt dla mipsel lub mbwe-bluering dla arm.

Wtedy możesz kompilować paczki ipk dla Tomato.
Router: Unifi Cloud Gateway Max
Switch: Netgear MS510TXPP
Switch: Unifi USW-Flex-Mini - szt. 2
Wi-Fi: Unifi U6-Lite - szt. 2
Proxmox VE: i5-13400T, 64GB RAM, 2x 512GB NVMe, 3x 2TB SSD, Intel X710-DA2 SFP+
VM #1: Synology SA6400
VM #2: Debian, WWW
VM #3: Home Assistant OS
 
djecstasy
Ok już poczytałem mniej więcej wiem o co chodzi ale niestety tylko mniej więcej ...
A więc tak wykonałem:

apt-get install gcc cvs flex bison make pkg-config rsync gettext libglib2.0-dev autoconf libtool automake automake1.9 sudo patch bzip2 wget sed texinfo subversion
cd ~ && svn co http://svn.nslu2-linux.org/svnroot/optware/trunk optware
cd optware && make ddwrt-target
wget -P downloads ftp://debian.lcs.mit.edu/pub/linux/devel/binutils//binutils-2.17.50.0.8.tar.bz2
wget -P downloads http://ftp.gnu.org/gnu/gdb/gdb-6.5a.tar.bz2
mv downloads/gdb-6.5a.tar.bz2 downloads/gdb-6.5.tar.bz2
cd ddwrt && make directories toolchain ipkg-utils

No na tym stanąłem. Chcę skompilować jedną paczkę ipk ale nie wiem co dalej:/
 
shibby
jeżeli to wykonałeś to musisz w katalogu ddwrt/make zrobić plik *.mk dla tej paczki. Następnie wracasz do katalogu dd-wrt i wydajesz komendę
make paczka-ipk

Jak się wykona to w katalogu build będziesz miał paczkę ipk
Router: Unifi Cloud Gateway Max
Switch: Netgear MS510TXPP
Switch: Unifi USW-Flex-Mini - szt. 2
Wi-Fi: Unifi U6-Lite - szt. 2
Proxmox VE: i5-13400T, 64GB RAM, 2x 512GB NVMe, 3x 2TB SSD, Intel X710-DA2 SFP+
VM #1: Synology SA6400
VM #2: Debian, WWW
VM #3: Home Assistant OS
 
djecstasy
Przy robieniu pliku .mk korzystałem z tego:

include $(TOPDIR)/rules.mk

PKG_NAME:=bridge
PKG_VERSION:=1.0.6
PKG_RELEASE:=1

PKG_SOURCE:=bridge-utils-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=@SF/bridge
PKG_MD5SUM:=9b7dc52656f5cbec846a7ba3299f73bd
PKG_CAT:=zcat

include $(INCLUDE_DIR)/package.mk

define Package/bridge
SECTION:=base
CATEGORY:=Network
DEFAULT:=y
TITLE:=Ethernet bridging configuration utility
DESCRIPTION:=Ethernet bridging configuration utility\\\
Manage ethernet bridging; a way to connect networks together to\\\
form a larger network.
URL:=http://bridge.sourceforge.net/
endef

define Build/Configure
$(call Build/Configure/Default,--with-linux-headers=$(LINUX_DIR))
endef

define Package/bridge/install
install -m0755 -d $(1)/usr/sbin
install -m0755 $(PKG_BUILD_DIR)/brctl/brctl $(1)/usr/sbin/
endef

$(eval $(call BuildPackage,bridge))

Przy próbie wykonania make:

/rules.mk: No such file or directory
/package.mk: No such file or directory
make: *** No rule to make target `/package.mk'.  Stop.
 
shibby
to jest plik z openwrt. To nie przejdzie. Zobacz jak wygląda struktura plików mk w toolchainie nslu2.

btw po co ci bridge skoro w tomato już jest? Co dokładnie potrzebujesz?
Router: Unifi Cloud Gateway Max
Switch: Netgear MS510TXPP
Switch: Unifi USW-Flex-Mini - szt. 2
Wi-Fi: Unifi U6-Lite - szt. 2
Proxmox VE: i5-13400T, 64GB RAM, 2x 512GB NVMe, 3x 2TB SSD, Intel X710-DA2 SFP+
VM #1: Synology SA6400
VM #2: Debian, WWW
VM #3: Home Assistant OS
 
djecstasy
A no tak. Chciałem skompilować readymedia-transcode stąd: https://bitbucket.org/stativ/readymedia-transcode bo podobno działa na nim radio internetowe na zwykłym minidlna niestety nie działa.

Połączony z 05 March 2015 08:49:34:
readymedia-transcode.mk:

###########################################################
#
# readymedia-transcode
#
###########################################################

# You must replace "readymedia-transcode" and "READYMEDIA-TRANSCODE" with the lower case name and
# upper case name of your new package.  Some places below will say
# "Do not change this" - that does not include this global change,
# which must always be done to ensure we have unique names.

#
# READYMEDIA-TRANSCODE_VERSION, READYMEDIA-TRANSCODE_SITE and READYMEDIA-TRANSCODE_SOURCE define
# the upstream location of the source code for the package.
# READYMEDIA-TRANSCODE_DIR is the directory which is created when the source
# archive is unpacked.
# READYMEDIA-TRANSCODE_UNZIP is the command used to unzip the source.
# It is usually "zcat" (for .gz) or "bzcat" (for .bz2)
#
# You should change all these variables to suit your package.
# Please make sure that you add a description, and that you
# list all your packages' dependencies, seperated by commas.
#
# If you list yourself as MAINTAINER, please give a valid email
# address, and indicate your irc nick if it cannot be easily deduced
# from your name or email address.  If you leave MAINTAINER set to
# "NSLU2 Linux" other developers will feel free to edit.
#
READYMEDIA-TRANSCODE_SITE=http://sourceforge.net/projects/readymediatranscodeddwrt/files/
READYMEDIA-TRANSCODE_VERSION=1.0
READYMEDIA-TRANSCODE_SOURCE=readymedia-transcode-$(READYMEDIA-TRANSCODE_VERSION).tar.gz
READYMEDIA-TRANSCODE_DIR=readymedia-transcode-$(READYMEDIA-TRANSCODE_VERSION)
READYMEDIA-TRANSCODE_UNZIP=zcat
READYMEDIA-TRANSCODE_MAINTAINER=NSLU2 Linux
READYMEDIA-TRANSCODE_DESCRIPTION=Describe readymedia-transcode here.
READYMEDIA-TRANSCODE_SECTION=
READYMEDIA-TRANSCODE_PRIORITY=optional
READYMEDIA-TRANSCODE_DEPENDS=
READYMEDIA-TRANSCODE_SUGGESTS=
READYMEDIA-TRANSCODE_CONFLICTS=

#
# READYMEDIA-TRANSCODE_IPK_VERSION should be incremented when the ipk changes.
#
READYMEDIA-TRANSCODE_IPK_VERSION=1

#
# READYMEDIA-TRANSCODE_CONFFILES should be a list of user-editable files
#READYMEDIA-TRANSCODE_CONFFILES=/opt/etc/readymedia-transcode.conf /opt/etc/init.d/SXXreadymedia-trans$

#
# READYMEDIA-TRANSCODE_PATCHES should list any patches, in the the order in

# which they should be applied to the source code.
#
# READYMEDIA-TRANSCODE_PATCHES=$(READYMEDIA-TRANSCODE_SOURCE_DIR)/configure.patch

#
# If the compilation of the package requires additional
# compilation or linking flags, then list them here.
#
READYMEDIA-TRANSCODE_CPPFLAGS=
READYMEDIA-TRANSCODE_LDFLAGS=

#
# READYMEDIA-TRANSCODE_BUILD_DIR is the directory in which the build is done.
# READYMEDIA-TRANSCODE_SOURCE_DIR is the directory which holds all the
# patches and ipkg control files.
# READYMEDIA-TRANSCODE_IPK_DIR is the directory in which the ipk is built.
# READYMEDIA-TRANSCODE_IPK is the name of the resulting ipk files.
#
# You should not change any of these variables.
#
READYMEDIA-TRANSCODE_BUILD_DIR=$(BUILD_DIR)/readymedia-transcode
READYMEDIA-TRANSCODE_SOURCE_DIR=$(SOURCE_DIR)/readymedia-transcode
READYMEDIA-TRANSCODE_IPK_DIR=$(BUILD_DIR)/readymedia-transcode-$(READYMEDIA-TRANSCODE_VERSION)-ipk
READYMEDIA-TRANSCODE_IPK=$(BUILD_DIR)/readymedia-transcode_$(READYMEDIA-TRANSCODE_VERSION)-$(READYMEDI$

.PHONY: readymedia-transcode-source readymedia-transcode-unpack readymedia-transcode readymedia-transc$

#
# This is the dependency on the source code.  If the source is missing,
# then it will be fetched from the site using wget.
#
$(DL_DIR)/$(READYMEDIA-TRANSCODE_SOURCE):
        $(WGET) -P $(@D) $(READYMEDIA-TRANSCODE_SITE)/$(@F) || \
        $(WGET) -P $(@D) $(SOURCES_NLO_SITE)/$(@F)

#
# The source code depends on it existing within the download directory.
# This target will be called by the top level Makefile to download the
# source code's archive (.tar.gz, .bz2, etc.)
#
readymedia-transcode-source: $(DL_DIR)/$(READYMEDIA-TRANSCODE_SOURCE) $(READYMEDIA-TRANSCODE_PATCHES)

#
# This target unpacks the source code in the build directory.
# If the source archive is not .tar.gz or .tar.bz2, then you will need
# to change the commands here.  Patches to the source code are also
# applied in this target as required.
#
# This target also configures the build within the build directory.
# Flags such as LDFLAGS and CPPFLAGS should be passed into configure
# and NOT $(MAKE) below.  Passing it to configure causes configure to
# correctly BUILD the Makefile with the right paths, where passing it
# to Make causes it to override the default search paths of the compiler.
#
# If the compilation of the package requires other packages to be staged
# first, then do that first (e.g. "$(MAKE) -stage -stage").
#
# If the package uses  GNU libtool, you should invoke $(PATCH_LIBTOOL) as
# shown below to make various patches to it.
#
$(READYMEDIA-TRANSCODE_BUILD_DIR)/.configured: $(DL_DIR)/$(READYMEDIA-TRANSCODE_SOURCE) $(READYMEDIA-T$
#       $(MAKE) -stage -stage
        rm -rf $(BUILD_DIR)/$(READYMEDIA-TRANSCODE_DIR) $(@D)
        $(READYMEDIA-TRANSCODE_UNZIP) $(DL_DIR)/$(READYMEDIA-TRANSCODE_SOURCE) | tar -C $(BUILD_DIR) -$
        if test -n "$(READYMEDIA-TRANSCODE_PATCHES)" ; \
                then cat $(READYMEDIA-TRANSCODE_PATCHES) | \
                patch -d $(BUILD_DIR)/$(READYMEDIA-TRANSCODE_DIR) -p0 ; \
        fi
        if test "$(BUILD_DIR)/$(READYMEDIA-TRANSCODE_DIR)" != "$(@D)" ; \
                then mv $(BUILD_DIR)/$(READYMEDIA-TRANSCODE_DIR) $(@D) ; \
        fi
        (cd $(@D); \
                $(TARGET_CONFIGURE_OPTS) \
                CPPFLAGS="$(STAGING_CPPFLAGS) $(READYMEDIA-TRANSCODE_CPPFLAGS)" \
                LDFLAGS="$(STAGING_LDFLAGS) $(READYMEDIA-TRANSCODE_LDFLAGS)" \
                ./configure \
                --build=$(GNU_HOST_NAME) \
                --host=$(GNU_TARGET_NAME) \
                --target=$(GNU_TARGET_NAME) \
                --prefix=/opt \
                --disable-nls \
                --disable-static \
        )
        $(PATCH_LIBTOOL) $(@D)/libtool
        touch $@

readymedia-transcode-unpack: $(READYMEDIA-TRANSCODE_BUILD_DIR)/.configured

#
# This builds the actual binary.
#
$(READYMEDIA-TRANSCODE_BUILD_DIR)/.built: $(READYMEDIA-TRANSCODE_BUILD_DIR)/.configured
        rm -f $@
        $(MAKE) -C $(@D)
        touch $@

#
# This is the build convenience target.
#
readymedia-transcode: $(READYMEDIA-TRANSCODE_BUILD_DIR)/.built

#
# If you are building a library, then you need to stage it too.
#
$(READYMEDIA-TRANSCODE_BUILD_DIR)/.staged: $(READYMEDIA-TRANSCODE_BUILD_DIR)/.built
        rm -f $@
        $(MAKE) -C $(@D) DESTDIR=$(STAGING_DIR) install
        touch $@
 
readymedia-transcode-stage: $(READYMEDIA-TRANSCODE_BUILD_DIR)/.staged

#
# This rule creates a control file for ipkg.  It is no longer
# necessary to create a seperate control file under sources/readymedia-transcode
#
$(READYMEDIA-TRANSCODE_IPK_DIR)/CONTROL/control:
        @install -d $(@D)
        @rm -f $@
        @echo "Package: readymedia-transcode" >>$@
        @echo "Architecture: $(TARGET_ARCH)" >>$@
        @echo "Priority: $(READYMEDIA-TRANSCODE_PRIORITY)" >>$@
        @echo "Section: $(READYMEDIA-TRANSCODE_SECTION)" >>$@
        @echo "Version: $(READYMEDIA-TRANSCODE_VERSION)-$(READYMEDIA-TRANSCODE_IPK_VERSION)" >>$@
        @echo "Maintainer: $(READYMEDIA-TRANSCODE_MAINTAINER)" >>$@
        @echo "Source: $(READYMEDIA-TRANSCODE_SITE)/$(READYMEDIA-TRANSCODE_SOURCE)" >>$@
        @echo "Description: $(READYMEDIA-TRANSCODE_DESCRIPTION)" >>$@
         @echo "Depends: $(READYMEDIA-TRANSCODE_DEPENDS)" >>$@
        @echo "Suggests: $(READYMEDIA-TRANSCODE_SUGGESTS)" >>$@
        @echo "Conflicts: $(READYMEDIA-TRANSCODE_CONFLICTS)" >>$@

#
# This builds the IPK file.
#
# Binaries should be installed into $(READYMEDIA-TRANSCODE_IPK_DIR)/opt/sbin or $(READYMEDIA-TRANSCODE$
# (use the location in a well-known Linux distro as a guide for choosing sbin or bin).
# Libraries and include files should be installed into $(READYMEDIA-TRANSCODE_IPK_DIR)/opt/{lib,includ$
# Configuration files should be installed in $(READYMEDIA-TRANSCODE_IPK_DIR)/opt/etc/readymedia-transc$
# Documentation files should be installed in $(READYMEDIA-TRANSCODE_IPK_DIR)/opt/doc/readymedia-transc$
# Daemon startup scripts should be installed in $(READYMEDIA-TRANSCODE_IPK_DIR)/opt/etc/init.d/S??read$
#
# You may need to patch your application to make it use these locations.
#
$(READYMEDIA-TRANSCODE_IPK): $(READYMEDIA-TRANSCODE_BUILD_DIR)/.built
        rm -rf $(READYMEDIA-TRANSCODE_IPK_DIR) $(BUILD_DIR)/readymedia-transcode_*_$(TARGET_ARCH).ipk
         $(MAKE) -C $(READYMEDIA-TRANSCODE_BUILD_DIR) DESTDIR=$(READYMEDIA-TRANSCODE_IPK_DIR) install-s$
#       install -d $(READYMEDIA-TRANSCODE_IPK_DIR)/opt/etc/
#       install -m 644 $(READYMEDIA-TRANSCODE_SOURCE_DIR)/readymedia-transcode.conf $(READYMEDIA-TRANS$
#       install -d $(READYMEDIA-TRANSCODE_IPK_DIR)/opt/etc/init.d
#       install -m 755 $(READYMEDIA-TRANSCODE_SOURCE_DIR)/rc.readymedia-transcode $(READYMEDIA-TRANSCO$
#       sed -i -e '/^#!/aOPTWARE_TARGET=${OPTWARE_TARGET}' $(READYMEDIA-TRANSCODE_IPK_DIR)/opt/etc/ini$
        $(MAKE) $(READYMEDIA-TRANSCODE_IPK_DIR)/CONTROL/control
#       install -m 755 $(READYMEDIA-TRANSCODE_SOURCE_DIR)/postinst $(READYMEDIA-TRANSCODE_IPK_DIR)/CON$
#       sed -i -e '/^#!/aOPTWARE_TARGET=${OPTWARE_TARGET}' $(READYMEDIA-TRANSCODE_IPK_DIR)/CONTROL/pos$
#       install -m 755 $(READYMEDIA-TRANSCODE_SOURCE_DIR)/prerm $(READYMEDIA-TRANSCODE_IPK_DIR)/CONTRO$
#       sed -i -e '/^#!/aOPTWARE_TARGET=${OPTWARE_TARGET}' $(READYMEDIA-TRANSCODE_IPK_DIR)/CONTROL/pre$
#       if test -n "$(UPD-ALT_PREFIX)"; then \
                sed -i -e '/^[  ]*update-alternatives /s|update-alternatives|$(UPD-ALT_PREFIX)/bin/&|'$
                        $(READYMEDIA-TRANSCODE_IPK_DIR)/CONTROL/postinst $(READYMEDIA-TRANSCODE_IPK_DI$
        fi
        echo $(READYMEDIA-TRANSCODE_CONFFILES) | sed -e 's/ /\n/g' > $(READYMEDIA-TRANSCODE_IPK_DIR)/C$
        cd $(BUILD_DIR); $(IPKG_BUILD) $(READYMEDIA-TRANSCODE_IPK_DIR)
        $(WHAT_TO_DO_WITH_IPK_DIR) $(READYMEDIA-TRANSCODE_IPK_DIR)
 
#
# This is called from the top level makefile to create the IPK file.
#
readymedia-transcode-ipk: $(READYMEDIA-TRANSCODE_IPK)

#
# This is called from the top level makefile to clean all of the built files.
#
readymedia-transcode-clean:
        rm -f $(READYMEDIA-TRANSCODE_BUILD_DIR)/.built
        -$(MAKE) -C $(READYMEDIA-TRANSCODE_BUILD_DIR) clean

#
# This is called from the top level makefile to clean all dynamically created
# directories.
#
readymedia-transcode-dirclean:
        rm -rf $(BUILD_DIR)/$(READYMEDIA-TRANSCODE_DIR) $(READYMEDIA-TRANSCODE_BUILD_DIR) $(READYMEDIA$
#
#
# Some sanity check for the package.
#
readymedia-transcode-check: $(READYMEDIA-TRANSCODE_IPK)
        perl scripts/optware-check-package.pl --target=$(OPTWARE_TARGET) $^

przy próbie kompilacji make readymedia-transcode-ipk wywala błąd:

/bin/sh: 2: ./configure: not found
make: *** [/home/marcin/optware/ddwrt/builds/readymedia-transcode/.configured] Error 127

Edytowany przez djecstasy dnia 05-03-2015 08:49
 
shibby
nie ma pliku configure w źródłach. Możliwe, że jest configure.in, wtedy musisz najpierw wywołać autoconf
Router: Unifi Cloud Gateway Max
Switch: Netgear MS510TXPP
Switch: Unifi USW-Flex-Mini - szt. 2
Wi-Fi: Unifi U6-Lite - szt. 2
Proxmox VE: i5-13400T, 64GB RAM, 2x 512GB NVMe, 3x 2TB SSD, Intel X710-DA2 SFP+
VM #1: Synology SA6400
VM #2: Debian, WWW
VM #3: Home Assistant OS
 
djecstasy
No niestety to chyba nie jest dla mnie :/ próbowałem dla testów skompilować zwykłe minidlna i też jakieś błędy... Możektoś by mógł skompilować readymedia-transcode pod tomato?
 
Przejdź do forum
Zaloguj
Wprowadź adres e-mail lub nazwę użytkownika

Hasło



Nie masz jeszcze konta? Zarejestruj się.

Zapomniałeś/aś hasła?
Aktualnie online
· Gości online: 109

· Użytkowników online: 0

· Łącznie użytkowników: 24,115
· Najnowszy użytkownik: Ja
Czat
Musisz się zalogować, aby opublikować wiadomość.

Maniek91PL
06-11-2024 22:37
dzięki !Grin

maxikaaz
29-10-2024 14:27
@Maniek91PL - Administration=> Admin Access, i tam masz "Allow Wireless Access" do zaznaczenia

Maniek91PL
26-10-2024 22:07
siemka! ktoś przypomni co się ustawiało jeśli nie mogę wejść od strony wifi do tomato? od lan działa

overflow2
04-10-2024 17:34
Kupowałem Asusy n10u albo n12d1 ale nie widzę ich, chyba już nie produkują, Chodzi o coś nowego i taniego. Transfery niewielkie.

maxikaaz
04-10-2024 09:38
@overflow2 patrząc po dostępności funkcji w nowych kompilacjach, to chyba nawet WRT54G/GL jeszcze ma OpenVPN, albo jakiś odpowiednik... zależy, na jakie transfery liczysz.

overflow2
30-09-2024 20:53
Jaki aktualnie najtańszy router do tomato do openvpn?

maxikaaz
27-07-2024 15:07
@servee - na początek router do rozebrania i obejrzenia, ciężko wróżyć tak tylko po objawach

maxikaaz
27-07-2024 14:55
@servee - cały kontroler nie pada tak sobie z powodu "zbiegu okoliczności",
więc prawdopodobnie gdzieś przepięcie.

servee
25-07-2024 13:33
@maxikaaz: działało, aż pewnego pięknego dnia przestało działać. W tym dniu była też burza, ale to raczej zbieg okoliczności.

maxikaaz
25-07-2024 11:38
@servee - o ile problem jest w obrębie samych wyjść (dławiki, warystory), to naprawialne, ale jeśli w samym SoC - to nienaprawialne ze względu na koszta. A co było przyczyną?

95,679,843 unikalnych wizyt