-
-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing environment variables for "briefcase dev" run #193
Comments
Thanks for the report; can you please clarify what operating system you're using? I think you've provided a uname string... but it's not at all clear what actual distribution that is. It seems to suggest Ubuntu... but it's not obvious what release of Ubuntu it is. |
Sure!
LSB Version:
core-11.2ubuntu1-noarch:printing-11.2ubuntu1-noarch:security-11.2ubuntu1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 22.10
Release: 22.10
Codename: kinetic
…On Sun, Mar 12, 2023 at 11:49 PM Russell Keith-Magee < ***@***.***> wrote:
Thanks for the report; can you please clarify what operating system you're
using? I *think* you've provided a uname string... but it's not at all
clear what actual distribution that is. It seems to suggest Ubuntu... but
it's not obvious what release of Ubuntu it is.
—
Reply to this email directly, view it on GitHub
<#193 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHMOYXOPVTUVBR5UW7AF5LW3ZHHJANCNFSM6AAAAAAVYFFWNM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Thanks for that clarification. This seems like you might be missing something in your local system configuration (and - admittedly, this might be because we've missed a pre-requisite in our tutorial). Can you confirm:
produces valid output (something like |
pkg-config --libs glib-2.0
Package glib-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `glib-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'glib-2.0' found
The above mentioned file seem to be here:
locate glib-2.0.pc
/usr/lib/x86_64-linux-gnu/pkgconfig/glib-2.0.pc
However using sudo, I get this result:
sudo pkg-config --libs glib-2.0
[sudo] password for nils:
-lglib-2.0
This is all done outside the venv environment, so "env | grep
PKG_CONFIG_PATH" returns nothing.
…On Mon, Mar 13, 2023 at 1:32 AM Russell Keith-Magee < ***@***.***> wrote:
Thanks for that clarification.
This seems like you might be missing something in your local system
configuration (and - admittedly, this might be because we've missed a
pre-requisite in our tutorial).
Can you confirm:
1. If your system has pkg-config installed
2. Whether:
pkg-config --libs glib-2.0
produces valid output (something like -lglib2.0) or an error, *without*
the environment configuration you mention above?
—
Reply to this email directly, view it on GitHub
<#193 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHMOYUZ3H2GWVAGGLVOOY3W3ZTJBANCNFSM6AAAAAAVYFFWNM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Thanks - I've never seen pkg-config provide different results depending on whether it's run with admin credentials. Is there any possibility that your local shell config is overriding (or ignoring) system default configurations? Have you got a non-default shell? Anything else of note that isn't a "Ubuntu Kinetic default system install"? |
I have personally done nothing to change it afaik.
It may be slightly special because it has Linux pre-installed by System76:
sudo lshw
nils-sys76
description: Desktop Computer
product: Sable (All)
vendor: System76, Inc.
version: sabl4
serial: System Serial Number
width: 64 bits
capabilities: smbios-2.7 dmi-2.7 smp vsyscall32
They install quite a few tools as indicated here:
[image: image.png]
I don't want to add a lot of info you don't need, but if you have commands
you want me to run and send the results of, then feel free to tell me.
However, if this is a problem only for me then it's fine if you want to
close this issue, after all I have a nice fix because of how your error
messages are so verbose and helpful.
…On Tue, Mar 14, 2023 at 1:54 AM Russell Keith-Magee < ***@***.***> wrote:
Thanks - I've never seen pkg-config provide different results depending on
whether it's run with admin credentials. Is there any possibility that your
local shell config is overriding (or ignoring) system default
configurations? Have you got a non-default shell? Anything else of note
that isn't a "Ubuntu Kinetic default system install"?
—
Reply to this email directly, view it on GitHub
<#193 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHMOYRKBUH5QZR32MT5TQ3W366VXANCNFSM6AAAAAAVYFFWNM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hrm - this is definitely odd. If you create a fresh user account on your machine, does that new user inherit this oddity, or does pkg-config work there without the environment variable? |
Tagging @Firstyear because he expressed an interest in the haunting of pkg-config in this case :-) |
Thanks @freakboy3742 I'm installing a VM to have a look at this. |
Okay, I've setup a ubuntu kinetic machine but I was unable to reproduce. @NilsRG Can you provide me the output of the following commands all run as your user - I will indicate inline when sudo is needed.
That will help give me some better ideas on where to follow from here because currently "out of box" I can't reproduce. |
|
Describe the bug
After following the setup description at beeware/docs/tutorial/tutorial-1.rst exactly, I get two errors about missing folders. I made it work by adding these lines to the activate script:
I don't know if that's the right way to do it, so I am not going to fork that page and make a fix (for now).
Log files before and after attached.
Steps to reproduce
Expected behavior
Expected behaviour is what happens in the last log file...
Screenshots
No response
Environment
166628906722.04fe0ce53dev-Ubuntu SMP PREEMPT_DY x86_64 x86_64 x86_64 GNU/LinuxLogs
briefcase.2023_03_12-14_37_26.dev.log
briefcase.2023_03_12-15_09_51.dev.log
briefcase.2023_03_12-15_16_07.dev.log
briefcase.2023_03_12-15_18_53.dev.log
Additional context
No response
The text was updated successfully, but these errors were encountered: