closed tools, Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
jarmo.ti...@nokia.com wrote: > BTW I think flasher is the only closed source tool we have in maemo > development environment. Or at least I do not know any other binary only tool > :). > I think gcc/uclibc toolchain for initfs development would qualify but it is much worse here, we even don't have the tool (despite GPL) :-( https://bugs.maemo.org/show_bug.cgi?id=3373 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
On Thu, Jul 2, 2009 at 1:36 AM, Ryan Abel wrote: > On Wed, Jul 1, 2009 at 3:44 PM, Kees > Jongenburger wrote: >>> There's absolutely no reason why not. Really, though, why don't we just open >>> source it so we don't have to deal with ANY of this insanity? >> >> There are other project the 0x flasher out there and not enough people >> tried and used it so what is the point? >> > > Define "enough", please. I've certainly seen plenty of people getting > good use out of it, so it certainly seems like "enough" to me. If > you're expecting a mass migration from a functional, tested > manufacturer-provided to an 3rd-party solution of unknown quality > which provides little in the way of additional features, well, of > course it's not going to be "enough". What are you missing and why didn't *you* add it? that is the question that you need to answer for yourself before making such statements. > > Really, the right question to be asking is "Why not?". The > justifications should be for keeping things closed, not making them > open. This is not the way we haven been working in the last year or so. We can create fair request to open component and Nokia can take them into account. I was able to use 0x to render my device usable after flashing a self modified image so I am very happy the alternative exists. Being able to create fiasco images (using specs) can also be nice for Mer. Greetings ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Hi, Some comments about opnesourcing flasher code below. BTW I think flasher is the only closed source tool we have in maemo development environment. Or at least I do not know any other binary only tool :). >-Original Message- >From: ext Hubert Figuiere [mailto:h...@figuiere.net] >Sent: 01 July, 2009 20:06 >Subject: Re: Maemo Flasher-3.5 Tool Beta for Fremantle and >Diablo released > >On 06/30/2009 08:41 AM, jarmo.ti...@nokia.com wrote: >> The Maemo Eclipse Integration 2nd Edition project has >released installation packages for Maemo Flasher-3.5 Tool Beta >for Linuxes, Mac OS X and Windows. Maemo Flasher-3.5 tool >supports flashing of N8x0 Diablo devices and coming Fremantle devices. >> > >Any plan to release the source code of the Flasher? Sorry no plans for that. I think the main reason being that we use some 3rd party interfaces that cannot be published and because of that propably also some source code. This is also business related issue as being able to freely update maintenance releases is of course the standard way of working but in commercial world being able to flash freely also new platform release to old hw (as we have provided in many cases) is not the standard way how or competitors work mainly befouse it is a lot of work to support old hw. Cheers, //Jarmo > > >Hub > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
On Wed, Jul 1, 2009 at 3:44 PM, Kees Jongenburger wrote: >> There's absolutely no reason why not. Really, though, why don't we just open >> source it so we don't have to deal with ANY of this insanity? > > There are other project the 0x flasher out there and not enough people > tried and used it so what is the point? > Define "enough", please. I've certainly seen plenty of people getting good use out of it, so it certainly seems like "enough" to me. If you're expecting a mass migration from a functional, tested manufacturer-provided to an 3rd-party solution of unknown quality which provides little in the way of additional features, well, of course it's not going to be "enough". Really, the right question to be asking is "Why not?". The justifications should be for keeping things closed, not making them open. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Hi Ryan On Wed, Jul 1, 2009 at 4:06 PM, Ryan Abel wrote: > (Sorry for the terrible quoting. You all knoe exactly how useless an > application Modest is. :)) Still not acceptable > > There's absolutely no reason why not. Really, though, why don't we just open > source it so we don't have to deal with ANY of this insanity? There are other project the 0x flasher out there and not enough people tried and used it so what is the point? Greetings ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Beagleboard touchscreens?
On Wed, 2009-07-01 at 10:29 +0200, carlos.guerre...@nokia.com wrote: > This will most definitely work with the BeagleBoard: > http://elinux.org/Xenarc_USB_touchscreen_for_Beagleboard/OMAP3_EVM > > We've got one of those in the office working with a BeagleBoard. > It has DVI input (you'll need a HDMI-to-DVI converter) and a > separate USB connection for the touchscreen. > It's not cheap though. > A minor annoyance - particularly if you are in a hurry - is > that Xenarc will not take foreign (as in non-US) > credit cards so you need to wire them the money before they ship. > Nevertheless I found their customer service responsive and > professional (in dealing with the order). They shipped it > quickly and it came in good shape. Thanks. I think we'll get one. 400 USD plus shipping doesn't seem too awful. -- murr...@murrayc.com www.murrayc.com www.openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Beagleboard touchscreens?
Hi, oh very nice, but even more pricey than my solution. And of course less "hackish" :-) Till Am Mittwoch 01 Juli 2009 schrieb carlos.guerre...@nokia.com: > >From: maemo-developers-boun...@maemo.org > >[mailto:maemo-developers-boun...@maemo.org] On Behalf Of ext > >Murray Cumming > >Sent: 30 June, 2009 20:48 > >To: maemo-developers@maemo.org > >Subject: Beagleboard touchscreens? > > > >I'm going to buy some BeagleBoards for the Openismus office. > >http://beagleboard.org/ > >I'd like to try installing Maemo 5 on them, which I believe is > >possible, and which will be a learning experience. > > > >I hear that Mer can be used with a mouse instead of just a > >touchscreen, but I'd like to install Maemo as intended, so I > >think we'll need touchscreen displays. So does anyone know of > >any touchscreen hardware that will definitely work with > >beagleboard and Maemo? > > Hi Murray, > > This will most definitely work with the BeagleBoard: > http://elinux.org/Xenarc_USB_touchscreen_for_Beagleboard/OMAP3_EVM > > We've got one of those in the office working with a BeagleBoard. > It has DVI input (you'll need a HDMI-to-DVI converter) and a > separate USB connection for the touchscreen. > It's not cheap though. > A minor annoyance - particularly if you are in a hurry - is > that Xenarc will not take foreign (as in non-US) > credit cards so you need to wire them the money before they ship. > Nevertheless I found their customer service responsive and > professional (in dealing with the order). They shipped it > quickly and it came in good shape. > > Br, > Carlos > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
*If* Nokia have no intention of open-sourcing this version of the flasher (because it can flash the new "tablet" and Nokia may not like the idea of releasing code relating to the internals of the new "tablet"), then I'd sincerely hope that they would at release the code to 3.0 as Nokia (yes, I mean Nokia: I'm not referring to Mer here) have no intention of providing updates for the devices flasher-3.0 supports (not bitter about it in any way - I'm just telling it as a statement of fact), it would be nice to have the source code to that version. Of course: Only if this version or the latest final version - whatever that may be - can't be open-sourced for whatever reason. Best Regards, Faheem On 7/1/09, Hubert Figuiere wrote: > On 06/30/2009 08:41 AM, jarmo.ti...@nokia.com wrote: >> The Maemo Eclipse Integration 2nd Edition project has released >> installation packages for Maemo Flasher-3.5 Tool Beta for Linuxes, Mac OS >> X and Windows. Maemo Flasher-3.5 tool supports flashing of N8x0 Diablo >> devices and coming Fremantle devices. >> > > Any plan to release the source code of the Flasher? > > > Hub > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Am Mittwoch, den 01.07.2009, 13:06 -0400 schrieb Hubert Figuiere: > Any plan to release the source code of the Flasher? Also see a thread from November/December 2008: http://lists.maemo.org/pipermail/maemo-community/2008-November/001367.html http://lists.maemo.org/pipermail/maemo-community/2008-December/001396.html andre -- Andre Klapper (maemo.org bugmaster) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
On 06/30/2009 08:41 AM, jarmo.ti...@nokia.com wrote: > The Maemo Eclipse Integration 2nd Edition project has released installation > packages for Maemo Flasher-3.5 Tool Beta for Linuxes, Mac OS X and Windows. > Maemo Flasher-3.5 tool supports flashing of N8x0 Diablo devices and coming > Fremantle devices. > Any plan to release the source code of the Flasher? Hub ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: HildonWindow dimensions not updated on unfullscreen in Fremantle SDK beta
On Wed, Jul 01, 2009 at 05:57:20PM +0200, Luca Donaggio wrote: > But detecting when an event of type GDK_CONFIGURE has occurred > shouldn't be more correct? Ah, yes, if you only want to detect changes in the size of the window I think that should be enough :) Berto ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: HildonWindow dimensions not updated on unfullscreen in Fremantle SDK beta
You're right on the expose event, of course. But detecting when an event of type GDK_CONFIGURE has occurred shouldn't be more correct? From GDK literature [1], an event of type GDK_CONFIGURE is "Generated when a window size or position has changed". That should cover all the bases (ie screen orientation and window fullscreen / unfullscreen changes), I think I'll try it and let you know if it works. Thanks, Luca Donaggio [1] http://maemo.org/api_refs/5.0/beta/gdk/gdk-Event-Structures.html#GdkEventConfigure On Wed, Jul 1, 2009 at 5:01 PM, Alberto Garcia wrote: > On Wed, Jul 01, 2009 at 03:40:08PM +0200, Luca Donaggio wrote: > > > I'm attaching a callback function to the expose event of my app > > HildonWindow to detect size changes occurring after a screen > > orientation change or a fullscreen / unfullscreen button press. > > 'expose' is generated when a part of the window becomes visible. > > For this case I think that you should use GdkScreen:size-changed > to detect orientation changes and GtkWidget:window-state-event for > fullscreen changes (see the documentation of gtk_window_fullscreen()). > > is_fs = (event->new_window_state & GDK_WINDOW_STATE_FULLSCREEN); > > Berto > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: HildonWindow dimensions not updated on unfullscreen in Fremantle SDK beta
On Wed, Jul 01, 2009 at 03:40:08PM +0200, Luca Donaggio wrote: > I'm attaching a callback function to the expose event of my app > HildonWindow to detect size changes occurring after a screen > orientation change or a fullscreen / unfullscreen button press. 'expose' is generated when a part of the window becomes visible. For this case I think that you should use GdkScreen:size-changed to detect orientation changes and GtkWidget:window-state-event for fullscreen changes (see the documentation of gtk_window_fullscreen()). is_fs = (event->new_window_state & GDK_WINDOW_STATE_FULLSCREEN); Berto ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: HildonWindow dimensions not updated on unfullscreen in Fremantle SDK beta
Thank you Daniel, no problem, I'll wait! Luca Donaggio On Wed, Jul 1, 2009 at 3:59 PM, daniel wilms wrote: > Hi, > > there was a similar problem with the callback function lately, and I try to > figure out what's wrong there. Please a bit more patience :) Hopefully > tomorrow I can come up with some information. > > cheers Daniel > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Hi, [jot] some answers below... From: ext gary liquid [mailto:liq...@gmail.com] Sent: 01 July, 2009 15:58 To: Ryan Abel Cc: Tikka Jarmo (Nokia-D/Helsinki); maemo-us...@maemo.org; maemo-developers@maemo.org Subject: Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released is it possible to do tablet->tablet flashing? (serious question) [jot] I think it is not possible because Tablet USB port drivers do not support it but I am not sure. What is possible is to use /usr/sbin/fiasco_flasher available from Tablet to flash images from mmc card. most of us now have more than one device and since not all of us have linux or windows available (hiya GA), having a native solution would be a possible quicker workaround [jot] The easies way to do flashing we be from PC but maybe it would be enough for you to flash from inside Tablet. BTW no quarantine this will work as I have not tested this myself. Cheers, //Jarmo gary ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Hi, I found something to comment from this last email :). >access to on a regular basis. Yes, you can tell the installer >that it should check the architecture. No, you shouldn't be If same installer can be used to install both x86 and PCC binaries depending on which PC you run installation package that would be great. Anyhow I think we can make at least separate PCC installation package when we will have PCC Mac to make it. >that it should check the architecture. No, you shouldn't be >doing that because you should be compiling a PPC binary. Nobody has told me if PCC binary can be build on x86 Mac. If not it will take some time to make PCC version of flasher-3.5 even when it is just rebuilding (at least in theory it should be just rebuilding task). Cheers, //Jarmo >-Original Message- >From: ext Ryan Abel [mailto:rabe...@gmail.com] >Sent: 01 July, 2009 15:37 >To: Tikka Jarmo (Nokia-D/Helsinki) >Cc: maemo-developers@maemo.org; maemo-us...@maemo.org >Subject: Re: Maemo Flasher-3.5 Tool Beta for Fremantle and >Diablo released > >On Wed, Jul 1, 2009 at 2:43 AM, wrote: > >>>One step forward and two steps back. >> >> Happy to see that you considered this Beta release to be at >least one >> step forward (before ending up being one step backward :) >> > >It's hardly every anything else with Nokia. :( > >>> >>>No PPC binary, and the installer will happily chug right >along without >>>telling users that they're installing something they can't even use. >> >> Only x86 and 32-bit support with this beta release. Could >you explain in more detailed your installation problems. E.g. >do you try to install Windows XP or Windows Vista or Mac OS X >10.x or Debian Linux or some other Linux or ... >> > >I don't use Windows, and, by and large, I don't use Linux. > >> Or are you trying to install Mac flasher-3.5 to PPC Mac? I >do not Mac myself well enoug to say if architecture can be >defined to the Mac installation package so that you will get >some sensible error message if you try to install "wrong" >architecture binary. >> > >Yes, because PPC OS X is basically the only thing I have >access to on a regular basis. Yes, you can tell the installer >that it should check the architecture. No, you shouldn't be >doing that because you should be compiling a PPC binary. > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
(Sorry for the terrible quoting. You all knoe exactly how useless an application Modest is. :)) There's absolutely no reason why not. Really, though, why don't we just open source it so we don't have to deal with ANY of this insanity? - Original message - is it possible to do tablet->tablet flashing? (serious question) most of us now have more than one device and since not all of us have linux or windows available (hiya GA), having a native solution would be a possible quicker workaround___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: HildonWindow dimensions not updated on unfullscreen in Fremantle SDK beta
Hi, there was a similar problem with the callback function lately, and I try to figure out what's wrong there. Please a bit more patience :) Hopefully tomorrow I can come up with some information. cheers Daniel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
HildonWindow dimensions not updated on unfullscreen in Fremantle SDK beta
Any hint?
-- Forwarded message --
From: Luca Donaggio
Date: Tue, Jun 30, 2009 at 5:13 PM
Subject: HildonWindow dimensions not updated on unfullscreen in Fremantle
SDK beta
To: Maemo developers mailing-list
Hi all,
I'm attaching a callback function to the expose event of my app HildonWindow
to detect size changes occurring after a screen orientation change or a
fullscreen / unfullscreen button press.
Everything works quite well, except after coming back from fullscreen: in
this case it seems that no expose events is triggered (my callback function
is never called). Is it right?
What is the correct way to do this? I need to detect window's size changes
to rescale the image displayed inside of it.
Here's my code:
g_signal_connect(G_OBJECT (myapp->mainwin),"expose_event",
G_CALLBACK (detect_main_window_changes),myapp);
gboolean detect_main_window_changes (GtkWidget *widget,GdkEvent
*event,app_data_t *myapp) {
switch (event->type) {
case GDK_EXPOSE :
scale_image(GTK_WIDGET (myapp->mainwin),myapp);
return TRUE;
}
return FALSE;
}
Thanks,
Luca Donaggio
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
is it possible to do tablet->tablet flashing? (serious question) most of us now have more than one device and since not all of us have linux or windows available (hiya GA), having a native solution would be a possible quicker workaround gary On Wed, Jul 1, 2009 at 1:36 PM, Ryan Abel wrote: > On Wed, Jul 1, 2009 at 2:43 AM, wrote: > > >>One step forward and two steps back. > > > > Happy to see that you considered this Beta release to be at least one > step forward (before ending up being one step backward :) > > > > It's hardly every anything else with Nokia. :( > > >> > >>No PPC binary, and the installer will happily chug right along > >>without telling users that they're installing something they > >>can't even use. > > > > Only x86 and 32-bit support with this beta release. Could you explain in > more detailed your installation problems. E.g. do you try to install Windows > XP or Windows Vista or Mac OS X 10.x or Debian Linux or some other Linux or > ... > > > > I don't use Windows, and, by and large, I don't use Linux. > > > Or are you trying to install Mac flasher-3.5 to PPC Mac? I do not Mac > myself well enoug to say if architecture can be defined to the Mac > installation package so that you will get some sensible error message if you > try to install "wrong" architecture binary. > > > > Yes, because PPC OS X is basically the only thing I have access to on > a regular basis. Yes, you can tell the installer that it should check > the architecture. No, you shouldn't be doing that because you should > be compiling a PPC binary. > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
On Wed, Jul 1, 2009 at 2:43 AM, wrote: >>One step forward and two steps back. > > Happy to see that you considered this Beta release to be at least one step > forward (before ending up being one step backward :) > It's hardly every anything else with Nokia. :( >> >>No PPC binary, and the installer will happily chug right along >>without telling users that they're installing something they >>can't even use. > > Only x86 and 32-bit support with this beta release. Could you explain in more > detailed your installation problems. E.g. do you try to install Windows XP or > Windows Vista or Mac OS X 10.x or Debian Linux or some other Linux or ... > I don't use Windows, and, by and large, I don't use Linux. > Or are you trying to install Mac flasher-3.5 to PPC Mac? I do not Mac myself > well enoug to say if architecture can be defined to the Mac installation > package so that you will get some sensible error message if you try to > install "wrong" architecture binary. > Yes, because PPC OS X is basically the only thing I have access to on a regular basis. Yes, you can tell the installer that it should check the architecture. No, you shouldn't be doing that because you should be compiling a PPC binary. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Beagleboard touchscreens?
>From: maemo-developers-boun...@maemo.org >[mailto:maemo-developers-boun...@maemo.org] On Behalf Of ext >Murray Cumming >Sent: 30 June, 2009 20:48 >To: maemo-developers@maemo.org >Subject: Beagleboard touchscreens? > >I'm going to buy some BeagleBoards for the Openismus office. >http://beagleboard.org/ >I'd like to try installing Maemo 5 on them, which I believe is >possible, and which will be a learning experience. > >I hear that Mer can be used with a mouse instead of just a >touchscreen, but I'd like to install Maemo as intended, so I >think we'll need touchscreen displays. So does anyone know of >any touchscreen hardware that will definitely work with >beagleboard and Maemo? Hi Murray, This will most definitely work with the BeagleBoard: http://elinux.org/Xenarc_USB_touchscreen_for_Beagleboard/OMAP3_EVM We've got one of those in the office working with a BeagleBoard. It has DVI input (you'll need a HDMI-to-DVI converter) and a separate USB connection for the touchscreen. It's not cheap though. A minor annoyance - particularly if you are in a hurry - is that Xenarc will not take foreign (as in non-US) credit cards so you need to wire them the money before they ship. Nevertheless I found their customer service responsive and professional (in dealing with the order). They shipped it quickly and it came in good shape. Br, Carlos ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
rtorrent make fails
Hi, i am trying to build rtorrent (http://libtorrent.rakshasa.no/) in my Maemo 3.1 sdk environment but the make keeps failing: /bin/sh ../libtool --tag=CXX --mode=link g++ -g -O2 -g -DDEBUG -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/scratchbox/devkits/maemo3-tools/include -o rtorrent command_download.o command_dynamic.o command_events.o command_file.o command_helpers.o command_local.o command_network.o command_object.o command_peer.o command_tracker.o command_scheduler.o command_ui.o control.o globals.o main.o option_parser.o signal_handler.o ui/libsub_ui.a core/libsub_core.a display/libsub_display.a input/libsub_input.a rpc/libsub_rpc.a utils/libsub_utils.a -lncurses -lsigc-2.0 -Wl,-rpath -Wl,/scratchbox/host_shared/lib/ -Wl,/scratchbox/tools/lib/ -Wl,/scratchbox/devkits/maemo3-tools/lib/ -L/scratchbox/devkits/maemo3-tools/lib -lcurl -ltorrent libtool: link: warning: library `/usr/lib/libtorrent.la' was moved. libtool: link: warning: library `/usr/lib/libtorrent.la' was moved. libtool: link: g++ -g -O2 -g -DDEBUG -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/scratchbox/devkits/maemo3-tools/include -o rtorrent command_download.o command_dynamic.o command_events.o command_file.o command_helpers.o command_local.o command_network.o command_object.o command_peer.o command_tracker.o command_scheduler.o command_ui.o control.o globals.o main.o option_parser.o signal_handler.o -Wl,-rpath -Wl,/scratchbox/host_shared/lib/ -Wl,/scratchbox/tools/lib/ -Wl,/scratchbox/devkits/maemo3-tools/lib/ ui/libsub_ui.a core/libsub_core.a display/libsub_display.a input/libsub_input.a rpc/libsub_rpc.a utils/libsub_utils.a -lncurses -L/scratchbox/devkits/maemo3-tools/lib /scratchbox/devkits/maemo3-tools/lib/libcurl.so -lidn -lssl -ldl -lz /usr/lib/libtorrent.so -lcrypto /usr/lib/libsigc-2.0.so -Wl,-rpath -Wl,/scratchbox/devkits/maemo3-tools/lib -Wl,-rpath -Wl,/scratchbox/devkits/maemo3-tools/lib /scratchbox/tools/lib/: file not recognized: Is a directory collect2: ld returned 1 exit status ... full output of ./configure: http://pastebin.com/m206173bd full output of make: http://pastebin.com/m5bb848c3 What kind of modifications should i make to rtorrent or to my environment to get it build? -- Jonni Nakari jo...@egarden.fi +358 50 4411 784 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
