svn-1655 make error

Viewing 8 posts - 21 through 28 (of 28 total)
  • Author
    Posts
  • #12450
    MSN_Exploder
    Participant

    @rpedde wrote:

    Still some sqlite3 stuff I needed fixed, but might not get to that.

    Hmm, what kind of stuff?
    Maybe i can look at it, maybe even help u out πŸ˜‰
    (Dont count on that πŸ™„ )

    @rpedde wrote:

    Sick like a dog last couple days.

    Come on, get well!!!
    Now!!!! πŸ˜‰

    MSN_Exploder

    #12451
    squashuax
    Participant

    I have been trying and trying to get 1671 to work, with no luck. Can someone please tell me how to ugrade to svn-1673, using ipkg, putty, and busybox?

    #12452
    rpedde
    Participant

    Hmm, what kind of stuff?
    Maybe i can look at it, maybe even help u out πŸ˜‰
    (Dont count on that πŸ™„ )

    i keep getting sqlite_misuse errors, but I can’t find it, so to work around it until I really find where I’m screwing stuff up, I’m just going to re-open the db in each thread.

    @rpedde wrote:

    Sick like a dog last couple days.

    Come on, get well!!!
    Now!!!! πŸ˜‰

    [/quote]

    Trying… I feel almost human now.

    — Ron

    #12453
    MSN_Exploder
    Participant

    @rpedde wrote:

    i keep getting sqlite_misuse errors, but I can’t find it, so to work around it until I really find where I’m screwing stuff up, I’m just going to re-open the db in each thread.

    Every thread connects directly to the db?
    (Cant look into the source right now)
    Why not simply use one thread only for the database?

    i.e. use one thread just doing the db stuff,
    and all the other fancy threads just queue the “db-master-thread”
    (Dont punish me if there already something similar, no source here πŸ˜‰ )

    btw, all the sourceforge links on the wiki – trac page are leading straight into nowhere πŸ˜‰

    @rpedde wrote:

    Trying… I feel almost human now.

    great ^^

    #12454
    rpedde
    Participant

    @MSN_Exploder wrote:

    @rpedde wrote:

    i keep getting sqlite_misuse errors, but I can’t find it, so to work around it until I really find where I’m screwing stuff up, I’m just going to re-open the db in each thread.

    Every thread connects directly to the db?
    (Cant look into the source right now)
    Why not simply use one thread only for the database?

    i.e. use one thread just doing the db stuff,
    and all the other fancy threads just queue the “db-master-thread”
    (Dont punish me if there already something similar, no source here πŸ˜‰ )

    Tried that first… amaaaaazingly slow.

    btw, all the sourceforge links on the wiki – trac page are leading straight into nowhere πŸ˜‰

    Hrmf… sourceforge… that’s the other thing, I’m trying to migrate all the web stuff to a new host too..

    — Ron

    #12455
    MSN_Exploder
    Participant

    @rpedde wrote:

    Tried that first… amaaaaazingly slow.

    Ok, never used db much, manly to store some values etc.
    and mostly mysql db’s
    never had a performance issue with that πŸ˜‰

    Will look at the code, maybe i can help u out.

    Maybe some sort of shared mem thing?
    just as a first thought πŸ™„

    Hmm, maybe after getting things ready from the university. 😯

    @rpedde wrote:

    Hrmf… sourceforge… that’s the other thing, I’m trying to migrate all the web stuff to a new host too..

    Ahh, k, I see.
    But whats wrong with sourceforge?

    #12456
    rpedde
    Participant

    @MSN_Exploder wrote:

    But whats wrong with sourceforge?

    Just slow. Move stuff around a fair amount. Just kind of a pain. Not as nice as a dedicated host. πŸ™‚

    — Ron

    #12457
    MSN_Exploder
    Participant

    @rpedde wrote:

    @MSN_Exploder wrote:

    But whats wrong with sourceforge?

    Just slow. Move stuff around a fair amount. Just kind of a pain. Not as nice as a dedicated host. πŸ™‚

    Ahh ok, never used sourceforge on a regular basis πŸ˜‰

    Yeah dedicated host is great, but expensive ^^

Viewing 8 posts - 21 through 28 (of 28 total)
  • The forum ‘Nightlies Feedback’ is closed to new topics and replies.