Menu
▾
▴
sumo-devel — Archive only, please subscribe to sumo-dev@eclipse.org
This list is closed, nobody may subscribe to it.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
|
Mar
(1) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(38) |
Dec
(1) |
| 2007 |
Jan
(5) |
Feb
(6) |
Mar
(1) |
Apr
(1) |
May
|
Jun
(1) |
Jul
(1) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2008 |
Jan
|
Feb
(1) |
Mar
(5) |
Apr
(15) |
May
(13) |
Jun
(3) |
Jul
(8) |
Aug
(6) |
Sep
(8) |
Oct
(14) |
Nov
(6) |
Dec
(1) |
| 2009 |
Jan
(1) |
Feb
(7) |
Mar
(12) |
Apr
(19) |
May
(8) |
Jun
(6) |
Jul
(2) |
Aug
|
Sep
(24) |
Oct
(17) |
Nov
(1) |
Dec
|
| 2010 |
Jan
(3) |
Feb
(7) |
Mar
(13) |
Apr
(19) |
May
(23) |
Jun
(8) |
Jul
(21) |
Aug
(19) |
Sep
(39) |
Oct
(27) |
Nov
(2) |
Dec
(7) |
| 2011 |
Jan
(6) |
Feb
(38) |
Mar
(19) |
Apr
(8) |
May
(23) |
Jun
(21) |
Jul
(42) |
Aug
(32) |
Sep
(31) |
Oct
(7) |
Nov
(12) |
Dec
(11) |
| 2012 |
Jan
(2) |
Feb
(10) |
Mar
(9) |
Apr
(25) |
May
(16) |
Jun
(25) |
Jul
(5) |
Aug
(11) |
Sep
(12) |
Oct
|
Nov
(9) |
Dec
(1) |
| 2013 |
Jan
|
Feb
(7) |
Mar
(5) |
Apr
(13) |
May
(13) |
Jun
(4) |
Jul
(5) |
Aug
(1) |
Sep
(7) |
Oct
(6) |
Nov
(4) |
Dec
(10) |
| 2014 |
Jan
(19) |
Feb
(16) |
Mar
(20) |
Apr
(7) |
May
(5) |
Jun
(11) |
Jul
(5) |
Aug
(3) |
Sep
(10) |
Oct
(7) |
Nov
|
Dec
(5) |
| 2015 |
Jan
(8) |
Feb
(1) |
Mar
(3) |
Apr
(9) |
May
(4) |
Jun
(11) |
Jul
|
Aug
(9) |
Sep
(2) |
Oct
(6) |
Nov
(1) |
Dec
(5) |
| 2016 |
Jan
(4) |
Feb
(10) |
Mar
(9) |
Apr
(22) |
May
(20) |
Jun
(41) |
Jul
(25) |
Aug
(5) |
Sep
(9) |
Oct
(1) |
Nov
(17) |
Dec
(8) |
| 2017 |
Jan
(6) |
Feb
(12) |
Mar
(8) |
Apr
(8) |
May
(3) |
Jun
(30) |
Jul
(32) |
Aug
(14) |
Sep
(8) |
Oct
(2) |
Nov
(6) |
Dec
(5) |
| 2018 |
Jan
(4) |
Feb
(3) |
Mar
(16) |
Apr
(6) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(2) |
Oct
(5) |
Nov
|
Dec
|
|
From: <beh...@in...> - 2008-11-16 01:53:52
|
make with all options failed ./utils/gui/drawer/GUIColorer_ByOptCORNValue.h: At global scope: ./utils/gui/drawer/GUIColorer_ByOptCORNValue.h: In instantiation of 'GUIColorer_ByOptCORNValue<myT, myD>::GUIColorer_ByOptCORNValue(bool (myT::*)(myD)const, int (myT::*)(myD)const, bool, double, double, const RGBColor&, const RGBColor&, const RGBColor&, myD) [with myT = GUIVehicle, myD = MSCORN::Function]': guisim_main.cpp:135: instantiated from here ./utils/gui/drawer/GUIColorer_ByOptCORNValue.h:63: warning: unused parameter 'catchNo' ./utils/gui/drawer/GUIColorer_ShadeByFunctionValue.h: In member function 'void GUIColorer_ShadeByFunctionValue<T, D>::setGlColor(const T&) const [with T = GUILaneWrapper, D = double]': guisim_main.cpp:478: instantiated from here ./utils/gui/drawer/GUIColorer_ShadeByFunctionValue.h:76: warning: comparing floating point with == or != is unsafe ./utils/gui/drawer/GUIColorer_ShadeByFunctionValue.h: In member function 'void GUIColorer_ShadeByFunctionValue<T, D>::setGlColor(const T&) const [with T = GUIVehicle, D = unsigned int]': guisim_main.cpp:478: instantiated from here ./utils/gui/drawer/GUIColorer_ShadeByFunctionValue.h:76: warning: comparing floating point with == or != is unsafe ./utils/gui/drawer/GUIColorer_ShadeByFunctionValue.h: In member function 'void GUIColorer_ShadeByFunctionValue<T, D>::setGlColor(const T&) const [with T = GUIVehicle, D = double]': guisim_main.cpp:478: instantiated from here ./utils/gui/drawer/GUIColorer_ShadeByFunctionValue.h:76: warning: comparing floating point with == or != is unsafe make[3]: *** [guisim_main.o] Error 1 make[3]: Leaving directory `/home1/behrisch/DLR/sumo/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src' make: *** [all-recursive] Error 1 |
|
From: Daniel K. <d.k...@we...> - 2008-11-15 12:54:33
|
Dear all, I added some further (optional) attributes to the vehicle type definition. These are - with default values given: - "emissionClass" which will be used to distinguished between different vehicle classes for emissions computation (SVE_PASSENGER) - "guiWidth" which will be used to determine the width of the vehicle when being painted (2m) - "guiOffset" to determine how much of the vehicle length shall be treaten as jam distance between vehicles (2.5m) - "guiShape" to determine how the vehicle shall be rendered (SVS_PASSENGER) The functionality behind these attributes is not yet implemented, nonetheless I want to inform you (especially you, Michael), because "guiOffset" it slightly differs to what we decided recently, and because I know that having an "emissionClass" definition within the vehicle type is interesting for others. Michael, I decided to use "guiOffset", because having a "guiLength" would require to define it each time for vehicles of different lengths. For "guiOffset", its standard value may be kept for all vehicle types - unless we have further information. The complete vehicle types are now stored on loading/saving the network state. sincerely, Daniel _____________________________________________________________________ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=000000000066 |
|
From: <beh...@in...> - 2008-11-04 01:03:37
|
svn up failed svn: PROPFIND request failed on '/svnroot/sumo/trunk/sumo' svn: PROPFIND of '/svnroot/sumo/trunk/sumo': Could not resolve hostname `sumo.svn.sourceforge.net': Host not found (https://sumo.svn.sourceforge.net) |
|
From: <beh...@in...> - 2008-10-31 01:47:24
|
make with all options failed
In file included from ../../../../src/foreign/rtree/SUMORTree.h:43,
from ../../../../src/utils/gui/windows/GUISUMOAbstractView.h:44,
from ../../../../src/utils/gui/windows/GUIGlChildWindow.h:38,
from ../../../../src/gui/GUISUMOViewParent.h:40,
from ../../../../src/gui/GUIApplicationWindow.h:45,
from GUIDialog_GLChosenEditor.cpp:35:
../../../../src/foreign/rtree/RTree.h: At global scope:
../../../../src/foreign/rtree/RTree.h:70: error: comma at end of enumerator list
../../../../src/foreign/rtree/RTree.h:591: error: extra ';'
make[5]: *** [GUIDialog_GLChosenEditor.o] Error 1
make[5]: Leaving directory `/home1/behrisch/DLR/sumo/src/utils/gui/div'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home1/behrisch/DLR/sumo/src/utils/gui'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home1/behrisch/DLR/sumo/src/utils'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make: *** [all-recursive] Error 1
|
|
From: <beh...@in...> - 2008-10-30 01:40:50
|
make with all options failed
from MSE2Collector.h:34,
from MSE2Collector.cpp:31:
../../../src/microsim/MSVehicleType.h: In member function 'double MSVehicleType::_vsafe(double, double) const':
../../../src/microsim/MSVehicleType.h:236: warning: comparing floating point with == or != is unsafe
MSE2Collector.cpp: In constructor 'MSE2Collector::MSE2Collector(const std::string&, DetectorUsage, MSLane*, double, double, SUMOTime, double, double)':
MSE2Collector.cpp:58: error: 'laneM' was not declared in this scope
MSE2Collector.cpp: In member function 'virtual void MSE2Collector::writeXMLOutput(OutputDevice&, SUMOTime, SUMOTime)':
MSE2Collector.cpp:337: warning: comparing floating point with == or != is unsafe
MSE2Collector.cpp:338: warning: comparing floating point with == or != is unsafe
make[5]: *** [MSE2Collector.o] Error 1
make[5]: Leaving directory `/home1/behrisch/DLR/sumo/src/microsim/output'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home1/behrisch/DLR/sumo/src/microsim/output'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home1/behrisch/DLR/sumo/src/microsim'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make: *** [all-recursive] Error 1
|
|
From: <beh...@in...> - 2008-10-29 01:42:05
|
make with all options failed
In file included from ../../../src/microsim/MSVehicle.h:46,
from ../../../src/microsim/MSLane.h:34,
from MSMeanData_Net.cpp:34:
../../../src/microsim/MSVehicleType.h: In member function 'double MSVehicleType::_vsafe(double, double) const':
../../../src/microsim/MSVehicleType.h:236: warning: comparing floating point with == or != is unsafe
MSMeanData_Net.cpp: At global scope:
MSMeanData_Net.cpp:104: warning: unused parameter 'stopTime'
MSMeanData_Net.cpp: In member function 'virtual void MSMeanData_Net::writeEdge(OutputDevice&, const std::vector<MSLaneMeanDataValues*, std::allocator<MSLaneMeanDataValues*> >&, SUMOTime, SUMOTime)':
MSMeanData_Net.cpp:272: error: 'lanes' was not declared in this scope
make[5]: *** [MSMeanData_Net.o] Error 1
make[5]: Leaving directory `/home1/behrisch/DLR/sumo/src/microsim/output'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home1/behrisch/DLR/sumo/src/microsim/output'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home1/behrisch/DLR/sumo/src/microsim'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make: *** [all-recursive] Error 1
|
|
From: Daniel K. <d.k...@we...> - 2008-10-28 15:49:46
|
Dear Mauro, > -----Ursprüngliche Nachricht----- > Von: "Mauro Bianchi" <bia...@gm...> > Gesendet: 28.10.08 14:57:28 > An: "Daniel Krajzewicz" <d.k...@we...> > CC: sum...@li... > Betreff: Re: [sumo-devel] Pollutant emission module > Dear Daniel, > > I appreciate a lot your reply, even if it comes after a while. > Moreover, I am effectively beginning to work on the emission model > just in these days, so you are still in time :) > Great. > First, a quick resume of my project : > Until now, besides getting familiar with SUMO simulations, i focused > on developing a set of tools for quickly developing traffic demand on > a given network, with a stochastic approach, suitable for my project. > I ended up with some python scripts that generate trips definitions > from an xml description of traffic fluxes. The xml description is > quite flexible and it covers vehicle types distributions, that are > needed to compute emissions. If you are interested in the topic, I can > give more details, as well as sharing my scripts/ideas. > Yes, this would be definitely of interest. As no free traffic demand data exists - at least, I have not found anything - people mostly try to use the "random-routes" - option. But this of course leads to a completely useless traffic, in fact. I thought of starting a wiki-manual called "Why random routes are evil", but unfortunately have not yet found the time to start. So, yes, we would be definitely very interested in what you have done. If you would find the time to get a sourceforge account, I would give you the rights to write into Wiki... > About traffic emissions, because of the limited time i have for my > project, I am actually working on a SUMO netstate-dump postprocessor, > instead of implementing an "online" sumo model. > This kind of processing should be enough for implementing an > aggregated model, like EMEP/CORINAIR methodology, which I was thinking > to implement on an edge level spatial aggregation. > The main issue is that time aggregations leading to mean speeds << 10 > Km/h should be avoided, in order to have some significant emission > estimates. > > you can find here the methodology specifications > http://reports.eea.europa.eu/EMEPCORINAIR5/en/page016.html > > > > As I wrote you a while ago, we also have the task to extend SUMO by a model of >vehicular emissions. I started to work on this recently, at first by designing/implementing >the iterfaces to the simulation. What I have done basically is to change the way the mean >data output values are collected. Now, the classes used for mean data generation should >be the proper base for those that calculate emissions. I will support you further details, if >wished. > > > I would be very interested in details of your implementation, if possible. > Ok, I'll keep you informed about what I do. I suppose that the whole work on interfaces will take me till the end of Novembre or so. The model itself will be implemented in parallel and afterwards incorporated. > > > Have you already decided which model to use? Our calculation will be based on HBEFA > >(www.hbefa.com). Still, it will not be HBEFA itself, but rather a subset of it, reworked to > >deal with continuous values instead of the discrete they use. > > For now my choice is to use the EMEP/CORINAIR methodology, which is > suitable for aggregate estimates. > With your implementation, which level of spatial and time detail are > you going to use? > HBEFA itself is a set of tables as I have understood it by now. We will try to reformulate as a per-vehicle computation function that uses the velocity and the speed. > > > I know that your post is quite old. Still, I hope to stay in touch and share our ideas and > >ways to implement the model. Do you think a Wiki-page is a good way to store the > >information about the implementation? > > > A wiki page would be definitely great. > > If we could keep in touch it would be really useful for me, as I will > be very active on this task during these weeks. > > Ok, I think it would be great if you would get a sourceforge account and post me your sourceforge-name as a first step. sincerely, Daniel > best regards, > Mauro > > > -- > Mauro Bianchi > bia...@gm... > _____________________________________________________________________ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=000000000066 |
|
From: Daniel K. <d.k...@we...> - 2008-10-28 14:28:48
|
Dear Mauro, you are not alone... As I wrote you a while ago, we also have the task to extend SUMO by a model of vehicular emissions. I started to work on this recently, at first by designing/implementing the iterfaces to the simulation. What I have done basically is to change the way the mean data output values are collected. Now, the classes used for mean data generation should be the proper base for those that calculate emissions. I will support you further details, if wished. Have you already decided which model to use? Our calculation will be based on HBEFA (www.hbefa.com). Still, it will not be HBEFA itself, but rather a subset of it, reworked to deal with continuous values instead of the discrete they use. I know that your post is quite old. Still, I hope to stay in touch and share our ideas and ways to implement the model. Do you think a Wiki-page is a good way to store the information about the implementation? sincerely, Daniel > -----Ursprüngliche Nachricht----- > Von: "Mauro Bianchi" <bia...@gm...> > Gesendet: 11.09.08 12:43:18 > An: sum...@li... > Betreff: [sumo-devel] Pollutant emission module > > Dear developers, > I am new to the mailing list (and also to SUMO), and I am beginning > to implement a module for pollutant emissions estimation for SUMO. > I'd like to share with you some ideas about my approach and ask for > your advices. > > First of all, for what i understand, there are two main possibilities: > 1) Integrate the emission calculation directly into SUMO > 2) Keeping the emission calculation in a separate module, and let it > communcate with SUMO at runtime via TCP/IP > For very simple emission models, another option can raise: > 3) Calculating emissions with an external program, processing the > dumpfiles produced by SUMO as output. > > Actually, I'm considering the first option, as it can cover a wider > range of emissions models and would end in a simpler architecture and > interface for the final user. > > Another question is related to what emission model to use. Theorically, > there are a good numbers of emission models, ranging from averaged > to istantaneous models. In practice, i found only two options that > seems to have updated and available emission factors for modern > vehicles: > 1) the COPERT model (http://lat.eng.auth.gr/copert/) > 2) The upcoming ARTEMIS model (http://www.inrets.fr/ur/lte/publi- > autresactions/fichesresultats/ficheartemis/artemis.html) > > The first is an aggregated model, depending only from averaged speeds > of vehicle fleet, and thus suitable only for time resolutions above 1 > day (which is probably yet too short). > The second model seems more promising, as it introduces the concept > of "traffic situations", pushing it closer to istantaneous models. > From model's documentation it seems like it is suitable for link-wise > evaluations, for a time resolution down to 1 hour. > > Before going deeper in the topic, I'd like to know if anyone is > working on a similar project, and if so to share your ideas. In > particular, has anyone identified an instantaneous model to be > plugged into the simulation? > > Thanks for your attention! > Best regards, > Mauro > > -- > Mauro Bianchi > bia...@gm... > > --------------------------------------------------------------------- > ---- This SF.Net email is sponsored by the Moblin Your Move Developer' > s challenge Build the coolest Linux based applications with Moblin > SDK & win great prizes Grand prize is a trip for two to an Open > Source event anywhere in the world http://moblin-contest.org/redirect. > php?banner_id=100&url=/ _____________________________________________ > __ sumo-devel mailing list sum...@li... https:// > > lists.sourceforge.net/lists/listinfo/sumo-devel __________________________________________________________________ "Run, Fatboy, Run" sowie "Rails & Ties" kostenlos anschauen! Blockbuster-Gutscheine sichern unter http://www.blockbuster.web.de |
|
From: Mauro B. <bia...@gm...> - 2008-10-28 13:57:20
|
Dear Daniel, I appreciate a lot your reply, even if it comes after a while. Moreover, I am effectively beginning to work on the emission model just in these days, so you are still in time :) First, a quick resume of my project : Until now, besides getting familiar with SUMO simulations, i focused on developing a set of tools for quickly developing traffic demand on a given network, with a stochastic approach, suitable for my project. I ended up with some python scripts that generate trips definitions from an xml description of traffic fluxes. The xml description is quite flexible and it covers vehicle types distributions, that are needed to compute emissions. If you are interested in the topic, I can give more details, as well as sharing my scripts/ideas. About traffic emissions, because of the limited time i have for my project, I am actually working on a SUMO netstate-dump postprocessor, instead of implementing an "online" sumo model. This kind of processing should be enough for implementing an aggregated model, like EMEP/CORINAIR methodology, which I was thinking to implement on an edge level spatial aggregation. The main issue is that time aggregations leading to mean speeds << 10 Km/h should be avoided, in order to have some significant emission estimates. you can find here the methodology specifications http://reports.eea.europa.eu/EMEPCORINAIR5/en/page016.html > As I wrote you a while ago, we also have the task to extend SUMO by a model of >vehicular emissions. I started to work on this recently, at first by designing/implementing >the iterfaces to the simulation. What I have done basically is to change the way the mean >data output values are collected. Now, the classes used for mean data generation should >be the proper base for those that calculate emissions. I will support you further details, if >wished. I would be very interested in details of your implementation, if possible. > Have you already decided which model to use? Our calculation will be based on HBEFA >(www.hbefa.com). Still, it will not be HBEFA itself, but rather a subset of it, reworked to >deal with continuous values instead of the discrete they use. For now my choice is to use the EMEP/CORINAIR methodology, which is suitable for aggregate estimates. With your implementation, which level of spatial and time detail are you going to use? > I know that your post is quite old. Still, I hope to stay in touch and share our ideas and >ways to implement the model. Do you think a Wiki-page is a good way to store the >information about the implementation? A wiki page would be definitely great. If we could keep in touch it would be really useful for me, as I will be very active on this task during these weeks. best regards, Mauro -- Mauro Bianchi bia...@gm... |
|
From: <beh...@in...> - 2008-10-28 01:57:10
|
make with all options failed ../../../../src/foreign/rtree/RTree.h:541: error: 'a_context' was not declared in this scope ../../../../src/foreign/rtree/RTree.h: At global scope: ../../../../src/foreign/rtree/RTree.h:623: error: extra ';' ../../../../src/foreign/rtree/RTree.h:1572: error: expected ',' or '...' before 'a_resultCallback' ../../../../src/foreign/rtree/RTree.h: In member function 'bool RTree<DATATYPE, DATATYPENP, ELEMTYPE, NUMDIMS, CONTEXT, ELEMTYPEREAL, TMAXNODES, TMINNODES>::Search(RTree<DATATYPE, DATATYPENP, ELEMTYPE, NUMDIMS, CONTEXT, ELEMTYPEREAL, TMAXNODES, TMINNODES>::Node*, RTree<DATATYPE, DATATYPENP, ELEMTYPE, NUMDIMS, CONTEXT, ELEMTYPEREAL, TMAXNODES, TMINNODES>::Rect*, int&, bool)': ../../../../src/foreign/rtree/RTree.h:1584: error: 'a_resultCallback' was not declared in this scope ../../../../src/foreign/rtree/RTree.h:1584: error: 'a_context' was not declared in this scope ../../../../src/foreign/rtree/RTree.h:1600: error: 'a_resultCallback' was not declared in this scope ../../../../src/foreign/rtree/RTree.h:1603: error: 'a_context' was not declared in this scope make[5]: *** [GUIDialog_GLChosenEditor.o] Error 1 make[5]: Leaving directory `/home1/behrisch/DLR/sumo/src/utils/gui/div' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home1/behrisch/DLR/sumo/src/utils/gui' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home1/behrisch/DLR/sumo/src/utils' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src' make: *** [all-recursive] Error 1 |
|
From: <beh...@in...> - 2008-10-22 00:43:52
|
make with all options failed NBContHelper.h:147: warning: comparing floating point with == or != is unsafe NBContHelper.h: In member function 'int NBContHelper::same_connection_edge_sorter::operator()(NBEdge*, NBEdge*) const': NBContHelper.h:304: warning: comparing floating point with == or != is unsafe NBContHelper.h:304: warning: comparing floating point with == or != is unsafe NBContHelper.h: In member function 'std::pair<double, double> NBContHelper::same_connection_edge_sorter::getMinMaxRelAngles(NBEdge*) const': NBContHelper.h:326: warning: comparing floating point with == or != is unsafe NBContHelper.h:329: warning: comparing floating point with == or != is unsafe NBRequest.cpp: In member function 'void NBRequest::writeResponse(std::ostream&, NBEdge*, NBEdge*, int, int)': NBRequest.cpp:562: error: 'struct NBEdge::Connection' has no member named 'edge' NBRequest.cpp:562: error: 'struct NBEdge::Connection' has no member named 'edge' NBRequest.cpp:548: warning: unused variable 'bla' NBRequest.cpp: At global scope: NBRequest.cpp:582: warning: unused parameter 'isInnerEnd' make[3]: *** [NBRequest.o] Error 1 make[3]: Leaving directory `/home1/behrisch/DLR/sumo/src/netbuild' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src' make: *** [all-recursive] Error 1 |
|
From: Michael B. <beh...@us...> - 2008-10-20 08:43:24
|
Dear SUMO-users, no, we don't want your money. ;-) But every now and then we need to explain why SUMO is a useful piece of software not only to the developers but to the whole (traffic) research community and why it should continue as an open source project. This is the point where you come into play. Please send us (to this mailing list if possible) short testimonials of your SUMO experience (positive and negative ones!). Please spread this message also to people that use SUMO but are possibly not on this list. If you already have a project and / or a publication referring to SUMO please add it to the respective list in the Wiki (http://sumo.sf.net/wiki/index.php/Projects, http://sumo.sf.net/wiki/index.php/Publications) or send it to the list with a remark that it can be added. I think, we do not exaggerate in saying that without your support SUMO might not exist any longer in about two years. Thanks for your help, Daniel and Michael |
|
From: Michael B. <beh...@us...> - 2008-10-20 08:03:42
|
Dear SUMO-users, as some of you may have noticed we are moving more and more of our documentation into the wiki. Now that SourceForge is offering mediawiki as a hosted application, we decided to switch to this wiki, which can be reached via http://apps.sourceforge.net/mediawiki/sumo/ The content of the old wiki has been moved already and all links to the old wiki get redirected. In the next months we will try to move our whole website (including all documentation) to the new wiki. Any help is greatly appreciated! In order to participate in the new wiki you will need a SourceForge account. Happy wikiing, Daniel and Michael |
|
From: <beh...@in...> - 2008-10-18 00:54:45
|
lost connection |
|
From: Michael B. <beh...@us...> - 2008-10-16 15:24:27
|
Hello, we have recently added experimental support for linux binary rpms using the openSUSE build service. Please try it out and tell us what you think. Currently there are only openSUSE 10.3 and 11.0 packages available. Just search for sumo using this form: http://software.opensuse.org/search Regards, Michael |
|
From: <beh...@in...> - 2008-10-16 00:42:26
|
make with all options failed
from ../../src/utils/geom/Position2DVector.h:36,
from NBEdge.h:41,
from NBConnection.cpp:35:
../../src/utils/geom/Position2D.h: In function 'bool operator==(const Position2D&, const Position2D&)':
../../src/utils/geom/Position2D.h:139: warning: comparing floating point with == or != is unsafe
../../src/utils/geom/Position2D.h:139: warning: comparing floating point with == or != is unsafe
../../src/utils/geom/Position2D.h: In function 'bool operator!=(const Position2D&, const Position2D&)':
../../src/utils/geom/Position2D.h:143: warning: comparing floating point with == or != is unsafe
../../src/utils/geom/Position2D.h:143: warning: comparing floating point with == or != is unsafe
In file included from NBConnection.cpp:35:
NBEdge.h: At global scope:
NBEdge.h:102: error: comma at end of enumerator list
NBEdge.h:115: error: comma at end of enumerator list
make[3]: *** [NBConnection.o] Error 1
make[3]: Leaving directory `/home1/behrisch/DLR/sumo/src/netbuild'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make: *** [all-recursive] Error 1
|
|
From: <beh...@in...> - 2008-10-14 00:36:48
|
make failed
ar cru librouter.a ROAbstractRouteDefLoader.o ROEdge.o ROFrame.o ROHelper.o ROLoader.o RONet.o RONetHandler.o RONode.o RORDGenerator_ODAmounts.o RORDGenerator_Random.o RORDLoader_SUMOBase.o RORDLoader_TripDefs.o RORoute.o RORouteDef.o RORouteDef_Alternatives.o RORouteDef_Complete.o RORouteDef_OrigDest.o ROTypedXMLRoutesLoader.o ROVehicle.o ROVehicleBuilder.o ROVehicleCont.o ROVehicleType.o ROVehicleType_ID.o ROVehicleType_Krauss.o
ranlib librouter.a
make[3]: Leaving directory `/home1/behrisch/DLR/sumo/src/router'
Making all in routing_df
make[3]: Entering directory `/home1/behrisch/DLR/sumo/src/routing_df'
g++ -DHAVE_CONFIG_H -I. -I../../src -O2 -DNDEBUG -MT RODFDetFlowLoader.o -MD -MP -MF .deps/RODFDetFlowLoader.Tpo -c -o RODFDetFlowLoader.o RODFDetFlowLoader.cpp
In file included from RODFDetFlowLoader.cpp:41:
../../src/utils/importio/LineReader.h:89: error: expected type-specifier before 'ProcessError'
../../src/utils/importio/LineReader.h:89: error: expected `)' before 'ProcessError'
../../src/utils/importio/LineReader.h:89: error: expected ';' before 'ProcessError'
../../src/utils/importio/LineReader.h:99: error: expected type-specifier before 'ProcessError'
../../src/utils/importio/LineReader.h:99: error: expected `)' before 'ProcessError'
../../src/utils/importio/LineReader.h:99: error: expected ';' before 'ProcessError'
make[3]: *** [RODFDetFlowLoader.o] Error 1
make[3]: Leaving directory `/home1/behrisch/DLR/sumo/src/routing_df'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make: *** [all-recursive] Error 1
make install failed
../../src/utils/importio/LineReader.h:89: error: expected `)' before 'ProcessError'
../../src/utils/importio/LineReader.h:89: error: expected ';' before 'ProcessError'
../../src/utils/importio/LineReader.h:99: error: expected type-specifier before 'ProcessError'
../../src/utils/importio/LineReader.h:99: error: expected `)' before 'ProcessError'
../../src/utils/importio/LineReader.h:99: error: expected ';' before 'ProcessError'
make[2]: *** [RODFDetFlowLoader.o] Error 1
make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src/routing_df'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make: *** [install-recursive] Error 1
make with all options failed
g++ -DHAVE_CONFIG_H -I. -I../../src -I/home1/behrisch/DLR/include/fox-1.4 -I/home1/behrisch/DLR/include -I/home1/behrisch/DLR/include -g -Wall -W -Wfloat-equal -pedantic -Wno-long-long -MT RODFDetFlowLoader.o -MD -MP -MF .deps/RODFDetFlowLoader.Tpo -c -o RODFDetFlowLoader.o RODFDetFlowLoader.cpp
In file included from RODFDetFlowLoader.cpp:41:
../../src/utils/importio/LineReader.h:89: error: expected type-specifier before 'ProcessError'
../../src/utils/importio/LineReader.h:89: error: expected `)' before 'ProcessError'
../../src/utils/importio/LineReader.h:89: error: expected ';' before 'ProcessError'
../../src/utils/importio/LineReader.h:99: error: expected type-specifier before 'ProcessError'
../../src/utils/importio/LineReader.h:99: error: expected `)' before 'ProcessError'
../../src/utils/importio/LineReader.h:99: error: expected ';' before 'ProcessError'
In file included from ../../src/routing_df/RODFDetector.h:38,
from RODFDetFlowLoader.h:37,
from RODFDetFlowLoader.cpp:49:
../../src/utils/common/RandomDistributor.h: In member function 'T RandomDistributor<T>::get() const':
../../src/utils/common/RandomDistributor.h:52: warning: comparing floating point with == or != is unsafe
make[3]: *** [RODFDetFlowLoader.o] Error 1
make[3]: Leaving directory `/home1/behrisch/DLR/sumo/src/routing_df'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make: *** [all-recursive] Error 1
|
|
From: Daniel K. <d.k...@we...> - 2008-09-30 10:56:29
|
Dear all, as I am currently working with the DFROUTER again, I have noticed several rather annoying behaviours of this application, which I would propose to change 1. use qKFZ and qLKW In the current implementation, DFROUTER assumes to get qPKW and qKFZ. This is very unlikely to be found in real world detector data, where qKFZ and qLKW are common. So, proposal #1: change input measures from qPKW and qKFZ to qKFZ and qLKW. BTW: Does anyone know how the values (number of and speeds of vehicles/trucks/passenger cars) which have passed a detector is abbreviated in English? 2. Elmar import For some historical reasons, DFROUTER still supports reading detector definitions in Elmar-format. I think this is no longer needed in any of our projects - and external users are surely not using it, too. Proposal #2: Remove Elmar-import support for DFROUTER 3. Time definition DFROUTER assumes the time given for detector entries to be given in minutes. This neither documented well, nor really well. Proposal #3: Detector value time shold be defined in seconds, not in minutes. I am awaiting your opinions till Monday, 6th October. If nothing arrives me, I'll apply the changes. bye, Daniel -- Deutsches Zentrum für Luft- und Raumfahrt e.V. in der Helmholtz-Gemeinschaft Institut für Verkehrssystemtechnik Daniel Krajzewicz, Dipl.-Inf. Rutherfordstr. 2 12489 Berlin Tel.: +49/(0)30/67055-273 Fax : +49/(0)30/67055-291 E-Mail: Dan...@dl... Internet: http://www.dlr.de/ts ____________________________________________________________________ Psssst! Schon vom neuen WEB.DE MultiMessenger gehört? Der kann`s mit allen: http://www.produkte.web.de/messenger/?did=3123 |
|
From: <beh...@in...> - 2008-09-18 17:51:14
|
lost connection lost connection lost connection lost connection lost connection |
|
From: <beh...@in...> - 2008-09-17 18:29:58
|
lost connection lost connection lost connection lost connection lost connection |
|
From: <beh...@in...> - 2008-09-16 17:51:46
|
lost connection lost connection lost connection lost connection lost connection |
|
From: <beh...@in...> - 2008-09-13 01:06:55
|
make with all options failed GUIDialog_ViewSettings.cpp: In member function 'void GUIDialog_ViewSettings::writeSettings()': GUIDialog_ViewSettings.cpp:876: warning: comparing floating point with == or != is unsafe GUIDialog_ViewSettings.cpp: At global scope: GUIDialog_ViewSettings.cpp:1060: warning: unused parameter 'data' GUIDialog_ViewSettings.cpp:1122: warning: unused parameter 'data' GUIDialog_ViewSettings.cpp:1149: warning: unused parameter 'data' GUIDialog_ViewSettings.cpp:1178: warning: unused parameter 'data' GUIDialog_ViewSettings.cpp: In member function 'long int GUIDialog_ViewSettings::onCmdEditTable(FX::FXObject*, FX::FXSelector, void*)': GUIDialog_ViewSettings.cpp:1408: warning: comparison between signed and unsigned integer expressions make[5]: *** [GUIDialog_ViewSettings.o] Error 1 make[5]: Leaving directory `/home1/behrisch/DLR/sumo/src/utils/gui/windows' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home1/behrisch/DLR/sumo/src/utils/gui' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home1/behrisch/DLR/sumo/src/utils' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src' make: *** [all-recursive] Error 1 |
|
From: <beh...@in...> - 2008-09-12 00:26:07
|
make failed
g++ -DHAVE_CONFIG_H -I. -I../../src -O2 -DNDEBUG -MT NBNodeShapeComputer.o -MD -MP -MF .deps/NBNodeShapeComputer.Tpo -c -o NBNodeShapeComputer.o NBNodeShapeComputer.cpp
mv -f .deps/NBNodeShapeComputer.Tpo .deps/NBNodeShapeComputer.Po
g++ -DHAVE_CONFIG_H -I. -I../../src -O2 -DNDEBUG -MT NBRequest.o -MD -MP -MF .deps/NBRequest.Tpo -c -o NBRequest.o NBRequest.cpp
mv -f .deps/NBRequest.Tpo .deps/NBRequest.Po
g++ -DHAVE_CONFIG_H -I. -I../../src -O2 -DNDEBUG -MT NBRequestEdgeLinkIterator.o -MD -MP -MF .deps/NBRequestEdgeLinkIterator.Tpo -c -o NBRequestEdgeLinkIterator.o NBRequestEdgeLinkIterator.cpp
mv -f .deps/NBRequestEdgeLinkIterator.Tpo .deps/NBRequestEdgeLinkIterator.Po
g++ -DHAVE_CONFIG_H -I. -I../../src -O2 -DNDEBUG -MT NBTrafficLightDefinition.o -MD -MP -MF .deps/NBTrafficLightDefinition.Tpo -c -o NBTrafficLightDefinition.o NBTrafficLightDefinition.cpp
mv -f .deps/NBTrafficLightDefinition.Tpo .deps/NBTrafficLightDefinition.Po
g++ -DHAVE_CONFIG_H -I. -I../../src -O2 -DNDEBUG -MT NBTrafficLightLogic.o -MD -MP -MF .deps/NBTrafficLightLogic.Tpo -c -o NBTrafficLightLogic.o NBTrafficLightLogic.cpp
mv -f .deps/NBTrafficLightLogic.Tpo .deps/NBTrafficLightLogic.Po
g++ -DHAVE_CONFIG_H -I. -I../../src -O2 -DNDEBUG -MT NBTrafficLightLogicCont.o -MD -MP -MF .deps/NBTrafficLightLogicCont.Tpo -c -o NBTrafficLightLogicCont.o NBTrafficLightLogicCont.cpp
NBTrafficLightLogicCont.cpp:193: error: declaration of 'bool NBTrafficLightLogicCont::insert(const std::string&, NBTrafficLightLogicVector*)' throws different exceptions
NBTrafficLightLogicCont.h:172: error: from previous declaration 'bool NBTrafficLightLogicCont::insert(const std::string&, NBTrafficLightLogicVector*) throw ()'
make[3]: *** [NBTrafficLightLogicCont.o] Error 1
make[3]: Leaving directory `/home1/behrisch/DLR/sumo/src/netbuild'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make: *** [all-recursive] Error 1
make install failed
Making install in netbuild
make[2]: Entering directory `/home1/behrisch/DLR/sumo/src/netbuild'
g++ -DHAVE_CONFIG_H -I. -I../../src -O2 -DNDEBUG -MT NBTrafficLightLogicCont.o -MD -MP -MF .deps/NBTrafficLightLogicCont.Tpo -c -o NBTrafficLightLogicCont.o NBTrafficLightLogicCont.cpp
NBTrafficLightLogicCont.cpp:193: error: declaration of 'bool NBTrafficLightLogicCont::insert(const std::string&, NBTrafficLightLogicVector*)' throws different exceptions
NBTrafficLightLogicCont.h:172: error: from previous declaration 'bool NBTrafficLightLogicCont::insert(const std::string&, NBTrafficLightLogicVector*) throw ()'
make[2]: *** [NBTrafficLightLogicCont.o] Error 1
make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src/netbuild'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make: *** [install-recursive] Error 1
make with all options failed
from NBConnection.h:34,
from NBConnectionDefs.h:35,
from NBTrafficLightLogic.h:38,
from NBTrafficLightLogicCont.cpp:37:
../../src/utils/geom/Position2D.h: In function 'bool operator==(const Position2D&, const Position2D&)':
../../src/utils/geom/Position2D.h:139: warning: comparing floating point with == or != is unsafe
../../src/utils/geom/Position2D.h:139: warning: comparing floating point with == or != is unsafe
../../src/utils/geom/Position2D.h: In function 'bool operator!=(const Position2D&, const Position2D&)':
../../src/utils/geom/Position2D.h:143: warning: comparing floating point with == or != is unsafe
../../src/utils/geom/Position2D.h:143: warning: comparing floating point with == or != is unsafe
NBTrafficLightLogicCont.cpp: At global scope:
NBTrafficLightLogicCont.cpp:193: error: declaration of 'bool NBTrafficLightLogicCont::insert(const std::string&, NBTrafficLightLogicVector*)' throws different exceptions
NBTrafficLightLogicCont.h:172: error: from previous declaration 'bool NBTrafficLightLogicCont::insert(const std::string&, NBTrafficLightLogicVector*) throw ()'
make[3]: *** [NBTrafficLightLogicCont.o] Error 1
make[3]: Leaving directory `/home1/behrisch/DLR/sumo/src/netbuild'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home1/behrisch/DLR/sumo/src'
make: *** [all-recursive] Error 1
|
|
From: Mauro B. <bia...@gm...> - 2008-09-11 10:43:11
|
Dear developers, I am new to the mailing list (and also to SUMO), and I am beginning to implement a module for pollutant emissions estimation for SUMO. I'd like to share with you some ideas about my approach and ask for your advices. First of all, for what i understand, there are two main possibilities: 1) Integrate the emission calculation directly into SUMO 2) Keeping the emission calculation in a separate module, and let it communcate with SUMO at runtime via TCP/IP For very simple emission models, another option can raise: 3) Calculating emissions with an external program, processing the dumpfiles produced by SUMO as output. Actually, I'm considering the first option, as it can cover a wider range of emissions models and would end in a simpler architecture and interface for the final user. Another question is related to what emission model to use. Theorically, there are a good numbers of emission models, ranging from averaged to istantaneous models. In practice, i found only two options that seems to have updated and available emission factors for modern vehicles: 1) the COPERT model (http://lat.eng.auth.gr/copert/) 2) The upcoming ARTEMIS model ( http://www.inrets.fr/ur/lte/publi-autresactions/fichesresultats/ficheartemis/artemis.html ) The first is an aggregated model, depending only from averaged speeds of vehicle fleet, and thus suitable only for time resolutions above 1 day (which is probably yet too short). The second model seems more promising, as it introduces the concept of "traffic situations", pushing it closer to istantaneous models. From model's documentation it seems like it is suitable for link-wise evaluations, for a time resolution down to 1 hour. Before going deeper in the topic, I'd like to know if anyone is working on a similar project, and if so to share your ideas. In particular, has anyone identified an instantaneous model to be plugged into the simulation? Thanks for your attention! Best regards, Mauro -- Mauro Bianchi bia...@gm... |
|
From: <beh...@in...> - 2008-09-07 00:26:56
|
autoreconf failed autoreconf -i Using `AC_PROG_RANLIB' is rendered obsolete by `AC_PROG_LIBTOOL' configure.ac:10: installing `./missing' configure.ac:10: installing `./install-sh' src/Makefile.am: installing `./depcomp' Makefile.am: installing `./INSTALL' configure.ac:87: required file `src/mesogui/Makefile.in' not found configure.ac:87: required file `src/mesosim/Makefile.in' not found autoreconf: automake failed with exit status: 1 make: *** [all] Error 1 configure failed config.status: creating src/utils/xml/Makefile config.status: creating docs/Makefile config.status: creating docs/docbook/Makefile config.status: creating docs/docbook/xslt/Makefile config.status: creating docs/docbook/xslt/sumo_html/Makefile config.status: creating docs/docbook/gfx/Makefile config.status: creating docs/docbook/gfx/dev/Makefile config.status: creating docs/docbook/gfx/more/Makefile config.status: creating docs/docbook/gfx/user/Makefile config.status: error: cannot find input file: Makefile.in make dist failed config.status: creating docs/Makefile config.status: creating docs/docbook/Makefile config.status: creating docs/docbook/xslt/Makefile config.status: creating docs/docbook/xslt/sumo_html/Makefile config.status: creating docs/docbook/gfx/Makefile config.status: creating docs/docbook/gfx/dev/Makefile config.status: creating docs/docbook/gfx/more/Makefile config.status: creating docs/docbook/gfx/user/Makefile config.status: error: cannot find input file: Makefile.in make: *** No rule to make target `dist'. Stop. make doc failed config.status: creating docs/docbook/Makefile config.status: creating docs/docbook/xslt/Makefile config.status: creating docs/docbook/xslt/sumo_html/Makefile config.status: creating docs/docbook/gfx/Makefile config.status: creating docs/docbook/gfx/dev/Makefile config.status: creating docs/docbook/gfx/more/Makefile config.status: creating docs/docbook/gfx/user/Makefile config.status: error: cannot find input file: Makefile.in make: *** No rule to make target `dist'. Stop. make: *** No rule to make target `doc'. Stop. make failed config.status: creating src/utils/gui/images/Makefile config.status: creating src/utils/gui/tracker/Makefile config.status: creating src/utils/gui/windows/Makefile config.status: creating src/utils/importio/Makefile config.status: creating src/utils/iodevices/Makefile config.status: creating src/utils/options/Makefile config.status: creating src/utils/shapes/Makefile config.status: creating src/utils/xml/Makefile config.status: creating docs/Makefile config.status: creating docs/docbook/Makefile config.status: creating docs/docbook/xslt/Makefile config.status: creating docs/docbook/xslt/sumo_html/Makefile config.status: creating docs/docbook/gfx/Makefile config.status: creating docs/docbook/gfx/dev/Makefile config.status: creating docs/docbook/gfx/more/Makefile config.status: creating docs/docbook/gfx/user/Makefile config.status: error: cannot find input file: Makefile.in make: *** No rule to make target `dist'. Stop. make: *** No rule to make target `doc'. Stop. make: *** No targets specified and no makefile found. Stop. make install failed config.status: creating docs/docbook/xslt/sumo_html/Makefile config.status: creating docs/docbook/gfx/Makefile config.status: creating docs/docbook/gfx/dev/Makefile config.status: creating docs/docbook/gfx/more/Makefile config.status: creating docs/docbook/gfx/user/Makefile config.status: error: cannot find input file: Makefile.in make: *** No rule to make target `dist'. Stop. make: *** No rule to make target `doc'. Stop. make: *** No targets specified and no makefile found. Stop. make: *** No rule to make target `install'. Stop. configure with all options failed config.status: creating src/utils/xml/Makefile config.status: creating docs/Makefile config.status: creating docs/docbook/Makefile config.status: creating docs/docbook/xslt/Makefile config.status: creating docs/docbook/xslt/sumo_html/Makefile config.status: creating docs/docbook/gfx/Makefile config.status: creating docs/docbook/gfx/dev/Makefile config.status: creating docs/docbook/gfx/more/Makefile config.status: creating docs/docbook/gfx/user/Makefile config.status: error: cannot find input file: Makefile.in make with all options failed config.status: creating src/utils/gui/events/Makefile config.status: creating src/utils/gui/globjects/Makefile config.status: creating src/utils/gui/images/Makefile config.status: creating src/utils/gui/tracker/Makefile config.status: creating src/utils/gui/windows/Makefile config.status: creating src/utils/importio/Makefile config.status: creating src/utils/iodevices/Makefile config.status: creating src/utils/options/Makefile config.status: creating src/utils/shapes/Makefile config.status: creating src/utils/xml/Makefile config.status: creating docs/Makefile config.status: creating docs/docbook/Makefile config.status: creating docs/docbook/xslt/Makefile config.status: creating docs/docbook/xslt/sumo_html/Makefile config.status: creating docs/docbook/gfx/Makefile config.status: creating docs/docbook/gfx/dev/Makefile config.status: creating docs/docbook/gfx/more/Makefile config.status: creating docs/docbook/gfx/user/Makefile config.status: error: cannot find input file: Makefile.in make: *** No rule to make target `clean'. Stop. |